idnits 2.17.1 draft-ietf-dime-local-keytran-13.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 (August 15, 2011) is 4631 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-34) exists of draft-ietf-dime-rfc3588bis-26 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- Obsolete informational reference (is this intentional?): RFC 5296 (Obsoleted by RFC 6696) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group G. Zorn 3 Internet-Draft Network Zen 4 Intended status: Standards Track Q. Wu 5 Expires: February 16, 2012 Huawei 6 V. Cakulev 7 Alcatel Lucent 8 August 15, 2011 10 Diameter Attribute-Value Pairs for Cryptographic Key Transport 11 draft-ietf-dime-local-keytran-13 13 Abstract 15 Some Authentication, Authorization, and Accounting (AAA) applications 16 require the transport of cryptographic keying material. This 17 document specifies a set of Attribute-Value Pairs (AVPs) providing 18 native Diameter support of cryptographic key delivery. 20 Status of this Memo 22 This Internet-Draft is submitted 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). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 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 This Internet-Draft will expire on February 16, 2012. 37 Copyright Notice 39 Copyright (c) 2011 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2.1. Standards Language . . . . . . . . . . . . . . . . . . . . 3 57 2.2. Technical Terms and Acronyms . . . . . . . . . . . . . . . 3 58 3. Attribute-Value Pair Definitions . . . . . . . . . . . . . . . 4 59 3.1. Key AVP . . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3.1.1. Key-Type AVP . . . . . . . . . . . . . . . . . . . . . 4 61 3.1.2. Key-Name AVP . . . . . . . . . . . . . . . . . . . . . 4 62 3.1.3. Keying-Material AVP . . . . . . . . . . . . . . . . . . 5 63 3.1.4. Key-Lifetime AVP . . . . . . . . . . . . . . . . . . . 5 64 3.1.5. Key-SPI . . . . . . . . . . . . . . . . . . . . . . . . 5 65 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 66 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 67 5.1. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 5.2. AVP Values . . . . . . . . . . . . . . . . . . . . . . . . 6 69 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 70 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 72 7.2. Informative References . . . . . . . . . . . . . . . . . . 7 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 75 1. Introduction 77 The Diameter EAP application [RFC4072] defines the EAP-Master- 78 Session-Key and EAP-Key-Name AVPs for the purpose of transporting 79 cryptographic keying material derived during the execution of certain 80 Extensible Authentication Protocol (EAP) [RFC3748] methods (for 81 example, EAP-TLS [RFC5216]). At most one instance of either of these 82 AVPs is allowed in any Diameter message. 84 However, recent work (see, for example, [RFC5295]) has specified 85 methods to derive other keys from the keying material created during 86 EAP method execution that may require transport in addition to the 87 MSK. In addition, the EAP Re-authentication Protocol (ERP) [RFC5296] 88 specifies new keys that may need to be transported between Diameter 89 nodes. 91 This note specifies a set of AVPs allowing the transport of multiple 92 cryptographic keys in a single Diameter message. 94 2. Terminology 96 2.1. Standards Language 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in RFC 2119 [RFC2119]. 102 2.2. Technical Terms and Acronyms 104 DSRK 105 Domain-Specific Root Key [RFC5295]. 107 MSK 108 Master Session Key [RFC3748]. 110 rMSK 111 reauthentication MSK [RFC5296]. This is a per-authenticator key, 112 derived from the rRK (below). 114 rRK 115 reauthentication Root Key, derived from the EMSK Extended Master 116 Session Key [RFC3748] or DSRK [RFC5296]. 118 3. Attribute-Value Pair Definitions 120 This section defines new AVPs for the transport of cryptographic keys 121 in the Diameter EAP application [RFC4072], as well as other Diameter 122 applications. 124 3.1. Key AVP 126 The Key AVP (AVP Code ) is of type Grouped. It contains the 127 type and keying material and, optionally, an indication of the usable 128 lifetime of the key, the name of the key and a Security Parameter 129 Index (SPI) with which the key is associated. 131 Key ::= < AVP Header: AC1 > 132 < Key-Type > 133 { Keying-Material } 134 [ Key-Lifetime ] 135 [ Key-Name ] 136 [ Key-SPI ] 137 * [ AVP ] 139 3.1.1. Key-Type AVP 141 The Key-Type AVP (AVP Code ) is of type Enumerated. This AVP 142 identifies the type of the key being sent. The following decimal 143 values are defined in this document: 145 DSRK (0) 146 A Domain-Specific Root Key [RFC5295]. 148 rRK (1) 149 A reauthentication Root Key [RFC5296]. 151 rMSK (2) 152 A reauthentication Master Session Key [RFC5296]. 154 If additional values are needed, they are to be assigned by IANA 155 according to the policy stated in Section 5.2, 157 3.1.2. Key-Name AVP 159 The Key-Name AVP (AVP Code ) is of type OctetString. It 160 contains an opaque key identifier. Exactly how this name is 161 generated and used depends on the key type and usage in question, and 162 is beyond the scope of this document (see [RFC5247] and [RFC5295] for 163 discussions of key name generation in the context of EAP). 165 3.1.3. Keying-Material AVP 167 The Keying-Material AVP (AVP Code ) is of type OctetString. The 168 exact usage of this keying material depends upon several factors, 169 including the link layer in use and the type of the key and is beyond 170 the scope of this document. 172 3.1.4. Key-Lifetime AVP 174 The Key-Lifetime AVP (AVP Code ) is of type Unsigned32 and 175 represents the period of time (in seconds) for which the contents of 176 the Keying-Material AVP (Section 3.1.3) is valid. 178 NOTE: 179 Applications using this value SHOULD consider the beginning of the 180 lifetime to be the point in time when the message containing the 181 keying material is received. In addition, client implementations 182 SHOULD check to ensure that the value is reasonable; for example, 183 the lifetime of a key should not generally be longer than the 184 session lifetime (see section 8.13 of [I-D.ietf-dime-rfc3588bis]. 186 3.1.5. Key-SPI 188 The Key-SPI AVP (AVP Code ) is of type Unsigned32 and contains a 189 SPI value that can be used with other parameters for identifying 190 associated keying material. 192 4. Security Considerations 194 The security considerations applicable to the Diameter Base Protocol 195 [I-D.ietf-dime-rfc3588bis] are also applicable to this document, as 196 are those in Section 8.4 of RFC 4072 [RFC4072]. 198 5. IANA Considerations 200 Upon publication of this memo as an RFC, IANA is requested to assign 201 values as described in the following sections. 203 5.1. AVP Codes 205 Codes must be assigned for the following AVPs using the policy 206 specified in [I-D.ietf-dime-rfc3588bis], Section 11.1.1: 208 o Key (, Section 3.1) 209 o Key-Type (, Section 3.1.1) 211 o Keying-Material (, Section 3.1.3) 213 o Key-Lifetime (, Section 3.1.4) 215 o Key-SPI (, Section 3.1.5) 217 o Key-Name (, Section 3.1.2) 219 5.2. AVP Values 221 IANA is requested to create a new registry for values assigned to the 222 Key-Type AVP and populated with the decimal values defined in this 223 document (Section 3.1.1). New values may be assigned for the Key- 224 Type AVP using the "Specification Required" policy [RFC5226]; once 225 values have been assigned, they MUST NOT be deleted, replaced or 226 modified. 228 6. Acknowledgements 230 Thanks (in no particular order) to Niclas Comstedt, Semyon 231 Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom Taylor, Frank Xia, 232 Lionel Morand, Dan Romascanu, Bernard Aboba, Jouni Korhonen, Stephen 233 Farrel, Joel Halpern, Phillip Hallam-Baker, Sean Turner and Sebastien 234 Decugis for useful comments, suggestions and review. 236 7. References 238 7.1. Normative References 240 [I-D.ietf-dime-rfc3588bis] 241 Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, 242 "Diameter Base Protocol", draft-ietf-dime-rfc3588bis-26 243 (work in progress), January 2011. 245 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 246 Requirement Levels", BCP 14, RFC 2119, March 1997. 248 [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. 249 Levkowetz, "Extensible Authentication Protocol (EAP)", 250 RFC 3748, June 2004. 252 [RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible 253 Authentication Protocol (EAP) Application", RFC 4072, 254 August 2005. 256 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 257 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 258 May 2008. 260 7.2. Informative References 262 [RFC5216] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS 263 Authentication Protocol", RFC 5216, March 2008. 265 [RFC5247] Aboba, B., Simon, D., and P. Eronen, "Extensible 266 Authentication Protocol (EAP) Key Management Framework", 267 RFC 5247, August 2008. 269 [RFC5295] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri, 270 "Specification for the Derivation of Root Keys from an 271 Extended Master Session Key (EMSK)", RFC 5295, 272 August 2008. 274 [RFC5296] Narayanan, V. and L. Dondeti, "EAP Extensions for EAP Re- 275 authentication Protocol (ERP)", RFC 5296, August 2008. 277 Authors' Addresses 279 Glen Zorn 280 Network Zen 281 227/358 Thanon Sanphawut 282 Bang Na, Bangkok 10260 283 Thailand 285 Phone: +66 (0) 87-040-4617 286 Email: glenzorn@gmail.com 288 Qin Wu 289 Huawei Technologies Co., Ltd. 290 101 Software Avenue, Yuhua District 291 Nanjing, Jiangsu 21001 292 China 294 Phone: +86-25-56623633 295 Email: sunseawq@huawei.com 296 Violeta Cakulev 297 Alcatel Lucent 298 600 Mountain Ave. 299 3D-517 300 Murray Hill, NJ 07974 301 US 303 Phone: +1 908 582 3207 304 Email: violeta.cakulev@alcatel-lucent.com