# HG changeset patch
# User Sebastien Decugis <sdecugis@nict.go.jp>
# Date 1238379226 -32400
# Node ID 05b38ab642bcacdf5d83721462942847cdda1de4
# Parent  d07dd60aefb0ffe540fb4db0ae2c772356e37668
Added new idea in the draft, to be merged in the text later.

diff -r d07dd60aefb0 -r 05b38ab642bc New_ERP_draft_src.txt
--- a/New_ERP_draft_src.txt	Wed Mar 25 02:38:52 2009 +0900
+++ b/New_ERP_draft_src.txt	Mon Mar 30 11:13:46 2009 +0900
@@ -10,6 +10,9 @@
 The EAP Re-authentication Protocol [RFC5296] provides an optimization for EAP authentication when a peer moves from an authenticator to another. This protocol assumes that a AAA protocol is available to transport the ERP messages between authenticator and ER server. [draft-gaonkar-radext-erp-attrs-03] specifies the transport of ERP using RADIUS. This document specifies the transport of ERP using Diameter [RFC3588].
 
 
+*** TODO ***
+-> Add a Session-Id AVP in the ERP-RK-Answer grouped AVP. This AVP contains the Session ID corresponding to the full EAP authentication. The ER server learns this Session ID and is able to send it to the NAS (how? TBD) when the peer re-authenticates. Then, on successful re-authentication, the NAS can send accounting records containing the proper Session-Id information (is it OK?)
+
 
 *Differences with [draft-ietf-dime-erp-00]*