RFC 5296: EAP Extensions for EAP Re-authentication Protocol (ERP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6696.
Current version: RFC 6696 — EAP Extensions for the EAP Re-authentication Protocol (ERP)
In plain English — editorial summary, not part of the RFC
The Extensible Authentication Protocol (EAP) is a generic framework supporting multiple types of authentication methods. In systems where EAP is used for authentication, it is desirable to not repeat the entire EAP exchange with another authenticator. This document specifies extensions to EAP and the EAP keying hierarchy to support an EAP method-independent protocol for efficient re-authentication between the peer and an EAP re-authentication server through any authenticator. The re-authentication server may be in the home network or in the local network to which the peer is connecting. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5296
- Published
- August 2008
- Authors
- V. Narayanan; L. Dondeti
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 43
- Also known as
- —
- Obsoleted by:
- RFC 6696
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5216The EAP-TLS Authentication ProtocolUpdated
March 2008
- RFC 4334Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)Current
February 2006
- RFC 9140Nimble Out-of-Band Authentication for EAP (EAP-NOOB)Updated
December 2021
- RFC 4793The EAP Protected One-Time Password Protocol (EAP-POTP)Current
February 2007
- RFC 4005Diameter Network Access Server ApplicationObsoleted
August 2005
- RFC 3748Extensible Authentication Protocol (EAP)Updated
June 2004
- RFC 2716PPP EAP TLS Authentication ProtocolObsoleted
October 1999
- RFC 5295Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)Current
August 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?