1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
|
<pre>Internet Engineering Task Force (IETF) G. Zorn
Request for Comments: 6734 Network Zen
Category: Standards Track Q. Wu
ISSN: 2070-1721 Huawei
V. Cakulev
Alcatel Lucent
October 2012
<span class="h1">Diameter Attribute-Value Pairs for Cryptographic Key Transport</span>
Abstract
Some Authentication, Authorization, and Accounting (AAA) applications
require the transport of cryptographic keying material. This
document specifies a set of Attribute-Value Pairs (AVPs) providing
native Diameter support of cryptographic key delivery.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6734">http://www.rfc-editor.org/info/rfc6734</a>.
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
<span class="grey">Zorn, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. Requirements Language ......................................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. Technical Terms and Acronyms ...............................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Attribute-Value Pair Definitions ................................<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Key AVP ....................................................<a href="#page-3">3</a>
<a href="#section-3.1.1">3.1.1</a>. Key-Type AVP ........................................<a href="#page-4">4</a>
<a href="#section-3.1.2">3.1.2</a>. Key-Name AVP ........................................<a href="#page-4">4</a>
<a href="#section-3.1.3">3.1.3</a>. Keying-Material AVP .................................<a href="#page-4">4</a>
<a href="#section-3.1.4">3.1.4</a>. Key-Lifetime AVP ....................................<a href="#page-4">4</a>
<a href="#section-3.1.5">3.1.5</a>. Key-SPI .............................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. IANA Considerations .............................................<a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. AVP Codes ..................................................<a href="#page-5">5</a>
<a href="#section-5.2">5.2</a>. AVP Values .................................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. Acknowledgements ................................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. References ......................................................<a href="#page-6">6</a>
<a href="#section-7.1">7.1</a>. Normative References .......................................<a href="#page-6">6</a>
<a href="#section-7.2">7.2</a>. Informative References .....................................<a href="#page-6">6</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Diameter Extensible Authentication Protocol (EAP) application
[<a href="./rfc4072" title=""Diameter Extensible Authentication Protocol (EAP) Application"">RFC4072</a>] defines the EAP-Master-Session-Key and EAP-Key-Name AVPs
for the purpose of transporting cryptographic keying material derived
during the execution of certain Extensible Authentication Protocol
(EAP) [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>] methods (for example, EAP-TLS [<a href="./rfc5216" title=""The EAP-TLS Authentication Protocol"">RFC5216</a>]). At most
one instance of either of these AVPs is allowed in any Diameter
message.
However, recent work (see, for example, [<a href="./rfc5295" title=""Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)"">RFC5295</a>]) has specified
methods to derive other keys from the keying material created during
EAP method execution that may require transport in addition to the
Master Session Key (MSK). Also, the EAP Re-authentication Protocol
(ERP) [<a href="./rfc6696" title=""EAP Extensions for the EAP Re-authentication Protocol (ERP)"">RFC6696</a>] specifies new keys that may need to be transported
between Diameter nodes.
This document specifies a set of AVPs allowing the transport of
multiple cryptographic keys in a single Diameter message.
<span class="grey">Zorn, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirements Language</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Technical Terms and Acronyms</span>
DSRK
Domain-Specific Root Key [<a href="./rfc5295" title=""Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)"">RFC5295</a>].
MSK
Master Session Key [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>].
rMSK
re-authentication MSK [<a href="./rfc6696" title=""EAP Extensions for the EAP Re-authentication Protocol (ERP)"">RFC6696</a>]. This is a per-authenticator key,
derived from the rRK (below).
rRK
re-authentication Root Key, derived from the Extended Master
Session Key (EMSK) [<a href="./rfc3748" title=""Extensible Authentication Protocol (EAP)"">RFC3748</a>] or DSRK [<a href="./rfc6696" title=""EAP Extensions for the EAP Re-authentication Protocol (ERP)"">RFC6696</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Attribute-Value Pair Definitions</span>
This section defines new AVPs for the transport of cryptographic keys
in the Diameter EAP application [<a href="./rfc4072" title=""Diameter Extensible Authentication Protocol (EAP) Application"">RFC4072</a>], as well as other Diameter
applications.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Key AVP</span>
The Key AVP (AVP Code 581) is of type Grouped. It contains the type
and keying material and, optionally, an indication of the usable
lifetime of the key, the name of the key and a Security Parameter
Index (SPI) with which the key is associated.
Key ::= < AVP Header: 581 >
< Key-Type >
{ Keying-Material }
[ Key-Lifetime ]
[ Key-Name ]
[ Key-SPI ]
* [ AVP ]
<span class="grey">Zorn, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. Key-Type AVP</span>
The Key-Type AVP (AVP Code 582) is of type Enumerated. This AVP
identifies the type of the key being sent. The following decimal
values are defined in this document:
DSRK (0)
A Domain-Specific Root Key [<a href="./rfc5295" title=""Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)"">RFC5295</a>].
rRK (1)
A re-authentication Root Key [<a href="./rfc6696" title=""EAP Extensions for the EAP Re-authentication Protocol (ERP)"">RFC6696</a>].
rMSK (2)
A re-authentication Master Session Key [<a href="./rfc6696" title=""EAP Extensions for the EAP Re-authentication Protocol (ERP)"">RFC6696</a>].
If additional values are needed, they are to be assigned by IANA
according to the policy stated in <a href="#section-5.2">Section 5.2</a>.
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Key-Name AVP</span>
The Key-Name AVP (AVP Code 586) is of type OctetString. It contains
an opaque key identifier. Exactly how this name is generated and
used depends on the key type and usage in question and is beyond the
scope of this document (see [<a href="./rfc5247" title=""Extensible Authentication Protocol (EAP) Key Management Framework"">RFC5247</a>] and [<a href="./rfc5295" title=""Specification for the Derivation of Root Keys from an Extended Master Session Key (EMSK)"">RFC5295</a>] for discussions
of key name generation in the context of EAP).
<span class="h4"><a class="selflink" id="section-3.1.3" href="#section-3.1.3">3.1.3</a>. Keying-Material AVP</span>
The Keying-Material AVP (AVP Code 583) is of type OctetString. The
exact usage of this keying material depends upon several factors,
including the type of the key and the link layer in use and is beyond
the scope of this document.
<span class="h4"><a class="selflink" id="section-3.1.4" href="#section-3.1.4">3.1.4</a>. Key-Lifetime AVP</span>
The Key-Lifetime AVP (AVP Code 584) is of type Unsigned32 and
represents the period of time (in seconds) for which the contents of
the Keying-Material AVP (<a href="#section-3.1.3">Section 3.1.3</a>) is valid.
NOTE:
Applications using this value SHOULD consider the beginning of the
lifetime to be the point in time when the message containing the
keying material is received. In addition, client implementations
SHOULD check to ensure that the value is reasonable; for example,
the lifetime of a key should not generally be longer than the
session lifetime (see <a href="./rfc6733#section-8.13">Section 8.13 of [RFC6733]</a>).
<span class="grey">Zorn, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
<span class="h4"><a class="selflink" id="section-3.1.5" href="#section-3.1.5">3.1.5</a>. Key-SPI</span>
The Key-SPI AVP (AVP Code 585) is of type Unsigned32 and contains an
SPI value that can be used with other parameters for identifying
associated keying material.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
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 a Keying-Material AVP
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
[<a href="./rfc6733" title=""Diameter Base Protocol"">RFC6733</a>] are also applicable to this document, as are those in
<a href="./rfc4072#section-8.4">Section 8.4 of RFC 4072</a> [<a href="./rfc4072" title=""Diameter Extensible Authentication Protocol (EAP) Application"">RFC4072</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
IANA has assigned values as described in the following sections.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. AVP Codes</span>
Codes have been assigned for the following AVPs using the policy
specified in <a href="./rfc6733#section-11.1.1">[RFC6733], Section 11.1.1</a>:
o Key (581, <a href="#section-3.1">Section 3.1</a>)
o Key-Type (582, <a href="#section-3.1.1">Section 3.1.1</a>)
o Keying-Material (583, <a href="#section-3.1.3">Section 3.1.3</a>)
o Key-Lifetime (584, <a href="#section-3.1.4">Section 3.1.4</a>)
o Key-SPI (585, <a href="#section-3.1.5">Section 3.1.5</a>)
o Key-Name (586, <a href="#section-3.1.2">Section 3.1.2</a>)
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. AVP Values</span>
IANA has created a new registry for values assigned to the Key-Type
AVP and populated it with the decimal values defined in this document
(<a href="#section-3.1.1">Section 3.1.1</a>). New values may be assigned for the Key-Type AVP
using the "Specification Required" policy [<a href="./rfc5226" title="">RFC5226</a>]; once values have
been assigned, they MUST NOT be deleted, replaced, or modified.
<span class="grey">Zorn, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Acknowledgements</span>
Thanks (in no particular order) to Niclas Comstedt, Semyon
Mizikovsky, Hannes Tschofenig, Joe Salowey, Tom Taylor, Frank Xia,
Lionel Morand, Dan Romascanu, Bernard Aboba, Jouni Korhonen, Stephen
Farrel, Joel Halpern, Phillip Hallam-Baker, Sean Turner, and
Sebastien Decugis for useful comments, suggestions, and review.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3748">RFC3748</a>] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H.
Levkowetz, "Extensible Authentication Protocol (EAP)",
<a href="./rfc3748">RFC 3748</a>, June 2004.
[<a id="ref-RFC4072">RFC4072</a>] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", <a href="./rfc4072">RFC 4072</a>,
August 2005.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC6733">RFC6733</a>] Fajardo, V., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", <a href="./rfc6733">RFC 6733</a>, October 2012.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-RFC5216">RFC5216</a>] Simon, D., Aboba, B., and R. Hurst, "The EAP-TLS
Authentication Protocol", <a href="./rfc5216">RFC 5216</a>, March 2008.
[<a id="ref-RFC5247">RFC5247</a>] Aboba, B., Simon, D., and P. Eronen, "Extensible
Authentication Protocol (EAP) Key Management Framework",
<a href="./rfc5247">RFC 5247</a>, August 2008.
[<a id="ref-RFC5295">RFC5295</a>] Salowey, J., Dondeti, L., Narayanan, V., and M. Nakhjiri,
"Specification for the Derivation of Root Keys from an
Extended Master Session Key (EMSK)", <a href="./rfc5295">RFC 5295</a>,
August 2008.
[<a id="ref-RFC6696">RFC6696</a>] Cao, Z., He, B., Shi, Y., Wu, Q., Ed., and G. Zorn, Ed.,
"EAP Extensions for the EAP Re-authentication Protocol
(ERP)", <a href="./rfc6696">RFC 6696</a>, July 2012.
<span class="grey">Zorn, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6734">RFC 6734</a> Diameter Key Transport AVPs October 2012</span>
Authors' Addresses
Glen Zorn
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 909-201060
EMail: glenzorn@gmail.com
Qin Wu
Huawei Technologies Co., Ltd.
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 21001
China
Phone: +86-25-56623633
EMail: sunseawq@huawei.com
Violeta Cakulev
Alcatel Lucent
600 Mountain Ave.
3D-517
Murray Hill, NJ 07974
US
Phone: +1 908 582 3207
EMail: violeta.cakulev@alcatel-lucent.com
Zorn, et al. Standards Track [Page 7]
</pre>
|
