draft-ietf-dime-local-keytran-08.txt   draft-ietf-dime-local-keytran-09.txt 
Network Working Group G. Zorn Network Working Group G. Zorn
Internet-Draft Network Zen Internet-Draft Network Zen
Intended status: Standards Track Q. Wu Intended status: Standards Track Q. Wu
Expires: April 20, 2011 Huawei Expires: October 6, 2011 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
October 17, 2010 April 4, 2011
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-08 draft-ietf-dime-local-keytran-09
Abstract Abstract
Some Authentication, Authorization, and Accounting (AAA) applications Some Authentication, Authorization, and Accounting (AAA) applications
require the transport of cryptographic keying material. This require the transport of cryptographic keying material. This
document specifies a set of Attribute-Value Pairs (AVPs) providing document specifies a set of Attribute-Value Pairs (AVPs) providing
native Diameter support of cryptographic key delivery. native 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 April 20, 2011. This Internet-Draft will expire on October 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 44 skipping to change at page 4, line 44
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
[I-D.ietf-dime-ikev2-psk-diameter].
RSA-KEM (5) RSA-KEM (5)
A symmetric key encrypted using the RSA public key of the A symmetric key encrypted using the RSA public key of the
recipient [RFC5990]. 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 (AVP Code <AC6>) is of type OctetString. It The Key-Name AVP (AVP Code <AC6>) is of type OctetString. It
skipping to change at page 6, line 43 skipping to change at page 6, line 43
Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom
Taylor, Frank Xia, Lionel Morand and Sebastien Decugis for useful Taylor, Frank Xia, Lionel Morand and Sebastien Decugis for useful
comments. comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-dime-rfc3588bis] [I-D.ietf-dime-rfc3588bis]
Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", draft-ietf-dime-rfc3588bis-25 "Diameter Base Protocol", draft-ietf-dime-rfc3588bis-26
(work in progress), September 2010. (work in progress), January 2011.
[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.
[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]
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-03 (work
in progress), August 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. 8 change blocks. 
17 lines changed or deleted 7 lines changed or added

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