draft-ietf-dime-local-keytran-07.txt   draft-ietf-dime-local-keytran-08.txt 
Network Working Group G. Zorn, Ed. Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track Q. Wu, Ed. Intended status: Standards Track Q. Wu
Expires: January 2, 2011 Huawei Expires: April 20, 2011 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
July 1, 2010 October 17, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-07 draft-ietf-dime-local-keytran-08
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
specifies a set of Attribute-Value Pairs (AVPs) providing native document specifies a set of Attribute-Value Pairs (AVPs) providing
Diameter support of cryptographic key delivery. native Diameter support of cryptographic key delivery.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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."
This Internet-Draft will expire on January 2, 2011. This Internet-Draft will expire on April 20, 2011.
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 3, line 10 skipping to change at page 3, line 10
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
The Extensible Authentication Protocol (EAP) [RFC3748] methods (for Extensible Authentication Protocol (EAP) [RFC3748] methods (for
example, EAP-TLS [RFC5216]). At most one instance of either of these example, EAP-TLS [RFC5216]). At most one instance of either of these
AVPs is allowed in any Diameter message. 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, the EAP Re-authentication Protocol (ERP) [RFC5296] MSK. In addition, the EAP Re-authentication Protocol (ERP) [RFC5296]
specifies new keys that may need to be transported between Diameter specifies new keys that may need to be transported between Diameter
nodes. nodes.
skipping to change at page 4, line 13 skipping to change at page 4, line 13
Session Key [RFC3748] or DSRK [RFC5296]. Session Key [RFC3748] or DSRK [RFC5296].
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. It contains the
contains the type and keying material and, optionally, an indication type and keying material and, optionally, an indication of the usable
of the usable lifetime of the key, the name of the key and a Security lifetime of the key, the name of the key and a Security Parameter
Parameter Index (SPI) with which the key is associated. Index (SPI) with which the key is associated.
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 ] [ 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. This AVP
the type of the key being sent. The following decimal values are identifies the type of the key being sent. The following decimal
defined in this document: values are defined in this document:
MSK (0) MSK (0)
The EAP Master Session Key [RFC3748] The EAP Master Session Key [RFC3748]
DSRK (1) DSRK (1)
A Domain-Specific Root Key [RFC5295]. A Domain-Specific Root Key [RFC5295].
rRK (2) rRK (2)
A reauthentication Root Key [RFC5296]. A reauthentication Root Key [RFC5296].
rMSK (3) rMSK (3)
A reauthentication Master Session Key [RFC5296]. A reauthentication Master Session Key [RFC5296].
IKEv2-PSK (4) IKEv2-PSK (4)
A pre-shared key for use in IKE-V2 key exchange A pre-shared key for use in IKE-V2 key exchange
[I-D.ietf-dime-ikev2-psk-diameter]. [I-D.ietf-dime-ikev2-psk-diameter].
RSA-KEM (5) RSA-KEM (5)
A symmetric keying material encrypted using the RSA public key of A symmetric key encrypted using the RSA public key of the
the recipient [I-D.ietf-smime-cms-rsa-kem]. recipient [RFC5990].
If additional values are needed, they are to be assigned by IANA If additional values are needed, they are to be assigned by IANA
according to the policy stated in Section 5.2, according to the policy stated in Section 5.2,
3.1.2. Key-Name AVP 3.1.2. Key-Name AVP
The Key-Name AVP is of type OctetString. It contains an opaque key The Key-Name AVP (AVP Code <AC6>) is of type OctetString. It
identifier. Exactly how this name is generated and used depends on contains an opaque key identifier. Exactly how this name is
the key type and usage in question, and is beyond the scope of this generated and used depends on the key type and usage in question, and
document (see [RFC5247] and [RFC5295] for discussions of key name is beyond the scope of this document (see [RFC5247] and [RFC5295] for
generation in the context of EAP). discussions of key name generation in the context of EAP).
3.1.3. Keying-Material AVP 3.1.3. Keying-Material AVP
The Keying-Material AVP (AVP Code <AC3>) is of type OctetString. The The Keying-Material AVP (AVP Code <AC3>) is of type OctetString. The
exact usage of this keying material depends upon several factors, exact usage of this keying material depends upon several factors,
including the link layer in use and the type of the key; it is beyond including the link layer in use and the type of the key and is beyond
the scope of this document. the scope of this document.
3.1.4. Key-Lifetime AVP 3.1.4. Key-Lifetime AVP
The Key-Lifetime AVP (AVP Code <AC4>) is of type Integer64 [RFC3588] The Key-Lifetime AVP (AVP Code <AC4>) is of type Unsigned32 and
and represents the period of time (in seconds) for which the contents represents the period of time (in seconds) for which the contents of
of the Keying-Material AVP (Section 3.1.3) is valid. 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 message containing the lifetime to be the point in time when the message containing the
keying material is received. keying material is received.
3.1.5. Key-SPI 3.1.5. Key-SPI
The Key-SPI AVP (AVP Code <AC5>) is of type Unsigned32 and contains a The Key-SPI AVP (AVP Code <AC5>) is of type Unsigned32 and contains a
SPI value that can be used with other parameters for identifying SPI value that can be used with other parameters for identifying
associated keying material. 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 [I-D.ietf-dime-rfc3588bis] are also applicable to this document, as
Section 8.4 of RFC 4072 [RFC4072]. are those in 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 [I-D.ietf-dime-rfc3588bis], 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) o Key-SPI (<AC5>, Section 3.1.5)
o Key-Name (<AC6>, Section 3.1.2)
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 decimal values defined in this Key-Type AVP and populated with the decimal values defined in this
document (Section 3.1.1). New values may be assigned for the Key- document (Section 3.1.1). New values may be assigned for the Key-
Type AVP using the "Expert Review" policy [RFC5226]; once values have Type AVP using the "Expert Review" policy [RFC5226]; once values have
been assigned, they MUST NOT be deleted, replaced, modified or been assigned, they MUST NOT be deleted, replaced, modified or
deprecated. deprecated.
6. Acknowledgements 6. Acknowledgements
Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom
Taylor, Frank Xia and Sebastien Decugis for useful comments. Taylor, Frank Xia, Lionel Morand and Sebastien Decugis for useful
comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-dime-rfc3588bis]
Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", draft-ietf-dime-rfc3588bis-25
(work in progress), September 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
Levkowetz, "Extensible Authentication Protocol (EAP)", Levkowetz, "Extensible Authentication Protocol (EAP)",
RFC 3748, June 2004. RFC 3748, June 2004.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072, Authentication Protocol (EAP) Application", RFC 4072,
August 2005. August 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
7.2. Informative References 7.2. Informative References
[I-D.ietf-dime-ikev2-psk-diameter] [I-D.ietf-dime-ikev2-psk-diameter]
Cakulev, V. and A. Lior, "Diameter IKEv2 PSK: Pre-Shared Cakulev, V. and A. Lior, "Diameter IKEv2 PSK: Pre-Shared
Secret-based Support for IKEv2 Server to Diameter Server Secret-based Support for IKEv2 Server to Diameter Server
Interaction", draft-ietf-dime-ikev2-psk-diameter-02 (work Interaction", draft-ietf-dime-ikev2-psk-diameter-03 (work
in progress), March 2010. in progress), August 2010.
[I-D.ietf-smime-cms-rsa-kem]
Brainard, J., Turner, S., Randall, J., and B. Kaliski,
"Use of the RSA-KEM Key Transport Algorithm in CMS",
draft-ietf-smime-cms-rsa-kem-13 (work in progress),
May 2010.
[RFC5216] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS [RFC5216] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS
Authentication Protocol", RFC 5216, March 2008. Authentication Protocol", RFC 5216, March 2008.
[RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible [RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible
Authentication Protocol (EAP) Key Management Framework", Authentication Protocol (EAP) Key Management Framework",
RFC 5247, August 2008. RFC 5247, August 2008.
[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.
[RFC5990] Randall, J., Kaliski, B., Brainard, J., and S. Turner,
"Use of the RSA-KEM Key Transport Algorithm in the
Cryptographic Message Syntax (CMS)", RFC 5990,
September 2010.
Authors' Addresses Authors' Addresses
Glen Zorn (editor) Glen Zorn
Network Zen Network Zen
1463 East Republican Street 227/358 Thanon Sanphawut
#358 Bang Na, Bangkok 10260
Seattle, Washington 98112 Thailand
US
Phone: +66 (0) 87-040-4617
Email: gwz@net-zen.net Email: gwz@net-zen.net
Qin Wu (editor)
Qin Wu
Huawei Technologies Co., Ltd. Huawei Technologies Co., Ltd.
Site B, Floor 12F, Huihong Mansion, No.91 Baixia Rd. 101 Software Avenue, Yuhua District
Nanjing, JiangSu 210001 Nanjing, Jiangsu 21001
China China
Phone: +86-25-84565892 Phone: +86-25-56623633
Email: Sunseawq@huawei.com Email: sunseawq@huawei.com
Violeta Cakulev Violeta Cakulev
Alcatel Lucent Alcatel Lucent
600 Mountain Ave. 600 Mountain Ave.
3D-517 3D-517
Murray Hill, NJ 07974 Murray Hill, NJ 07974
US US
Phone: +1 908 582 3207 Phone: +1 908 582 3207
Email: violeta.cakulev@alcatel-lucent.com Email: violeta.cakulev@alcatel-lucent.com
 End of changes. 27 change blocks. 
53 lines changed or deleted 58 lines changed or added

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