EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying
RFC 6630, “EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying”, is a Proposed Standard document published in June 2012 by Z. Cao, H. Deng, Q. Wu, G. Zorn. 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.
The EAP Re-authentication Protocol (ERP) 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.
Authenticated Anticipatory Keying (AAK) is a method by which cryptographic keying material may be established upon one or more Candidate Attachment Points (CAPs) prior to handover. AAK uses the AAA infrastructure for key transport.
This document specifies the extensions necessary to enable AAK support in ERP. [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 6630 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6629 Considerations on the Application of the Level 3 Multihoming Shim Protocol for IPv6
- RFC 6631 Password Authenticated Connection Establishment with the Internet Key Exchange Protocol version 2
- RFC 6628 Efficient Augmented Password-Only Authentication and Key Exchange for IKEv2
- RFC 6632 An Overview of the IETF Network Management Standards
- RFC 6627 Overview of Pre-Congestion Notification Encoding
- RFC 6633 Deprecation of ICMP Source Quench Messages
- RFC 6626 Dynamic Prefix Allocation for Network Mobility for Mobile IPv4
- RFC 6625 Wildcards in Multicast VPN Auto-Discovery Routes