Diameter Attribute-Value Pairs for Cryptographic Key Transport
RFC 6734
|
| Document |
Type |
|
RFC - Proposed Standard
(October 2012; No errata)
|
|
Last updated |
|
2015-10-14
|
|
Replaces |
|
draft-wu-dime-local-keytran
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Lionel Morand
|
| IESG |
IESG state |
|
RFC 6734 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Dan Romascanu
|
|
IESG note |
|
Lionel Morand (lionel.morand@orange-ftgroup.com) is the document shepherd.
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force (IETF) G. Zorn
Request for Comments: 6734 Network Zen
Category: Standards Track Q. Wu
ISSN: 2070-1721 Huawei
V. Cakulev
Alcatel Lucent
October 2012
Diameter Attribute-Value Pairs for Cryptographic Key Transport
Abstract
Some Authentication, Authorization, and Accounting (AAA) applications
require the transport of cryptographic keying material. This
document specifies a set of Attribute-Value Pairs (AVPs) providing
native Diameter support of cryptographic key delivery.
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/rfc6734.
Copyright 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.
Zorn, et al. Standards Track [Page 1]
RFC 6734 Diameter Key Transport AVPs October 2012
Table of Contents
1. Introduction ....................................................2
2. Terminology .....................................................3
2.1. Requirements Language ......................................3
2.2. Technical Terms and Acronyms ...............................3
3. Attribute-Value Pair Definitions ................................3
3.1. Key AVP ....................................................3
3.1.1. Key-Type AVP ........................................4
3.1.2. Key-Name AVP ........................................4
3.1.3. Keying-Material AVP .................................4
3.1.4. Key-Lifetime AVP ....................................4
3.1.5. Key-SPI .............................................5
4. Security Considerations .........................................5
5. IANA Considerations .............................................5
5.1. AVP Codes ..................................................5
5.2. AVP Values .................................................5
6. Acknowledgements ................................................6
7. References ......................................................6
7.1. Normative References .......................................6
7.2. Informative References .....................................6
1. Introduction
The Diameter Extensible Authentication Protocol (EAP) application
[RFC4072] defines the EAP-Master-Session-Key and EAP-Key-Name AVPs
for the purpose of transporting cryptographic keying material derived
during the execution of certain Extensible Authentication Protocol
(EAP) [RFC3748] methods (for example, EAP-TLS [RFC5216]). At most
one instance of either of these AVPs is allowed in any Diameter
message.
However, recent work (see, for example, [RFC5295]) has specified
methods to derive other keys from the keying material created during
EAP method execution that may require transport in addition to the
Master Session Key (MSK). Also, the EAP Re-authentication Protocol
(ERP) [RFC6696] specifies new keys that may need to be transported
between Diameter nodes.
This document specifies a set of AVPs allowing the transport of
multiple cryptographic keys in a single Diameter message.
Zorn, et al. Standards Track [Page 2]
RFC 6734 Diameter Key Transport AVPs October 2012
Show full document text