Network Working Group G. Zorn, Ed.
Internet-Draft Network Zen
Intended status: Standards Track Q. Wu, Ed.
Expires: November 27, 2010 Huawei
V. Cakulev
Alcatel Lucent
May 26, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-06
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 Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 27, 2010.
Copyright Notice
Copyright (c) 2010 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
Zorn, et al. Expires November 27, 2010 [Page 1]
Internet-Draft Diameter Key Transport AVPs May 2010
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3
2.2. Technical Terms and Acronyms . . . . . . . . . . . . . . . 3
3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . . 4
3.1. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . . 4
3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 5
3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5
3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5
3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
Zorn, et al. Expires November 27, 2010 [Page 2]
Internet-Draft Diameter Key Transport AVPs May 2010
1. Introduction
The Diameter 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
The 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
MSK. In addition, the EAP Re-authentication Protocol (ERP) [RFC5296]
specifies new keys that may need to be transported between Diameter
nodes.
This note specifies a set of AVPs allowing the transport of multiple
cryptographic keys in a single Diameter message.
2. Terminology
2.1. Standards Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2.2. Technical Terms and Acronyms
DSRK
Domain-Specific Root Key [RFC5295].
MSK
Master Session Key [RFC3748].
rMSK
reauthentication MSK [RFC5296]. This is a per-authenticator key,
derived from the rRK (below).
rRK
reauthentication Root Key, derived from the EMSK Extended Master
Session Key [RFC3748] or DSRK [RFC5296].
Zorn, et al. Expires November 27, 2010 [Page 3]
Internet-Draft Diameter Key Transport AVPs May 2010
3. Attribute-Value Pair Definitions
This section defines new AVPs for the transport of cryptographic keys
in the Diameter EAP application [RFC4072], as well as other Diameter
applications.
3.1. Key AVP
The Key AVP (AVP Code <AC1>) is of type Grouped [RFC3588]. It
contains the type and keying material and, optionally, an indication
of the usable lifetime of the key, the name of the key and a Security
Parameter Index (SPI) with which the key is associated.
Key ::= < AVP Header: AC1 >
< Key-Type >
{ Keying-Material }
[ Key-Lifetime ]
[ Key-Name ]
[ Key-SPI ]
* [ AVP ]
3.1.1. Key-Type AVP
The Key-Type AVP (AVP Code <AC2>) is of type Enumerated and signifies
the type of the key being sent. The following decimal values are
defined in this document:
MSK (0)
The EAP Master Session Key [RFC3748]
DSRK (1)
A Domain-Specific Root Key [RFC5295].
rRK (2)
A reauthentication Root Key [RFC5296].
rMSK (3)
A reauthentication Master Session Key [RFC5296].
IKEv2-PSK (4)
A pre-shared key for use in IKE-V2 key exchange
[I-D.ietf-dime-ikev2-psk-diameter].
If additional values are needed, they are to be assigned by IANA
according to the policy stated in Section 5.2
Zorn, et al. Expires November 27, 2010 [Page 4]
Internet-Draft Diameter Key Transport AVPs May 2010
3.1.2. Key-Name AVP
The Key-Name AVP is of type OctetString. It contains an opaque key
identifier. Exactly how this name is generated and used depends on
the key type and usage in question, and is beyond the scope of this
document (see [RFC5247] and [RFC5295] for discussions of key name
generation in the context of EAP).
3.1.3. Keying-Material AVP
The Keying-Material AVP (AVP Code <AC3>) is of type OctetString. The
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
the scope of this document.
3.1.4. Key-Lifetime AVP
The Key-Lifetime AVP (AVP Code <AC4>) is of type Integer64 [RFC3588]
and represents the period of time (in seconds) for which the contents
of the Keying-Material AVP (Section 3.1.3) is valid.
NOTE:
Applications using this value SHOULD consider the beginning of the
lifetime to be the point in time when the message containing the
keying material is received.
3.1.5. Key-SPI
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
associated keying material.
4. Security Considerations
The security considerations applicable to the Diameter Base Protocol
[RFC3588] are also applicable to this document, as are those in
Section 8.4 of RFC 4072 [RFC4072].
5. IANA Considerations
Upon publication of this memo as an RFC, IANA is requested to assign
values as described in the following sections.
Zorn, et al. Expires November 27, 2010 [Page 5]
Internet-Draft Diameter Key Transport AVPs May 2010
5.1. AVP Codes
Codes must be assigned for the following AVPs using the policy
specified in RFC 3588, Section 11.1.1:
o Key (<AC1>, Section 3.1)
o Key-Type (<AC2>, Section 3.1.1)
o Keying-Material (<AC3>, Section 3.1.3)
o Key-Lifetime (<AC4>, Section 3.1.4)
o Key-SPI (<AC5>, Section 3.1.5)
5.2. AVP Values
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
document (Section 3.1.1). New values may be assigned for the Key-
Type AVP using the "Expert Review" policy [RFC5226]; once values have
been assigned, they MUST NOT be deleted, replaced, modified or
deprecated.
6. Acknowledgements
Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom
Taylor, Frank Xia and Sebastien Decugis for useful comments.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
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.
Levkowetz, "Extensible Authentication Protocol (EAP)",
RFC 3748, June 2004.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072,
August 2005.
Zorn, et al. Expires November 27, 2010 [Page 6]
Internet-Draft Diameter Key Transport AVPs May 2010
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
7.2. Informative References
[I-D.ietf-dime-ikev2-psk-diameter]
Cakulev, V. and A. Lior, "Diameter IKEv2 PSK: Pre-Shared
Secret-based Support for IKEv2 Server to Diameter Server
Interaction", draft-ietf-dime-ikev2-psk-diameter-02 (work
in progress), March 2010.
[RFC5216] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS
Authentication Protocol", RFC 5216, March 2008.
[RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible
Authentication Protocol (EAP) Key Management Framework",
RFC 5247, August 2008.
[RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri,
"Specification for the Derivation of Root Keys from an
Extended Master Session Key (EMSK)", RFC 5295,
August 2008.
[RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re-
authentication Protocol (ERP)", RFC 5296, August 2008.
Authors' Addresses
Glen Zorn (editor)
Network Zen
1463 East Republican Street
#358
Seattle, Washington 98112
US
Email: gwz@net-zen.net
Zorn, et al. Expires November 27, 2010 [Page 7]
Internet-Draft Diameter Key Transport AVPs May 2010
Qin Wu (editor)
Huawei Technologies Co., Ltd.
Site B, Floor 12F, Huihong Mansion, No.91 Baixia Rd.
Nanjing, JiangSu 210001
China
Phone: +86-25-84565892
Email: Sunseawq@huawei.com
Violeta Cakulev
Alcatel Lucent
600 Mountain Ave.
3D-517
Murray Hill, NJ 07974
US
Phone: +1 908 582 3207
Email: violeta.cakulev@alcatel-lucent.com
Zorn, et al. Expires November 27, 2010 [Page 8]
