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 avoid repeating 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
- RFC6696
- Published
- July 2012
- Authors
- Z. Cao; B. He; Y. Shi; Q. Wu; G. Zorn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 47
- Also known as
- —
- Obsoletes:
- RFC 5296
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5295Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)Current
August 2008
- RFC 6697Handover Keying (HOKEY) Architecture DesignCurrent
July 2012
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
- RFC 6685Expert Review for Incident Object Description Exchange Format (IODEF) Extensions in IANA XML RegistryObsoleted
July 2012
- RFC 6684Guidelines and Template for Defining Extensions to the Incident Object Description Exchange Format (IODEF)Current
July 2012
- RFC 6680Generic Security Service Application Programming Interface (GSS-API) Naming ExtensionsCurrent
August 2012
- RFC 6712Internet X.509 Public Key Infrastructure -- HTTP Transfer for the Certificate Management Protocol (CMP)Obsoleted
September 2012
- RFC 6678Requirements for a Tunnel-Based Extensible Authentication Protocol (EAP) MethodCurrent
July 2012
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?