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) K. Ma
Request for Comments: 7736 Ericsson
Category: Informational December 2015
ISSN: 2070-1721
Content Delivery Network Interconnection (CDNI) Media Type Registration
Abstract
This document defines the standard media type used by the Content
Delivery Network Interconnection (CDNI) protocol suite, including the
registration procedure and recommended usage of the required payload-
type parameter.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
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). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <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/rfc7736">http://www.rfc-editor.org/info/rfc7736</a>.
Copyright Notice
Copyright (c) 2015 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">Ma Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
Table of Contents
<a href="#section-1">1</a>. Introduction and Scope . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. CDNI Media Type . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. CDNI Payload-Types Parameters Registry . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-3">3</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4">4</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4.1">4.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-4.2">4.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction and Scope</span>
The Content Delivery Network Interconnection (CDNI) working group is
developing a set of protocols to enable the interconnection of
multiple content delivery networks (CDNs), as discussed in [<a href="./rfc6770" title=""Use Cases for Content Delivery Network Interconnection"">RFC6770</a>].
The CDNI protocol suite consists of multiple HTTP-based interfaces,
many of which transfer various payloads encoded in JSON (JavaScript
Object Notation) [<a href="./rfc7159" title=""The JavaScript Object Notation (JSON) Data Interchange Format"">RFC7159</a>]. The main interfaces (i.e., CDNI Control
interface, CDNI Footprint & Capabilities Advertisement interface,
CDNI Request Routing Redirection interface, CDNI Metadata interface,
and CDNI Logging interface) are described in [<a href="./rfc7336" title=""Framework for Content Distribution Network Interconnection (CDNI)"">RFC7336</a>]. It is
desirable to be able to indicate the type of object carried in the
HTTP entity-body without having to register separate media types for
each CDNI object. To accomplish this aim, this document defines a
single new media type for CDNI that includes a required payload-type
parameter. A separate registry of CDNI payload-type parameters is
also defined. CDNI protocol specifications may register interface-
specific payload types, specifying the payload encoding and parsing
semantics for that message (e.g., JSON serialization for a CDNI
metadata object). The same payload-type parameter may also be used
as references for other purposes (e.g., referencing CDNI metadata
objects from CDNI capability advertisement objects).
<span class="grey">Ma Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. IANA Considerations</span>
This section contains the CDNI media type registration as well as the
payload-type parameter registry definition for IANA.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. CDNI Media Type</span>
Type name: application
Subtype name: cdni
Required parameters:
ptype
The required parameter "ptype" describes the type of CDNI
message contained in the message payload, as registered in the
"Content Delivery Network Interconnection (CDNI) Parameters"
registry (<a href="#section-2.2">Section 2.2</a>) defined below.
Optional parameters: none
Encoding considerations:
The CDNI protocol suite includes interfaces with encoded messages
that may be 8bit or binary, as well as generic logging information
that may be 7bit or binary.
Security considerations:
CDNI interfaces that return encoded data may be (mis)interpreted
if parsed by non-CDNI or non-compliant CDNI implementations. In
addition, CDNI logging information is likely to transfer large
amounts of data that may overload unexpecting clients. The
individual CDNI interface specifications provide more detailed
analysis of security and privacy concerns, and define the
requirements for authentication, authorization, confidentiality,
integrity, and privacy for each interface.
The application/cdni media type is a generic media type to be used
by multiple CDNI interfaces for transporting different types of
control and logging information. Proper validation of message
data requires parsing and understanding the ptype parameter and
the associated data encoding. Failure to properly validate
payloads may allow data extrusion under the auspices of the
application/cdni media type.
<span class="grey">Ma Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
Interoperability considerations:
The required ptype field is intended to fully describe the
structure and parsing of CDNI messages, as enforced by the ptype
registry designated expert.
Published specification: <a href="./rfc7736">RFC 7736</a>
Applications that use this media type:
CDNI is intended for use between interconnected CDNs for sharing
configuration and logging data, as well as for issuing content
management and redirection requests.
Fragment identifier considerations: N/A
Additional information: N/A
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): N/A
Macintosh file type code(s): N/A
Person & email address to contact for further information:
Kevin Ma <kevin.j.ma@ericsson.com>
Intended usage: LIMITED USE
Restrictions on usage:
This media type is intended only for use in CDNI protocol message
exchanges.
Author: IETF CDNI working group
Change controller: IETF CDNI working group
Provisional registration: no
<span class="grey">Ma Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. CDNI Payload-Types Parameters Registry</span>
IANA has created a new "CDNI Payload Types" subregistry within the
"Content Delivery Network Interconnection (CDNI) Parameters"
registry. The "CDNI Payload Types" namespace defines the valid
values for the required "ptype" parameter of the "application/cdni"
media type. The CDNI payload type is an ASCII string value that
consists of only visible (printing) characters but excludes equal
signs (=), double quotes ("), and semicolons (;). It will not exceed
256 characters in length. The following Augmented Backus-Naur Form
(ABNF) definition of the CDNI payload type is provided for clarity
[<a href="./rfc5234" title=""Augmented BNF for Syntax Specifications: ABNF"">RFC5234</a>]
ptype = 1*256(ptype-char)
ptype-char = %x21 / %x23-3A / %x3C / %x3E-7E
; Includes ALPHA, DIGIT, and other printables
; Excludes equal signs (=), double quotes ("), semicolons (;)
Additions to the "CDNI Payload Types" namespace will be made via
"Specification Required" as defined in [<a href="./rfc5226" title="">RFC5226</a>]. The designated
expert will verify that new type definitions do not duplicate
existing type definitions (in name or functionality), prevent
gratuitous additions to the namespace, and prevent any additions to
the namespace that would impair the interoperability of CDNI
implementations. The designated expert will review the
specification, even if it is a Standards Track RFC, to verify that it
contains the following information:
o The review will verify that the specification contains a
reasonably defined purpose for the new payload type. A reasonably
defined purpose will relate to an existing or proposed CDNI
interface and will not duplicate the functionality of any existing
CDNI protocol feature without specifying a rational reason (e.g.,
updating an obsolete feature), a method for detecting and handling
conflicts (e.g., a versioning system with prioritization matrix),
and a suggested migration path (e.g., deprecation of the
overlapped feature, or justification for co-existence).
o The review will verify that the specification contains information
as to which CDNI interface the new payload type pertains or
affects. The payload type may be applicable to multiple CDNI
interfaces, but the justification for the new payload type will
include a reasonable relationship to at least one Standards Track
CDNI interface.
<span class="grey">Ma Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
o The review will verify that the specification contains sufficient
detail about the data encoding (e.g., JSON serialization for new
CDNI metadata or capability advertisement objects, or ABNF and
description for new CDNI logging file formats) to allow senders
and receivers of the new payload type to implement compliant and
interoperable payload parsers.
The registry contains the payload type and the specification
describing the payload type. The registry will initially be
unpopulated.
+--------------+---------------+
| Payload Type | Specification |
+--------------+---------------+
+--------------+---------------+
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
See the portion of <a href="#section-2.1">Section 2.1</a> labeled "Security considerations".
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. References</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Normative References</span>
[<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>,
DOI 10.17487/RFC5226, May 2008,
<<a href="http://www.rfc-editor.org/info/rfc5226">http://www.rfc-editor.org/info/rfc5226</a>>.
[<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
DOI 10.17487/RFC5234, January 2008,
<<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>>.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Informative References</span>
[<a id="ref-RFC6770">RFC6770</a>] Bertrand, G., Ed., Stephan, E., Burbridge, T., Eardley,
P., Ma, K., and G. Watson, "Use Cases for Content Delivery
Network Interconnection", <a href="./rfc6770">RFC 6770</a>, DOI 10.17487/RFC6770,
November 2012, <<a href="http://www.rfc-editor.org/info/rfc6770">http://www.rfc-editor.org/info/rfc6770</a>>.
[<a id="ref-RFC7159">RFC7159</a>] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", <a href="./rfc7159">RFC 7159</a>, DOI 10.17487/RFC7159, March
2014, <<a href="http://www.rfc-editor.org/info/rfc7159">http://www.rfc-editor.org/info/rfc7159</a>>.
<span class="grey">Ma Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7736">RFC 7736</a> CDNI Media Type December 2015</span>
[<a id="ref-RFC7336">RFC7336</a>] Peterson, L., Davie, B., and R. van Brandenburg, Ed.,
"Framework for Content Distribution Network
Interconnection (CDNI)", <a href="./rfc7336">RFC 7336</a>, DOI 10.17487/RFC7336,
August 2014, <<a href="http://www.rfc-editor.org/info/rfc7336">http://www.rfc-editor.org/info/rfc7336</a>>.
Acknowledgments
This document is the culmination of the efforts of many in the CDNI
working group, including (in alphabetical order): Francois Le
Faucheur, Daryl Malas, Rob Murray, Ben Niven-Jenkins, Iuniana
Oprescu, Jon Peterson, and Jan Seedorf.
Author's Address
Kevin J. Ma
Ericsson
43 Nagog Park
Acton, MA 01720
United States
Phone: +1 978-844-5100
Email: kevin.j.ma@ericsson.com
Ma Informational [Page 7]
</pre>
|
