draft-ietf-dime-local-keytran-02.txt   draft-ietf-dime-local-keytran-03.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: September 5, 2010 Huawei Expires: November 2, 2010 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
March 4, 2010 May 1, 2010
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-02 draft-ietf-dime-local-keytran-03
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
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 2, 2010.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 5, 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
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
described in the BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
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
skipping to change at page 5, line 50 skipping to change at page 5, line 50
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.
3.1.5. Key-SPI 3.1.5. Key-SPI
The Key-SPI AVP (AVP Code <AC5>) is of is of type Unsigned32 and The Key-SPI AVP (AVP Code <AC5>) is of type Unsigned32 and contains a
contains a Security Parameter Index (SPI) value that can be used with Security Parameter Index (SPI) value that can be used with other
other parameters for identifying associated keying material. parameters for identifying associated keying material.
4. Security Considerations 4. 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, as are those in [RFC3588] are also applicable to this document, as are those in
Section 8.4 of RFC 4072 [RFC4072]. Section 8.4 of RFC 4072 [RFC4072].
5. 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
 End of changes. 8 change blocks. 
18 lines changed or deleted 12 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/