draft-ietf-dime-local-keytran-05.txt   draft-ietf-dime-local-keytran-06.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 27, 2010 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
May 25, 2010 May 26, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-05 draft-ietf-dime-local-keytran-06
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 36 skipping to change at page 1, line 36
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 November 26, 2010. This Internet-Draft will expire on November 27, 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 3, line 42 skipping to change at page 3, line 42
2.2. Technical Terms and Acronyms 2.2. Technical Terms and Acronyms
DSRK DSRK
Domain-Specific Root Key [RFC5295]. Domain-Specific Root Key [RFC5295].
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 Paragraph 4). derived from the rRK (below).
rRK rRK
reauthentication Root Key, derived from the EMSK Extended Master reauthentication Root Key, derived from the EMSK Extended Master
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.
skipping to change at page 4, line 29 skipping to change at page 4, line 29
< 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 and signifies
the type of the key being sent. The following values are defined in the type of the key being sent. The following decimal values are
this document: 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) A pre-shared key for use in IKE-V2 key exchange IKEv2-PSK (4)
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].
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 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 usage in question, and is beyond the scope of this the key type and usage in question, and is beyond the scope of this
skipping to change at page 5, line 24 skipping to change at page 5, line 24
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; it 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 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 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
skipping to change at page 6, line 23 skipping to change at page 6, line 23
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)
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 decimal values defined in this
(Section 3.1.1). New values may be assigned for the Key-Type AVP document (Section 3.1.1). New values may be assigned for the Key-
using the "Expert Review" policy [RFC5226]; once values have been Type AVP using the "Expert Review" policy [RFC5226]; once values have
assigned, they MUST NOT be deleted, replaced, modified or deprecated. been assigned, they MUST NOT be deleted, replaced, modified or
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 and Sebastien Decugis for useful comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
 End of changes. 9 change blocks. 
13 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/