draft-ietf-dime-local-keytran-00.txt   draft-ietf-dime-local-keytran-01.txt 
Network Working Group Q. Wu, Ed. Network Working Group Q. Wu, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track G. Zorn, Ed. Intended status: Standards Track G. Zorn, Ed.
Expires: July 12, 2010 Network Zen Expires: August 1, 2010 Network Zen
January 8, 2010 January 28, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-00 draft-ietf-dime-local-keytran-01
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 40
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 July 12, 2010. This Internet-Draft will expire on August 1, 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 23
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. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6
6.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 7 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7
8.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.
skipping to change at page 4, line 44 skipping to change at page 4, line 44
Key ::= < AVP Header: AC1 > Key ::= < AVP Header: AC1 >
< Key-Type > < Key-Type >
{ Keying-Material } { Keying-Material }
[ Key-Lifetime ] [ Key-Lifetime ]
[ Key-Name ] [ Key-Name ]
* [ 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 Key-Type AVP MAY be included in the type of the key being sent. The following values are defined in
a DER command as a signal that a certain type of key is required in this document:
the response (e.g., to support ERP). The following 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].
USRK (2) USRK (2)
A Usage Specific Root Key [RFC5295]. A Usage Specific Root Key [RFC5295].
rRK (3) rRK (3)
A reauthentication Root Key [RFC5296]. A reauthentication Root Key [RFC5296].
rMSK (4) rMSK (4)
A reauthentication Master Session Key [RFC5296]. A reauthentication Master Session Key [RFC5296].
DSUSRK (5) A Domain-Specific Usage-Specific Root Key [RFC5295]. DSUSRK (5) A Domain-Specific Usage-Specific Root Key [RFC5295].
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 6.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 is of type OctetString. It contains an opaque key
identifier. Exactly how this name is generated and used depends on identifier. Exactly how this name is generated and used depends on
the key type and link layer in question, and is beyond the scope of the key type and link layer in question, and is beyond the scope of
this document (see [RFC5247] and [RFC5295] for discussions of key this document (see [RFC5247] and [RFC5295] for discussions of key
name generation in the context of EAP). name generation in the context of EAP).
3.1.3. Keying-Material AVP 3.1.3. Keying-Material AVP
skipping to change at page 6, line 5 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.
4. AVP Occurrence Table 4. Security Considerations
The following table lists the AVPs that MAY be present in the DER and
DEA commands [RFC4072].
+---------------+
| Command-Code |
+-+-----+-----+-+
AVP Name | DER | DEA |
-------------------------------|-----+-----+
Key | 0 | 0+ |
Key-Type | 0+ | 0 |
Key-Name | 0-1 | 0-1 |
+-----+-----+
DER and DEA Commands AVP Table
5. 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. [RFC3588] are also applicable to this document, as are those in
Section 8.4 of RFC 4072 [RFC4072].
6. 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.
6.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
6.2. AVP Values 5.2. AVP Values
New values may be assigned for the Key-Type AVP (Section 3.1.1) using IANA is requested to create a new registry for values assigned to the
the "First Come First Served" policy [RFC5226]. 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
using the "Expert Review" policy [RFC5226].
7. Acknowledgements 6. Acknowledgements
Thanks to Semyon Mizikovsky and Sebastien Decugis for useful Thanks to Semyon Mizikovsky, Hannes Tschofenig and Sebastien Decugis
comments. for useful comments.
8. References 7. References
8.1. Normative References 7.1. Normative References
[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. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 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.
8.2. Informative References 7.2. Informative References
[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
 End of changes. 17 change blocks. 
48 lines changed or deleted 31 lines changed or added

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