idnits 2.17.1 draft-ietf-dime-local-keytran-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 4, 2010) is 5167 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 5296 (Obsoleted by RFC 6696) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn, Ed. 3 Internet-Draft Network Zen 4 Intended status: Standards Track Q. Wu, Ed. 5 Expires: September 5, 2010 Huawei 6 V. Cakulev 7 Alcatel Lucent 8 March 4, 2010 10 Diameter Attribute-Value Pairs for Cryptographic Key Transport 11 draft-ietf-dime-local-keytran-02 13 Abstract 15 Some Authentication, Authorization, and Accounting (AAA) applications 16 require the transport of cryptographic keying material; this document 17 specifies a set of Attribute-Value Pairs (AVPs) providing native 18 Diameter support of cryptographic key delivery. 20 Status of this Memo 22 This Internet-Draft is submitted to IETF in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt. 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 This Internet-Draft will expire on September 5, 2010. 43 Copyright Notice 45 Copyright (c) 2010 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 63 2.2. Technical Terms and Acronyms . . . . . . . . . . . . . . . 3 64 3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . . 4 65 3.1. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 3.1.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . . 4 67 3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 5 68 3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5 69 3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5 70 3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5 71 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 72 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 73 5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 6 74 5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6 75 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 76 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 78 7.2. Informative References . . . . . . . . . . . . . . . . . . 7 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 81 1. Introduction 83 The Diameter EAP application [RFC4072] defines the EAP-Master- 84 Session-Key and EAP-Key-Name AVPs for the purpose of transporting 85 cryptographic keying material derived during the execution of certain 86 EAP [RFC3748] methods (for example, EAP-TLS [RFC5216]). At most one 87 instance of either of these AVPs is allowed in any Diameter message. 89 However, recent work (see, for example, [RFC5295]) has specified 90 methods to derive other keys from the keying material created during 91 EAP method execution that may require transport in addition to the 92 MSK. In addition, ERP [RFC5296] specifies new keys that may need to 93 be transported between Diameter nodes. 95 This note specifies a set of AVPs allowing the transport of multiple 96 cryptographic keys in a single Diameter message. 98 2. Terminology 100 2.1. Standards Language 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 104 document are to be interpreted as described in RFC 2119 [RFC2119]. 106 2.2. Technical Terms and Acronyms 108 DER 109 Diameter EAP request [RFC4072]. 111 DEA 112 Diameter EAP Answer [RFC4072]. 114 DSRK 115 Domain-Specific Root Key [RFC5295]. 117 DSUSRK 118 Domain-Specific Usage-Specific Root Key. This is a Usage-Specific 119 Root Key derived from a DSRK [RFC5295]. 121 EAP 122 Extensible Authentication Protocol [RFC3748]. 124 EMSK 125 Extended Master Session Key [RFC3748]. 127 ERP 128 EAP Re-authentication Protocol [RFC5296]. 130 MSK 131 Master Session Key [RFC3748]. 133 rMSK 134 reauthentication MSK [RFC5296]. This is a per-authenticator key, 135 derived from the rRK (see below). 137 rRK 138 reauthentication Root Key, derived from the EMSK or DSRK 139 [RFC5296]. 141 USRK 142 Usage-Specific Root Key [RFC5295] 144 3. Attribute-Value Pair Definitions 146 This section defines new AVPs for the transport of cryptographic keys 147 in the Diameter EAP application [RFC4072], as well as other Diameter 148 applications. 150 3.1. Key AVP 152 The Key AVP (AVP Code ) is of type Grouped [RFC3588] It contains 153 the name, type and optionally, the usable lifetime of the key, as 154 well as the keying material itself. 156 Key ::= < AVP Header: AC1 > 157 < Key-Type > 158 { Keying-Material } 159 [ Key-Lifetime ] 160 [ Key-Name ] 161 [ Key-SPI ] 162 * [ AVP ] 164 3.1.1. Key-Type AVP 166 The Key-Type AVP (AVP Code ) is of type Enumerated and signifies 167 the type of the key being sent. The following values are defined in 168 this document: 170 MSK (0) 171 The EAP Master Session Key [RFC3748] 173 DSRK (1) 174 A Domain-Specific Root Key [RFC5295]. 176 USRK (2) 177 A Usage Specific Root Key [RFC5295]. 179 rRK (3) 180 A reauthentication Root Key [RFC5296]. 182 rMSK (4) 183 A reauthentication Master Session Key [RFC5296]. 185 DSUSRK (5) A Domain-Specific Usage-Specific Root Key [RFC5295]. 187 If additional values are needed, they are to be assigned by IANA 188 according to the policy stated in Section 5.2 190 3.1.2. Key-Name AVP 192 The Key-Name AVP is of type OctetString. It contains an opaque key 193 identifier. Exactly how this name is generated and used depends on 194 the key type and link layer in question, and is beyond the scope of 195 this document (see [RFC5247] and [RFC5295] for discussions of key 196 name generation in the context of EAP). 198 3.1.3. Keying-Material AVP 200 The Keying-Material AVP (AVP Code ) is of type OctetString. The 201 exact usage of this keying material depends upon several factors, 202 including the link layer in use and the type of the key; it is beyond 203 the scope of this document. 205 3.1.4. Key-Lifetime AVP 207 The Key-Lifetime AVP (AVP Code ) is of type Integer64 [RFC3588] 208 and represents the period of time (in seconds) for which the contents 209 of the Keying-Material AVP Section 3.1.3 is valid. 211 NOTE: 212 Applications using this value SHOULD consider the beginning of the 213 lifetime to be the point in time when the keying material is first 214 used. 216 3.1.5. Key-SPI 218 The Key-SPI AVP (AVP Code ) is of is of type Unsigned32 and 219 contains a Security Parameter Index (SPI) value that can be used with 220 other parameters for identifying associated keying material. 222 4. Security Considerations 224 The security considerations applicable to the Diameter Base Protocol 225 [RFC3588] are also applicable to this document, as are those in 226 Section 8.4 of RFC 4072 [RFC4072]. 228 5. IANA Considerations 230 Upon publication of this memo as an RFC, IANA is requested to assign 231 values as described in the following sections. 233 5.1. AVP Codes 235 Codes must be assigned for the following AVPs using the policy 236 specified in RFC 3588, Section 11.1.1: 238 o Key (, Section 3.1) 240 o Key-Type (, Section 3.1.1) 242 o Keying-Material (, Section 3.1.3) 244 o Key-Lifetime (, Section 3.1.4) 246 o Key-SPI (, Section 3.1.5) 248 5.2. AVP Values 250 IANA is requested to create a new registry for values assigned to the 251 Key-Type AVP and populated with the values defined in this document 252 (Section 3.1.1). New values may be assigned for the Key-Type AVP 253 using the "Expert Review" policy [RFC5226]; once values have been 254 assigned, they MUST NOT be deleted, replaced, modified or deprecated. 256 6. Acknowledgements 258 Thanks to Semyon Mizikovsky, Hannes Tschofenig and Sebastien Decugis 259 for useful comments. 261 7. References 263 7.1. Normative References 265 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 266 Requirement Levels", BCP 14, RFC 2119, March 1997. 268 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 269 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 271 [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. 272 Levkowetz, "Extensible Authentication Protocol (EAP)", 273 RFC 3748, June 2004. 275 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 276 Authentication Protocol (EAP) Application", RFC 4072, 277 August 2005. 279 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 280 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 281 May 2008. 283 7.2. Informative References 285 [RFC5216] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS 286 Authentication Protocol", RFC 5216, March 2008. 288 [RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible 289 Authentication Protocol (EAP) Key Management Framework", 290 RFC 5247, August 2008. 292 [RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri, 293 "Specification for the Derivation of Root Keys from an 294 Extended Master Session Key (EMSK)", RFC 5295, 295 August 2008. 297 [RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re- 298 authentication Protocol (ERP)", RFC 5296, August 2008. 300 Authors' Addresses 302 Glen Zorn (editor) 303 Network Zen 304 1463 East Republican Street 305 #358 306 Seattle, Washington 98112 307 US 309 Email: gwz@net-zen.net 310 Qin Wu (editor) 311 Huawei Technologies Co., Ltd. 312 Site B, Floor 12F, Huihong Mansion, No.91 Baixia Rd. 313 Nanjing, JiangSu 210001 314 China 316 Phone: +86-25-84565892 317 Email: Sunseawq@huawei.com 319 Violeta Cakulev 320 Alcatel Lucent 321 600 Mountain Ave. 322 3D-517 323 Murray Hill, NJ 07974 324 US 326 Phone: +1 908 582 3207 327 Email: violeta.cakulev@alcatel-lucent.com