Internet Engineering Task Force (IETF) Z. Cao
Request for Comments: 6696 China Mobile
Obsoletes: 5296 B. He
Category: Standards Track CATR
ISSN: 2070-1721 Y. Shi
Q. Wu, Ed.
Huawei
G. Zorn, Ed.
Network Zen
July 2012
EAP Extensions for the EAP Re-authentication Protocol (ERP)
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 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.
This memo obsoletes RFC 5296.
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/rfc6696.
Cao, et al. Standards Track [Page 1]RFC 6696 EAP Extensions for ERP July 2012Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Cao, et al. Standards Track [Page 2]RFC 6696 EAP Extensions for ERP July 2012Table of Contents
1. Introduction ....................................................4
1.1. Changes from RFC 5296 ......................................5
2. Terminology .....................................................5
3. ERP Description .................................................7
3.1. ERP with the Home ER Server ...............................10
3.2. ERP with a Local ER Server ................................11
4. ER Key Hierarchy ...............................................13
4.1. rRK Derivation ............................................13
4.2. rRK Properties ............................................14
4.3. rIK Derivation ............................................14
4.4. rIK Properties ............................................15
4.5. rIK Usage .................................................16
4.6. rMSK Derivation ...........................................16
4.7. rMSK Properties ...........................................17
5. Protocol Details ...............................................17
5.1. ERP Bootstrapping .........................................17
5.2. Steps in ERP ..............................................20
5.2.1. Multiple Simultaneous Runs of ERP ..................23
5.2.2. ERP Failure Handling ...............................23
5.3. EAP Codes .................................................25
5.3.1. EAP-Initiate/Re-auth-Start Packet ..................26
5.3.1.1. Authenticator Operation ...................27
5.3.1.2. Peer Operation ............................27
5.3.2. EAP-Initiate/Re-auth Packet ........................28
datatracker.ietf.org