RADIUS Support for EAP Re-authentication Protocol
draft-gaonkar-radext-erp-attrs-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kedar Gaonkar , Lakshminath R. Dondeti , Vidya Narayanan , Glen Zorn | ||
| Last updated | 2008-02-25 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFCxxxx (draft-ietf-hokey-erx after publication) [6] specifies the EAP Re-authentication Protocol (ERP). This document specifies RADIUS support for ERP. The procedures in RFC3579 [1] are used for encapsulating the EAP Initiate and Finish messages specified in RFCxxxx (draft-ietf-hokey-erx after publication) [6]. This document specifies attributes for the request and delivery of Domain Specific Root Keys from the AAA/EAP server to the ER Server. Additionally, this document also specifies RADIUS message processing rules relevant to ERP.
Authors
Kedar Gaonkar
Lakshminath R. Dondeti
Vidya Narayanan
Glen Zorn
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)