Mercurial > hg > ietf
comparison New_ERP_draft_src.txt @ 22:05b38ab642bc
Added new idea in the draft, to be merged in the text later.
| author | Sebastien Decugis <sdecugis@nict.go.jp> |
|---|---|
| date | Mon, 30 Mar 2009 11:13:46 +0900 |
| parents | 8b6e98eec7ef |
| children |
comparison
equal
deleted
inserted
replaced
| 21:d07dd60aefb0 | 22:05b38ab642bc |
|---|---|
| 7 | 7 |
| 8 *Abstract* | 8 *Abstract* |
| 9 | 9 |
| 10 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]. | 10 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]. |
| 11 | 11 |
| 12 | |
| 13 *** TODO *** | |
| 14 -> 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?) | |
| 12 | 15 |
| 13 | 16 |
| 14 *Differences with [draft-ietf-dime-erp-00]* | 17 *Differences with [draft-ietf-dime-erp-00]* |
| 15 | 18 |
| 16 In this document, we specify a new Diameter application ID for Diameter messages transporting ERP exchanges between authenticator and ER server. We re-use the mechanism described in [draft-ietf-dime-erp-00] as an option available to provide implicit bootstrapping to the ER server. | 19 In this document, we specify a new Diameter application ID for Diameter messages transporting ERP exchanges between authenticator and ER server. We re-use the mechanism described in [draft-ietf-dime-erp-00] as an option available to provide implicit bootstrapping to the ER server. |