draft-ietf-dime-local-keytran-13.txt   draft-ietf-dime-local-keytran-14.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: February 16, 2012 Huawei Expires: February 20, 2012 Huawei
V. Cakulev V. Cakulev
Alcatel Lucent Alcatel Lucent
August 15, 2011 August 19, 2011
Diameter Attribute-Value Pairs for Cryptographic Key Transport Diameter Attribute-Value Pairs for Cryptographic Key Transport
draft-ietf-dime-local-keytran-13 draft-ietf-dime-local-keytran-14
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 February 16, 2012. This Internet-Draft will expire on February 20, 2012.
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 2, line 22 skipping to change at page 2, line 22
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
3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 4 3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 4
3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5 3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5
3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5 3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5
3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5 3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6 5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
The Diameter EAP application [RFC4072] defines the EAP-Master- The Diameter EAP application [RFC4072] defines the EAP-Master-
skipping to change at page 5, line 9 skipping to change at page 5, line 9
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
generated and used depends on the key type and usage in question, and generated and used depends on the key type and usage in question, and
is beyond the scope of this document (see [RFC5247] and [RFC5295] for is beyond the scope of this document (see [RFC5247] and [RFC5295] for
discussions of key name generation in the context of EAP). discussions of key name generation in the context of EAP).
3.1.3. Keying-Material AVP 3.1.3. Keying-Material AVP
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 and is beyond including the type of the key and the link layer in use and 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 Unsigned32 and The Key-Lifetime AVP (AVP Code <AC4>) is of type Unsigned32 and
represents the period of time (in seconds) for which the contents of represents the period of time (in seconds) for which the contents of
the Keying-Material AVP (Section 3.1.3) is valid. 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
skipping to change at page 5, line 34 skipping to change at page 5, line 34
session lifetime (see section 8.13 of [I-D.ietf-dime-rfc3588bis]. session lifetime (see section 8.13 of [I-D.ietf-dime-rfc3588bis].
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
associated keying material. associated keying material.
4. Security Considerations 4. Security Considerations
Transporting keys is a security-sensitive action. Some forms of
keying material are already protected and can be sent safely over the
open Internet. However, if a Key AVP contains Keying-Material that
is not already protected, then the Diameter messages containing that
Key AVP MUST only be sent protected via mutually authenticated TLS or
IPsec.
The security considerations applicable to the Diameter Base Protocol The security considerations applicable to the Diameter Base Protocol
[I-D.ietf-dime-rfc3588bis] are also applicable to this document, as [I-D.ietf-dime-rfc3588bis] are also applicable to this document, as
are those in Section 8.4 of RFC 4072 [RFC4072]. are those in 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
values as described in the following sections. values as described in the following sections.
5.1. AVP Codes 5.1. AVP Codes
 End of changes. 7 change blocks. 
6 lines changed or deleted 13 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/