Diameter Support for the EAP Re-authentication Protocol (ERP)
RFC 6942
Document | Type |
RFC - Proposed Standard
(May 2013; No errata)
Was draft-ietf-dime-erp (dime WG)
|
|
---|---|---|---|
Authors | Julien Bournelle , Lionel Morand , Sebastien Decugis , Qin Wu , Glen Zorn | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Jouni Korhonen | ||
IESG | IESG state | RFC 6942 (Proposed Standard) | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | BenoƮt Claise | ||
IESG note | Jouni Korhonen (jouni.nospam@gmail.com) is the document shepherd. | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) J. Bournelle Request for Comments: 6942 L. Morand Category: Standards Track Orange Labs ISSN: 2070-1721 S. Decugis INSIDE Secure Q. Wu Huawei G. Zorn Network Zen May 2013 Diameter Support for the EAP Re-authentication Protocol (ERP) Abstract The EAP Re-authentication Protocol (ERP) defines extensions to the Extensible Authentication Protocol (EAP) to support efficient re-authentication between the peer and an EAP Re-authentication (ER) server through a compatible authenticator. This document specifies Diameter support for ERP. It defines a new Diameter ERP application to transport ERP messages between an ER authenticator and the ER server, and a set of new Attribute-Value Pairs (AVPs) that can be used to transport the cryptographic material needed by the re-authentication server. 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/rfc6942. Bournelle, et al. Standards Track [Page 1] RFC 6942 Diameter ERP Application May 2013 Copyright Notice Copyright (c) 2013 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 3. Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 5 5. Bootstrapping the ER Server . . . . . . . . . . . . . . . . . 6 5.1. Bootstrapping during the Initial EAP Authentication . . . 6 5.2. Bootstrapping during the First Re-authentication . . . . 8 6. Re-authentication . . . . . . . . . . . . . . . . . . . . . . 11 7. Application Id . . . . . . . . . . . . . . . . . . . . . . . 12 8. AVPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.1. ERP-RK-Request AVP . . . . . . . . . . . . . . . . . . . 13 8.2. ERP-Realm AVP . . . . . . . . . . . . . . . . . . . . . . 13 8.3. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . 13 8.3.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . 13 8.3.2. Keying-Material AVP . . . . . . . . . . . . . . . . . 13 8.3.3. Key-Name AVP . . . . . . . . . . . . . . . . . . . . 14 8.3.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . 14 9. Result-Code AVP Values . . . . . . . . . . . . . . . . . . . 14 9.1. Permanent Failures . . . . . . . . . . . . . . . . . . . 14 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 10.1. Diameter Application Identifier . . . . . . . . . . . . 14 10.2. New AVPs . . . . . . . . . . . . . . . . . . . . . . . . 15 10.3. New Permanent Failures Result-Code AVP Values . . . . . 15 11. Security Considerations . . . . . . . . . . . . . . . . . . . 15 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 14.1. Normative References . . . . . . . . . . . . . . . . . . 16 14.2. Informative References . . . . . . . . . . . . . . . . . 17Show full document text