draft-ietf-dime-local-keytran-04.txt   draft-ietf-dime-local-keytran-05.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track Q. Wu, Ed. Intended status: Standards Track Q. Wu, Ed.
Expires: November 26, 2010 Huawei Expires: November 26, 2010 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
May 25, 2010 May 25, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-04 draft-ietf-dime-local-keytran-05
Abstract Abstract
Some Authentication, Authorization, and Accounting (AAA) applications Some Authentication, Authorization, and Accounting (AAA) applications
require the transport of cryptographic keying material; this document require the transport of cryptographic keying material; this document
specifies a set of Attribute-Value Pairs (AVPs) providing native specifies a set of Attribute-Value Pairs (AVPs) providing native
Diameter support of cryptographic key delivery. Diameter support of cryptographic key delivery.
Status of this Memo Status of this Memo
skipping to change at page 2, line 19 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3
2.2. Technical Terms and Acronyms . . . . . . . . . . . . . . . 3 2.2. Technical Terms and Acronyms . . . . . . . . . . . . . . . 3
3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . . 4 3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . . 4
3.1. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.1. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . . 4 3.1.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . . 4
3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 5 3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 5
3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5 3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5
3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5 3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5
3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 6 3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
The Diameter EAP application [RFC4072] defines the EAP-Master- The Diameter EAP application [RFC4072] defines the EAP-Master-
Session-Key and EAP-Key-Name AVPs for the purpose of transporting Session-Key and EAP-Key-Name AVPs for the purpose of transporting
cryptographic keying material derived during the execution of certain cryptographic keying material derived during the execution of certain
EAP [RFC3748] methods (for example, EAP-TLS [RFC5216]). At most one The Extensible Authentication Protocol (EAP) [RFC3748] methods (for
instance of either of these AVPs is allowed in any Diameter message. 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 However, recent work (see, for example, [RFC5295]) has specified
methods to derive other keys from the keying material created during methods to derive other keys from the keying material created during
EAP method execution that may require transport in addition to the EAP method execution that may require transport in addition to the
MSK. In addition, ERP [RFC5296] specifies new keys that may need to MSK. In addition, the EAP Re-authentication Protocol (ERP) [RFC5296]
be transported between Diameter nodes. specifies new keys that may need to be transported between Diameter
nodes.
This note specifies a set of AVPs allowing the transport of multiple This note specifies a set of AVPs allowing the transport of multiple
cryptographic keys in a single Diameter message. cryptographic keys in a single Diameter message.
2. Terminology 2. Terminology
2.1. Standards Language 2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2.2. Technical Terms and Acronyms 2.2. Technical Terms and Acronyms
DER
Diameter EAP request [RFC4072].
DEA
Diameter EAP Answer [RFC4072].
DSRK DSRK
Domain-Specific Root Key [RFC5295]. Domain-Specific Root Key [RFC5295].
DSUSRK
Domain-Specific Usage-Specific Root Key. This is a Usage-Specific
Root Key derived from a DSRK [RFC5295].
EAP
Extensible Authentication Protocol [RFC3748].
EMSK
Extended Master Session Key [RFC3748].
ERP
EAP Re-authentication Protocol [RFC5296].
MSK MSK
Master Session Key [RFC3748]. Master Session Key [RFC3748].
rMSK rMSK
reauthentication MSK [RFC5296]. This is a per-authenticator key, reauthentication MSK [RFC5296]. This is a per-authenticator key,
derived from the rRK (see below). derived from the rRK (see Paragraph 4).
rRK rRK
reauthentication Root Key, derived from the EMSK or DSRK reauthentication Root Key, derived from the EMSK Extended Master
[RFC5296]. Session Key [RFC3748] or DSRK [RFC5296].
USRK
Usage-Specific Root Key [RFC5295]
3. Attribute-Value Pair Definitions 3. Attribute-Value Pair Definitions
This section defines new AVPs for the transport of cryptographic keys This section defines new AVPs for the transport of cryptographic keys
in the Diameter EAP application [RFC4072], as well as other Diameter in the Diameter EAP application [RFC4072], as well as other Diameter
applications. applications.
3.1. Key AVP 3.1. Key AVP
The Key AVP (AVP Code <AC1>) is of type Grouped [RFC3588]. It The Key AVP (AVP Code <AC1>) is of type Grouped [RFC3588]. It
 End of changes. 9 change blocks. 
35 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/