draft-ietf-dime-local-keytran-10.txt   draft-ietf-dime-local-keytran-11.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: November 27, 2011 Huawei Expires: December 19, 2011 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
May 26, 2011 June 17, 2011
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-10 draft-ietf-dime-local-keytran-11
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 November 27, 2011. This Internet-Draft will expire on December 19, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 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
skipping to change at page 4, line 36 skipping to change at page 4, line 36
[ 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. This AVP The Key-Type AVP (AVP Code <AC2>) is of type Enumerated. This AVP
identifies the type of the key being sent. The following decimal identifies the type of the key being sent. The following decimal
values are defined in this document: values are defined in this document:
MSK (0) DSRK (0)
The EAP Master Session Key [RFC3748]
DSRK (1)
A Domain-Specific Root Key [RFC5295]. A Domain-Specific Root Key [RFC5295].
rRK (2) rRK (1)
A reauthentication Root Key [RFC5296]. A reauthentication Root Key [RFC5296].
rMSK (3) rMSK (2)
A reauthentication Master Session Key [RFC5296]. A reauthentication Master Session Key [RFC5296].
RSA-KEM (4) RSA-KEM (3)
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
contains an opaque key identifier. Exactly how this name is contains an opaque key identifier. Exactly how this name is
skipping to change at page 6, line 33 skipping to change at page 6, line 33
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 decimal values defined in this 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- document (Section 3.1.1). New values may be assigned for the Key-
Type AVP using the "Specification Required" policy [RFC5226]; once Type AVP using the "Specification Required" policy [RFC5226]; once
values have been assigned, they MUST NOT be deleted, replaced or values have been assigned, they MUST NOT be deleted, replaced or
modified. modified.
6. Acknowledgements 6. Acknowledgements
Thanks to Semyon Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom Thanks to Niclas Comstedt, Semyon Mizikovsky, Hannes Tschofenig, Joe
Taylor, Frank Xia, Lionel Morand, Dan Romascanu and Sebastien Decugis Salowey, Tom Taylor, Frank Xia, Lionel Morand, Dan Romascanu, Bernard
for useful comments. Aboba, Jouni Korhonen and Sebastien Decugis for useful comments,
suggestions and review.
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-26 "Diameter Base Protocol", draft-ietf-dime-rfc3588bis-26
(work in progress), January 2011. (work in progress), January 2011.
 End of changes. 9 change blocks. 
14 lines changed or deleted 12 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/