EAP Re-authentication Protocol Extensions for Authenticated Anticipatory Keying (ERP/AAK)

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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6630.

Access Control Solutions for Next Generation Networks

“…Mishra et al (2004), S. Pack & Y. Choi (2002, Z. Cao et al (2011), F.Bernal-Hidalgo et al (2011) propose the pre-installation of cryptographic material (e.g., keys) in candidate authenticators so that the keys required for secure association are already available when the peer moves to the authenticators. As depicted in Fig.…”

Handover Keying (HOKEY) Architecture Design

“…o the peer; o the authenticator, which is a part of the SAP and CAPs; o the EAP server; o the ER server; and o the ER/AAK server [RFC6630], either in the home domain or local to the authenticator.…”