Diameter Attribute-Value Pairs for Cryptographic Key Transport

Cakulev, Violeta; Zorn, Glen

doi:10.17487/rfc6734

Cited by 3 publications

(6 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…When the authenticator receives this ERP/DEA answer, it processes it as described in the Diameter EAP Application specification [RFC4072] and RFC 6696: the content of the EAP-Payload AVP is forwarded to the peer, and the contents of the Keying-Material AVP [RFC6734] is used as a shared secret for a secure association protocol specific to the lower layer in use.…”

Section: Bootstrapping During the First Re-authenticationmentioning

confidence: 99%

See 1 more Smart Citation

Diameter Support for the EAP Re-authentication Protocol (ERP)

Bournelle¹,

Morand²,

Decugis³

et al. 2013

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Section: Bootstrapping During the First Re-authenticationmentioning

confidence: 99%

“…The Key AVP [RFC6734] is of type Grouped and is used to carry the rRK or rMSK and associated attributes. The usage of the Key AVP and its constituent AVPs in this application is specified in the following subsections.…”

Section: Key Avpmentioning

confidence: 99%

Diameter Support for the EAP Re-authentication Protocol (ERP)

Bournelle¹,

Morand²,

Decugis³

et al. 2013

Self Cite

View full text Add to dashboard Cite

show abstract

“…This mismatch will result in different SKs being generated. The HAAA returns the SK to the IKEv2 server using the Key AVP as specified in [RFC6734].…”

Section: Support For Ikev2 and Shared Keysmentioning

confidence: 99%

“…The IKEv2-SK-Request message MAY contain a Key-SPI AVP (Key-SPI AVP is specified in [RFC6734]). If included, it contains the SPI that HAAA SHALL use, in addition to the other parameters (e.g., Initiator-Identity), to identify the appropriate SK.…”

Section: * [ Avp ]mentioning

confidence: 99%

See 1 more Smart Citation

Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers

Cakulev¹,

Lior²

2012

Self Cite

View full text Add to dashboard Cite

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

Zorn¹,

Deng²,

Cao³

et al. 2012

Self Cite

View full text Add to dashboard Cite

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.

show abstract

Diameter Attribute-Value Pairs for Cryptographic Key Transport

Cited by 3 publications

References 4 publications

Diameter Support for the EAP Re-authentication Protocol (ERP)

Diameter Support for the EAP Re-authentication Protocol (ERP)

Diameter IKEv2 SK: Using Shared Keys to Support Interaction between IKEv2 Servers and Diameter Servers

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

Contact Info

Product

Resources

About