Diameter Support for the EAP Re-authentication Protocol (ERP) (RFC6942)
Original Publication Date: 2013-May-01
Included in the Prior Art Database: 2013-May-11
Internet Society Requests For Comment (RFCs)
J. Bournelle: AUTHOR [+5]
AbstractCao, et al. [RFC6696] defines the EAP Re-authentication Protocol (ERP). It consists of the following steps:
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)
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 (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 Docu...