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>Network Working Group A. Jerichow, Ed.
Request for Comments: 5410 Nokia Siemens Networks
Obsoletes: <a href="./rfc4909">4909</a> L. Piron
Category: Informational Nagravision S.A.
January 2009
<span class="h1">Multimedia Internet KEYing (MIKEY) General Extension Payload</span>
<span class="h1">for Open Mobile Alliance BCAST 1.0</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (c) 2009 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/</a>
<a href="http://trustee.ietf.org/license-info">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.
Abstract
This document specifies a new Multimedia Internet KEYing (MIKEY)
General Extension payload to transport the short-term key message
(STKM) and long-term key message (LTKM) payloads as well as the
management data LTKM reporting message and parental control message
payloads defined in the Open Mobile Alliance's (OMA) Broadcast
(BCAST) group's Service and Content protection specification.
<span class="grey">Jerichow & Piron Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</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-3">3</a>. MIKEY General Extension for OMA BCAST Usage . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-4">4</a>. Interoperability Considerations . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-7">7</a>. Changes since <a href="./rfc4909">RFC 4909</a> . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-8">8</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-9">9</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-9.1">9.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-9.2">9.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 Multimedia Internet KEYing (MIKEY) protocol specification (<a href="./rfc3830">RFC</a>
<a href="./rfc3830">3830</a> [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>]) defines a General Extension payload to allow possible
extensions to MIKEY without having to allocate a new payload type.
The General Extension payload can be used in any MIKEY message and is
part of the authenticated/signed data part. There is an 8-bit type
field in that payload. The type code assignment is IANA-managed, and
<a href="./rfc3830">RFC 3830</a> requires IETF consensus for assignments from the public
range of 0-240.
The Open Mobile Alliance's (OMA) Broadcast (BCAST) group's Service
and Content Protection specification [<a href="#ref-SPCP" title=""Service and Content Protection for Mobile Broadcast Services"">SPCP</a>] specifies the use of a
short-term key message (STKM), a long-term key message (LTKM), an
LTKM reporting message, and a parental control message that carry
attributes related to Service and Content protection. Note that any
keys associated with the attributes, such as the Parental Control
Pincode if present, are part of the MIKEY KEMAC payload.
This document specifies the use of the General Extension payload of
MIKEY to carry the messages mentioned above, as well as protection of
the credentials using mechanisms supported by MIKEY with
modifications in [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>].
<a href="./rfc3830">RFC 3830</a> [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>], the MIKEY General Extension payload defined in
<a href="./rfc4563">RFC 4563</a> [<a href="./rfc4563" title=""The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)"">RFC4563</a>], and the 3rd Generation Partnership Project
(3GPP)'s Multimedia Broadcast/ Multicast Service (MBMS) document
[<a href="#ref-3GPP.33.246" title=""3G Security; Security of Multimedia Broadcast/ Multicast Service (MBMS)"">3GPP.33.246</a>] specify the transport of MIKEY messages via unicast or
broadcast; the OMA BCAST specifications use either for transport of
MIKEY messages.
<span class="grey">Jerichow & Piron Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</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>].
OMA BCAST MIKEY General Extension: We refer to the General Extension
type -- 5 -- as the OMA BCAST MIKEY General Extension.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. MIKEY General Extension for OMA BCAST Usage</span>
The OMA BCAST Type (Type 5) formats the MIKEY General Extension
payload as follows:
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! Next Payload ! Type ! Length !
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! OMA BCAST Data Subtype (variable length) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: OMA BCAST MIKEY General Extension
Next Payload and Length are defined in <a href="./rfc3830#section-6.15">Section 6.15 of [RFC3830]</a>.
Type (8 bits): identifies the type of the General Extension Payload
(see <a href="./rfc3830#section-6.15">Section 6.15 of [RFC3830]</a>). This document adds a new type. It
specifies the use of Type 5 for OMA BCAST Service and Content
Protection using the Smartcard Profile.
Type | Value | Comments
------------------------------------------------------------------
OMA BCAST | 5 | information on type and identity of messages
Figure 2: Definition of the OMA BCAST MIKEY General Extension Payload
OMA BCAST Data Subtype (variable length): defines a variable length
Data field. This field is formed by subtype-payloads. The contents
of the variable length OMA BCAST Data Subtype field are defined
below.
<span class="grey">Jerichow & Piron Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</span>
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
! Subtype ! Subtype Specific Data (variable length) ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: STKM/LTKM/LTKM Reporting/Parental Control Subtype Payload
Subtype: 8 bits. This field indicates the subtype of the OMA
BCAST payload. In this specification, four values are specified:
LTKM (1), STKM (2), LTKM Reporting (3), and Parental Control (4).
Subtype Specific Data: Variable length.
OMA BCAST Data Subtype | Value | Comment
-----------------------------------------------------------
LTKM | 1 | Long Term Key Message
STKM | 2 | Short Term Key Message
LTKM Reporting | 3 | LTKM Reporting Message
Parental Control | 4 | Parental Control Message
Figure 4: Subtype Definitions for OMA BCAST Messages
The contents of the OMA BCAST Data Subtype payload field are defined
in <a href="#section-6">Section 6</a> of the OMA BCAST Service and Content Protection
specification [<a href="#ref-SPCP" title=""Service and Content Protection for Mobile Broadcast Services"">SPCP</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Interoperability Considerations</span>
This document specifies the use of MIKEY General Extension payload
Type 5 and four subtype values: 1 and 2 for OMA BCAST Service and
Content protection's LTKM and STKM payloads (respectively), 3 for
LTKM Reporting payload, and 4 for Parental Control payload.
Interoperability considerations span several standards bodies, with
OMA BCAST 1.0 enabler compliance being the key aspect; as such, it is
up to the OMA test planning to verify the interoperability and
compliance of OMA BCAST 1.0 implementations. This payload type
assignment does not change MIKEY beyond <a href="./rfc3830">RFC 3830</a> [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>] and <a href="./rfc4563">RFC</a>
<a href="./rfc4563">4563</a> [<a href="./rfc4563" title=""The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)"">RFC4563</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
According to <a href="./rfc3830">RFC 3830</a> [<a href="./rfc3830" title=""MIKEY: Multimedia Internet KEYing"">RFC3830</a>], the General Extension payload can be
used in any MIKEY message and is part of the authenticated/signed
data part. The parameters proposed to be included in the OMA BCAST
MIKEY General Extension payload (listed in <a href="#section-3">Section 3</a>) need only to be
integrity protected, which is already allowed by the MIKEY
specification. The OMA BCAST MIKEY General Extension payload SHALL
<span class="grey">Jerichow & Piron Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</span>
be integrity protected. Furthermore, keys or any parameters that
require confidentiality MUST NOT be included in the General Extension
payload. If keys or other confidential data are to be transported
via the General Extension payload, such data MUST be encrypted and
encapsulated independently. Finally, note that MIKEY already
provides replay protection and that protection also covers the
General Extension payload.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
IANA has allocated an OMA BCAST MIKEY General Extension Type --5--
from the "General Extensions payload name space" for use by OMA BCAST
as requested by <a href="./rfc4909">RFC 4909</a> [<a href="./rfc4909" title=""Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport"">RFC4909</a>]. Furthermore, IANA has created a
name space for the OMA BCAST payload subtype values defined in
[<a href="./rfc4909" title=""Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport"">RFC4909</a>] and has assigned the following subtype values from this
name space: LTKM (1), STKM (2).
IANA has allocated two new subtypes from the OMA BCAST payload
subtype name space.
The subtypes are as follows:
Subtype Name: LTKM Reporting
Value: 3
and
Subtype Name: Parental Control
Value: 4
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Changes since <a href="./rfc4909">RFC 4909</a></span>
OMA BCAST Service and Content Protection specification [<a href="#ref-SPCP" title=""Service and Content Protection for Mobile Broadcast Services"">SPCP</a>]
contains messages that were created since <a href="./rfc4909">RFC 4909</a> was written. This
document only adds the necessary assignments to support these new
messages. No modifications are made on values assigned by <a href="./rfc4909">RFC 4909</a>
[<a href="./rfc4909" title=""Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport"">RFC4909</a>].
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgments</span>
Many thanks to the authors of <a href="./rfc4909">RFC 4909</a> [<a href="./rfc4909" title=""Multimedia Internet KEYing (MIKEY) General Extension Payload for Open Mobile Alliance BCAST LTKM/STKM Transport"">RFC4909</a>] for allowing us to
obsolete their RFC.
<span class="grey">Jerichow & Piron Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-3GPP.33.246">3GPP.33.246</a>] 3GPP, "3G Security; Security of Multimedia Broadcast/
Multicast Service (MBMS)", 3GPP TS 33.246 6.12.0,
October 2007.
[<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-RFC3830">RFC3830</a>] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and
K. Norrman, "MIKEY: Multimedia Internet KEYing",
<a href="./rfc3830">RFC 3830</a>, August 2004.
[<a id="ref-RFC4563">RFC4563</a>] Carrara, E., Lehtovirta, V., and K. Norrman, "The Key
ID Information Type for the General Extension Payload
in Multimedia Internet KEYing (MIKEY)", <a href="./rfc4563">RFC 4563</a>,
June 2006.
[<a id="ref-SPCP">SPCP</a>] Open Mobile Alliance, "Service and Content Protection
for Mobile Broadcast Services",
OMA-TS-BCAST_SvcCntProtection-V1_0,
<<a href="http://www.openmobilealliance.org">http://www.openmobilealliance.org</a>>.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC4909">RFC4909</a>] Dondeti, L., Castleford, D., and F. Hartung,
"Multimedia Internet KEYing (MIKEY) General Extension
Payload for Open Mobile Alliance BCAST LTKM/STKM
Transport", <a href="./rfc4909">RFC 4909</a>, June 2007.
<span class="grey">Jerichow & Piron Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5410">RFC 5410</a> OMA BCAST MIKEY GenExt January 2009</span>
Authors' Addresses
Anja Jerichow (editor)
Nokia Siemens Networks
Martinstr. 76
81541 Munich
Germany
Phone: +49 89 636-45868
EMail: anja.jerichow@nsn.com
Laurent Piron
Nagravision S.A.
Case Postale 134
1033 Cheseaux
Switzerland
Phone: +41 21 732 05 37
EMail: laurent.piron@nagravision.com
Jerichow & Piron Informational [Page 7]
</pre>
|
