draft-ietf-dime-local-keytran-06.txt   draft-ietf-dime-local-keytran-07.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 27, 2010 Huawei Expires: January 2, 2011 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
May 26, 2010 July 1, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-06 draft-ietf-dime-local-keytran-07
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 27, 2010. This Internet-Draft will expire on January 2, 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 4, line 48 skipping to change at page 4, line 48
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)
A symmetric keying material encrypted using the RSA public key of
the recipient [I-D.ietf-smime-cms-rsa-kem].
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
document (see [RFC5247] and [RFC5295] for discussions of key name document (see [RFC5247] and [RFC5295] for discussions of key name
generation in the context of EAP). generation in the context of EAP).
3.1.3. Keying-Material AVP 3.1.3. Keying-Material AVP
skipping to change at page 7, line 17 skipping to change at page 7, line 17
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-02 (work
in progress), March 2010. in progress), March 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,
 End of changes. 7 change blocks. 
5 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/