EAP Extensions for EAP Re-authentication Protocol
RFC 5296, “EAP Extensions for EAP Re-authentication Protocol”, is a Proposed Standard document published in August 2008 by V. Narayanan, L. Dondeti. It has been obsoleted by RFC 6696 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5296 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5295 Specification for the Derivation of Root Keys from an Extended Master Session Key
- RFC 5297 Synthetic Initialization Vector Authenticated Encryption Using the Advanced Encryption Standard
- RFC 5294 Host Threats to Protocol Independent Multicast
- RFC 5298 Analysis of Inter-Domain Label Switched Path Recovery
- RFC 5293 Sieve Email Filtering: Editheader Extension
- RFC 5292 Address-Prefix-Based Outbound Route Filter for BGP-4
- RFC 5291 Outbound Route Filtering Capability for BGP-4
- RFC 5301 Dynamic Hostname Exchange Mechanism for IS-IS