draft-ietf-dime-local-keytran-01.txt   draft-ietf-dime-local-keytran-02.txt 
Network Working Group Q. Wu, Ed. Network Working Group G. Zorn, Ed.
Internet-Draft Huawei Internet-Draft Network Zen
Intended status: Standards Track G. Zorn, Ed. Intended status: Standards Track Q. Wu, Ed.
Expires: August 1, 2010 Network Zen Expires: September 5, 2010 Huawei
January 28, 2010 V. Cakulev
Alcatel Lucent
March 4, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-01 draft-ietf-dime-local-keytran-02
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 1, line 40 skipping to change at page 1, line 42
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 1, 2010. This Internet-Draft will expire on September 5, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 25
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
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 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 EAP [RFC3748] methods (for example, EAP-TLS [RFC5216]). At most one
instance of either of these AVPs is allowed in any Diameter message. instance of either of these AVPs is allowed in any Diameter message.
However, recent work [RFC5295] has specified methods to derive other However, recent work (see, for example, [RFC5295]) has specified
keys from the keying material created during EAP method execution methods to derive other keys from the keying material created during
that may require transport in addition to the MSK. In addition, ERP EAP method execution that may require transport in addition to the
[RFC5296] specifies new keys that may need to be transported between MSK. In addition, ERP [RFC5296] specifies new keys that may need to
Diameter nodes. 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
skipping to change at page 4, line 39 skipping to change at page 4, line 39
The Key AVP (AVP Code <AC1>) is of type Grouped [RFC3588] It contains The Key AVP (AVP Code <AC1>) is of type Grouped [RFC3588] It contains
the name, type and optionally, the usable lifetime of the key, as the name, type and optionally, the usable lifetime of the key, as
well as the keying material itself. well as the keying material itself.
Key ::= < AVP Header: AC1 > Key ::= < AVP Header: AC1 >
< Key-Type > < Key-Type >
{ Keying-Material } { Keying-Material }
[ Key-Lifetime ] [ Key-Lifetime ]
[ Key-Name ] [ Key-Name ]
[ Key-SPI ]
* [ AVP ] * [ AVP ]
3.1.1. Key-Type AVP 3.1.1. Key-Type AVP
The Key-Type AVP (AVP Code <AC2>) is of type Enumerated and signifies The Key-Type AVP (AVP Code <AC2>) is of type Enumerated and signifies
the type of the key being sent. The following values are defined in the type of the key being sent. The following values are defined in
this document: this document:
MSK (0) MSK (0)
The EAP Master Session Key [RFC3748] The EAP Master Session Key [RFC3748]
skipping to change at page 5, line 48 skipping to change at page 5, line 48
The Key-Lifetime AVP (AVP Code <AC4>) is of type Integer64 [RFC3588] The Key-Lifetime AVP (AVP Code <AC4>) is of type Integer64 [RFC3588]
and represents the period of time (in seconds) for which the contents and represents the period of time (in seconds) for which the contents
of the Keying-Material AVP Section 3.1.3 is valid. of the Keying-Material AVP Section 3.1.3 is valid.
NOTE: NOTE:
Applications using this value SHOULD consider the beginning of the Applications using this value SHOULD consider the beginning of the
lifetime to be the point in time when the keying material is first lifetime to be the point in time when the keying material is first
used. used.
3.1.5. Key-SPI
The Key-SPI AVP (AVP Code <AC5>) is of is of type Unsigned32 and
contains a Security Parameter Index (SPI) value that can be used with
other parameters for identifying associated keying material.
4. Security Considerations 4. Security Considerations
The security considerations applicable to the Diameter Base Protocol The security considerations applicable to the Diameter Base Protocol
[RFC3588] are also applicable to this document, as are those in [RFC3588] are also applicable to this document, as are those in
Section 8.4 of RFC 4072 [RFC4072]. Section 8.4 of RFC 4072 [RFC4072].
5. IANA Considerations 5. IANA Considerations
Upon publication of this memo as an RFC, IANA is requested to assign Upon publication of this memo as an RFC, IANA is requested to assign
values as described in the following sections. values as described in the following sections.
5.1. AVP Codes 5.1. AVP Codes
Codes must be assigned for the following AVPs using the policy Codes must be assigned for the following AVPs using the policy
specified in RFC 3588, Section 11.1.1: specified in RFC 3588, Section 11.1.1:
o Key (<AC1>, Section 3.1) o Key (<AC1>, Section 3.1)
o Key-Type (<AC2>, Section 3.1.1) o Key-Type (<AC2>, Section 3.1.1)
o Keying-Material (<AC3>, Section 3.1.3 o Keying-Material (<AC3>, Section 3.1.3)
o Key-Lifetime (<AC4>, Section 3.1.4 o Key-Lifetime (<AC4>, Section 3.1.4)
o Key-SPI (<AC5>, Section 3.1.5)
5.2. AVP Values 5.2. AVP Values
IANA is requested to create a new registry for values assigned to the IANA is requested to create a new registry for values assigned to the
Key-Type AVP and populated with the values defined in this document Key-Type AVP and populated with the values defined in this document
(Section 3.1.1. New values may be assigned for the Key-Type AVP (Section 3.1.1). New values may be assigned for the Key-Type AVP
using the "Expert Review" policy [RFC5226]. using the "Expert Review" policy [RFC5226]; once values have been
assigned, they MUST NOT be deleted, replaced, modified or deprecated.
6. Acknowledgements 6. Acknowledgements
Thanks to Semyon Mizikovsky, Hannes Tschofenig and Sebastien Decugis Thanks to Semyon Mizikovsky, Hannes Tschofenig and Sebastien Decugis
for useful comments. for useful comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
skipping to change at page 7, line 32 skipping to change at page 7, line 39
[RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri, [RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri,
"Specification for the Derivation of Root Keys from an "Specification for the Derivation of Root Keys from an
Extended Master Session Key (EMSK)", RFC 5295, Extended Master Session Key (EMSK)", RFC 5295,
August 2008. August 2008.
[RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re- [RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re-
authentication Protocol (ERP)", RFC 5296, August 2008. authentication Protocol (ERP)", RFC 5296, August 2008.
Authors' Addresses Authors' Addresses
Glen Zorn (editor)
Network Zen
1463 East Republican Street
#358
Seattle, Washington 98112
US
Email: gwz@net-zen.net
Qin Wu (editor) Qin Wu (editor)
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
Site B, Floor 12F, Huihong Mansion, No.91 Baixia Rd. Site B, Floor 12F, Huihong Mansion, No.91 Baixia Rd.
Nanjing, JiangSu 210001 Nanjing, JiangSu 210001
China China
Phone: +86-25-84565892 Phone: +86-25-84565892
Email: Sunseawq@huawei.com Email: Sunseawq@huawei.com
Glen Zorn (editor) Violeta Cakulev
Network Zen Alcatel Lucent
1463 East Republican Street 600 Mountain Ave.
#358 3D-517
Seattle, Washington 98112 Murray Hill, NJ 07974
USA US
Email: gwz@net-zen.net Phone: +1 908 582 3207
Email: violeta.cakulev@alcatel-lucent.com
 End of changes. 13 change blocks. 
23 lines changed or deleted 44 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/