Debian Codegraph @

rfc6839.html

raw
1 <pre>Internet Engineering Task Force (IETF) T. Hansen
2 Request for Comments: 6839 AT&amp;T Laboratories
3 Updates: <a href="./rfc3023">3023</a> A. Melnikov
4 Category: Informational Isode Ltd
5 ISSN: 2070-1721 January 2013
6
7
8 <span class="h1">Additional Media Type Structured Syntax Suffixes</span>
9
10 Abstract
11
12 A content media type name sometimes includes partitioned meta-
13 information distinguished by a structured syntax to permit noting an
14 attribute of the media as a suffix to the name. This document
15 defines several structured syntax suffixes for use with media type
16 registrations. In particular, it defines and registers the "+json",
17 "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" structured syntax
18 suffixes, and provides a media type structured syntax suffix
19 registration form for the "+xml" structured syntax suffix.
20
21 Status of This Memo
22
23 This document is not an Internet Standards Track specification; it is
24 published for informational purposes.
25
26 This document is a product of the Internet Engineering Task Force
27 (IETF). It represents the consensus of the IETF community. It has
28 received public review and has been approved for publication by the
29 Internet Engineering Steering Group (IESG). Not all documents
30 approved by the IESG are a candidate for any level of Internet
31 Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.
32
33 Information about the current status of this document, any errata,
34 and how to provide feedback on it may be obtained at
35 <a href="http://www.rfc-editor.org/info/rfc6839">http://www.rfc-editor.org/info/rfc6839</a>.
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Hansen &amp; Melnikov Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2013 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-2">2</a>. When to Use These Structured Syntax Suffixes . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-3">3</a>. Initial Structured Syntax Suffix Definitions . . . . . . . . . <a href="#page-4">4</a>
77 <a href="#section-3.1">3.1</a>. The +json Structured Syntax Suffix . . . . . . . . . . . . <a href="#page-4">4</a>
78 <a href="#section-3.2">3.2</a>. The +ber Structured Syntax Suffix . . . . . . . . . . . . <a href="#page-5">5</a>
79 <a href="#section-3.3">3.3</a>. The +der Structured Syntax Suffix . . . . . . . . . . . . <a href="#page-6">6</a>
80 <a href="#section-3.4">3.4</a>. The +fastinfoset Structured Syntax Suffix . . . . . . . . <a href="#page-7">7</a>
81 <a href="#section-3.5">3.5</a>. The +wbxml Structured Syntax Suffix . . . . . . . . . . . <a href="#page-9">9</a>
82 <a href="#section-3.6">3.6</a>. The +zip Structured Syntax Suffix . . . . . . . . . . . . <a href="#page-10">10</a>
83 <a href="#section-4">4</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
84 <a href="#section-4.1">4.1</a>. The +xml Structured Syntax Suffix . . . . . . . . . . . . <a href="#page-11">11</a>
85 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
86 <a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
87 <a href="#section-6.1">6.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
88 <a href="#section-6.2">6.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Hansen &amp; Melnikov Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 [<a id="ref-RFC3023">RFC3023</a>] created the +xml suffix convention that can be used when
116 defining names for media types whose representation uses XML
117 underneath. That is, they could have been successfully parsed as if
118 the media type had been application/xml in addition to their being
119 parsed as their media type that is using the +xml suffix. [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>]
120 defines the media type "Structured Syntax Suffix Registry" to be used
121 for such structured syntax suffixes.
122
123 A variety of structured syntax suffixes have already been used in
124 some media type registrations, in particular "+json", "+der",
125 "+fastinfoset", and "+wbxml". This document defines and registers
126 these structured syntax suffixes in the Structured Syntax Suffix
127 Registry, along with "+ber" and "+zip". In addition, this document
128 updates [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>] to formally register the "+xml" structured syntax
129 suffix according to the procedure defined in [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>].
130
131 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
132 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
133 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].
134
135 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. When to Use These Structured Syntax Suffixes</span>
136
137 Each of the structured syntax suffixes defined in this document is
138 appropriate for use when the media type identifies the semantics of
139 the protocol payload. That is, knowing the semantics of the specific
140 media type provides for more specific processing of the content than
141 that afforded by generic processing of the underlying representation.
142
143 At the same time, using the suffix allows receivers of the media
144 types to do generic processing of the underlying representation in
145 cases where
146
147 they do not need to perform special handling of the particular
148 semantics of the exact media type, and
149
150 there is no special knowledge needed by such a generic processor
151 in order to parse that underlying representation other than what
152 would be needed to parse any example of that underlying
153 representation.
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Hansen &amp; Melnikov Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
167
168
169 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Initial Structured Syntax Suffix Definitions</span>
170
171 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. The +json Structured Syntax Suffix</span>
172
173 [<a id="ref-RFC4627">RFC4627</a>] defines the "application/json" media type. The suffix
174 "+json" MAY be used with any media type whose representation follows
175 that established for "application/json". The media type structured
176 syntax suffix registration form follows. See [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] for
177 definitions of each of the registration form headings.
178
179 Name: JavaScript Object Notation (JSON)
180
181 +suffix: +json
182
183 References: [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>]
184
185 Encoding considerations:
186
187 Per [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>], JSON is allowed to be represented using UTF-8,
188 UTF-16, or UTF-32. When JSON is written in UTF-8, JSON is 8bit
189 compatible ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]). When JSON is written in UTF-16 or UTF-32,
190 JSON is binary ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).
191
192 Fragment identifier considerations:
193
194 The syntax and semantics of fragment identifiers specified for
195 +json SHOULD be as specified for "application/json". (At
196 publication of this document, there is no fragment identification
197 syntax defined for "application/json".)
198
199 The syntax and semantics for fragment identifiers for a specific
200 "xxx/yyy+json" SHOULD be processed as follows:
201
202 For cases defined in +json, where the fragment identifier resolves
203 per the +json rules, then process as specified in +json.
204
205 For cases defined in +json, where the fragment identifier does
206 not resolve per the +json rules, then process as specified in
207 "xxx/yyy+json".
208
209 For cases not defined in +json, then process as specified in
210 "xxx/yyy+json".
211
212 Interoperability considerations: n/a
213
214 Security considerations: See [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>]
215
216 Contact: Apps Area Working Group ([email protected])
217
218
219
220 <span class="grey">Hansen &amp; Melnikov Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
223
224
225 Author/Change controller:
226
227 The Apps Area Working Group. IESG has change control over this
228 registration.
229
230 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. The +ber Structured Syntax Suffix</span>
231
232 The ITU defined the Basic Encoding Rules (BER) transfer syntax in
233 [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]. The suffix "+ber" MAY be used with any media type
234 whose representation follows the BER transfer syntax. (The Expert
235 Reviewer for media type structured syntax suffix registrations ought
236 to be aware of the relationship between BER and DER to aid in
237 selecting the proper suffix.) The media type structured syntax
238 suffix registration form for +ber follows:
239
240 Name: Basic Encoding Rules (BER) transfer syntax
241
242 +suffix: +ber
243
244 References: [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]
245
246 Encoding considerations: BER is a binary encoding.
247
248 Fragment identifier considerations:
249
250 At publication of this document, there is no fragment
251 identification syntax defined for +ber.
252
253 The syntax and semantics for fragment identifiers for a specific
254 "xxx/yyy+ber" SHOULD be processed as follows:
255
256 For cases defined in +ber, where the fragment identifier
257 resolves per the +ber rules, then process as specified in +ber.
258
259 For cases defined in +ber, where the fragment identifier does
260 not resolve per the +ber rules, then process as specified in
261 "xxx/yyy+ber".
262
263 For cases not defined in +ber, then process as specified in
264 "xxx/yyy+ber".
265
266 Interoperability considerations: n/a
267
268 Security considerations:
269
270 Each individual media type registered with a +ber suffix can have
271 additional security considerations.
272
273
274
275
276 <span class="grey">Hansen &amp; Melnikov Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
279
280
281 BER has a type-length-value structure, and it is easy to construct
282 malicious content with invalid length fields that can cause buffer
283 overrun conditions.
284
285 BER allows for arbitrary levels of nesting, which may make it
286 possible to construct malicious content that will cause a stack
287 overflow.
288
289 Interpreters of the BER structures should be aware of these issues
290 and should take appropriate measures to guard against buffer
291 overflows and stack overruns in particular and malicious content
292 in general.
293
294 Contact: Apps Area Working Group ([email protected])
295
296 Author/Change controller:
297
298 The Apps Area Working Group. IESG has change control over this
299 registration.
300
301 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. The +der Structured Syntax Suffix</span>
302
303 The ITU defined the Distinguished Encoding Rules (DER) transfer
304 syntax in [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]. The suffix "+der" MAY be used with any
305 media type whose representation follows the DER transfer syntax.
306 (The Expert Reviewer for media type structured syntax suffix
307 registrations ought to be aware of the relationship between BER and
308 DER to aid in selecting the proper suffix.) The media type
309 structured syntax suffix registration form for +der follows:
310
311 Name: Distinguished Encoding Rules (DER) transfer syntax
312
313 +suffix: +der
314
315 References: [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]
316
317 Encoding considerations: DER is a binary encoding.
318
319 Fragment identifier considerations:
320
321 At publication of this document, there is no fragment
322 identification syntax defined for +der.
323
324 The syntax and semantics for fragment identifiers for a specific
325 "xxx/yyy+der" SHOULD be processed as follows:
326
327 For cases defined in +der, where the fragment identifier
328 resolves per the +der rules, then process as specified in +der.
329
330
331
332 <span class="grey">Hansen &amp; Melnikov Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
335
336
337 For cases defined in +der, where the fragment identifier does
338 not resolve per the +der rules, then process as specified in
339 "xxx/yyy+der".
340
341 For cases not defined in +der, then process as specified in
342 "xxx/yyy+der".
343
344 Interoperability considerations: n/a
345
346 Security considerations:
347
348 Each individual media type registered with a +der suffix can have
349 additional security considerations.
350
351 DER has a type-length-value structure, and it is easy to construct
352 malicious content with invalid length fields that can cause buffer
353 overrun conditions.
354
355 DER allows for arbitrary levels of nesting, which may make it
356 possible to construct malicious content that will cause a stack
357 overflow.
358
359 Interpreters of the DER structures should be aware of these issues
360 and should take appropriate measures to guard against buffer
361 overflows and stack overruns in particular and malicious content
362 in general.
363
364 Contact: Apps Area Working Group ([email protected])
365
366 Author/Change controller:
367
368 The Apps Area Working Group. IESG has change control over this
369 registration.
370
371 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. The +fastinfoset Structured Syntax Suffix</span>
372
373 The ITU defined the Fast Infoset document format as a binary
374 representation of the XML Information Set in [<a href="#ref-ITU.X891.2005">ITU.X891.2005</a>]. These
375 documents further define the "application/fastinfoset" media type.
376 The suffix "+fastinfoset" MAY be used with any media type whose
377 representation follows that established for "application/
378 fastinfoset". The media type structured syntax suffix registration
379 form follows:
380
381 Name: Fast Infoset document format
382
383 +suffix: +fastinfoset
384
385
386
387
388 <span class="grey">Hansen &amp; Melnikov Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
391
392
393 References: [<a href="#ref-ITU.X891.2005">ITU.X891.2005</a>]
394
395 Encoding considerations:
396
397 Fast Infoset is a binary encoding. The binary, quoted-printable,
398 and base64 content-transfer-encodings are suitable for use with
399 Fast Infoset.
400
401 Fragment identifier considerations:
402
403 The syntax and semantics of fragment identifiers specified for
404 +fastinfoset SHOULD be as specified for "application/fastinfoset".
405 (At publication of this document, there is no fragment
406 identification syntax defined for "application/fastinfoset".)
407
408 The syntax and semantics for fragment identifiers for a specific
409 "xxx/ yyy+fastinfoset" SHOULD be processed as follows:
410
411 For cases defined in +fastinfoset, where the fragment
412 identifier resolves per the +fastinfoset rules, then process as
413 specified in +fastinfoset.
414
415 For cases defined in +fastinfoset, where the fragment
416 identifier does not resolve per the +fastinfoset rules, then
417 process as specified in "xxx/yyy+fastinfoset".
418
419 For cases not defined in +fastinfoset, then process as
420 specified in "xxx/ yyy+fastinfoset".
421
422 Interoperability considerations: n/a
423
424 Security considerations:
425
426 There are no security considerations inherent in Fast Infoset.
427 Each individual media type registered with a +fastinfoset suffix
428 can have additional security considerations.
429
430 Contact: Apps Area Working Group ([email protected])
431
432 Author/Change controller:
433
434 The Apps Area Working Group. IESG has change control over this
435 registration.
436
437
438
439
440
441
442
443
444 <span class="grey">Hansen &amp; Melnikov Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
447
448
449 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. The +wbxml Structured Syntax Suffix</span>
450
451 The Wireless Application Protocol (WAP) Forum has defined the WAP
452 Binary XML (WBXML) document format as a binary representation of XML
453 in [<a href="#ref-WBXML" title="&quot;Binary XML Content Format Specification&quot;">WBXML</a>]. This document further defines the "application/
454 vnd.wap.wbxml" media type. The suffix "+wbxml" MAY be used with any
455 media type whose representation follows that established for
456 "application/vnd.wap.wbxml". The media type structured syntax suffix
457 registration form follows:
458
459 Name: WAP Binary XML (WBXML) document format
460
461 +suffix: +wbxml
462
463 References: [<a href="#ref-WBXML" title="&quot;Binary XML Content Format Specification&quot;">WBXML</a>]
464
465 Encoding considerations: WBXML is a binary encoding.
466
467 Fragment identifier considerations:
468
469 The syntax and semantics of fragment identifiers specified for
470 +wbxml SHOULD be as specified for "application/vnd.wap.wbxml".
471 (At publication of this document, there is no fragment
472 identification syntax defined for "application/vnd.wap.wbxml".)
473
474 The syntax and semantics for fragment identifiers for a specific
475 "xxx/yyy+wbxml" SHOULD be processed as follows:
476
477 For cases defined in +wbxml, where the fragment identifier
478 resolves per the +wbxml rules, then process as specified in
479 +wbxml.
480
481 For cases defined in +wbxml, where the fragment identifier does
482 not resolve per the +wbxml rules, then process as specified in
483 "xxx/yyy+wbxml".
484
485 For cases not defined in +wbxml, then process as specified in
486 "xxx/yyy+wbxml".
487
488 Interoperability considerations: n/a
489
490 Security considerations:
491
492 There are no security considerations inherent in WBXML. Each
493 individual media type registered with a +wbxml suffix can have
494 additional security considerations.
495
496 Contact: Apps Area Working Group ([email protected])
497
498
499
500 <span class="grey">Hansen &amp; Melnikov Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
503
504
505 Author/Change controller:
506
507 The Apps Area Working Group. IESG has change control over this
508 registration.
509
510 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. The +zip Structured Syntax Suffix</span>
511
512 The ZIP format is a public domain, cross-platform, interoperable file
513 storage and transfer format, originally defined by PKWARE, Inc.; it
514 supports compression and encryption and is used as the underlying
515 representation by a variety of file formats. The media type
516 "application/zip" has been registered for such files. The suffix
517 "+zip" MAY be used with any media type whose representation follows
518 that established for "application/zip". The media type structured
519 syntax suffix registration form follows:
520
521 Name: ZIP file storage and transfer format
522
523 +suffix: +zip
524
525 References: [<a href="#ref-ZIP" title="&quot;APPNOTE.TXT - .ZIP File Format Specification&quot;">ZIP</a>]
526
527 Encoding considerations: ZIP is a binary encoding.
528
529 Fragment identifier considerations:
530
531 The syntax and semantics of fragment identifiers specified for
532 +zip SHOULD be as specified for "application/zip". (At
533 publication of this document, there is no fragment identification
534 syntax defined for "application/zip".)
535
536 The syntax and semantics for fragment identifiers for a specific
537 "xxx/yyy+zip" SHOULD be processed as follows:
538
539 For cases defined in +zip, where the fragment identifier
540 resolves per the +zip rules, then process as specified in +zip.
541
542 For cases defined in +zip, where the fragment identifier does
543 not resolve per the +zip rules, then process as specified in
544 "xxx/yyy+zip".
545
546 For cases not defined in +zip, then process as specified in
547 "xxx/yyy+zip".
548
549 Interoperability considerations: n/a
550
551
552
553
554
555
556 <span class="grey">Hansen &amp; Melnikov Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
559
560
561 Security considerations:
562
563 IP files support two forms of encryption: Strong Encryption and
564 AES 128-bit, 192-bit, and 256-bit encryption; see the
565 specification for further details. Each individual media type
566 registered with a +zip suffix can have additional security
567 considerations.
568
569 Contact: Apps Area Working Group ([email protected])
570
571 Author/Change controller: The Apps Area Working Group. IESG has
572 change control over this registration.
573
574 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. IANA Considerations</span>
575
576 See the media type structured syntax suffix registration forms in
577 Sections <a href="#section-3.1">3.1</a> - <a href="#section-3.6">3.6</a>.
578
579 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. The +xml Structured Syntax Suffix</span>
580
581 The following structured syntax suffix registration for "+xml" shall
582 be used to reflect the information found in [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>], with the
583 addition of fragment identifier considerations. (Note that [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]
584 is in the process of being updated by [<a href="#ref-XML-MEDIATYPES">XML-MEDIATYPES</a>].)
585
586 Name: Extensible Markup Language (XML)
587
588 +suffix: +xml
589
590 References: [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]
591
592 Encoding considerations:
593
594 Per [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>], XML is allowed to be represented using both 7-bit
595 and 8-bit encodings. When XML is written in UTF-8, XML is 8bit
596 compatible ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]). When XML is written in UTF-16 or UTF-32,
597 XML is binary ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).
598
599 Fragment identifier considerations:
600
601 The syntax and semantics of fragment identifiers specified for
602 +xml SHOULD be as specified for "application/xml". (At
603 publication of this document, the fragment identification syntax
604 considerations for "application/xml" are defined in [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>],
605 Sections <a href="#section-5">5</a> and <a href="#section-7">7</a>.)
606
607
608
609
610
611
612 <span class="grey">Hansen &amp; Melnikov Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
615
616
617 The syntax and semantics for fragment identifiers for a specific
618 "xxx/yyy+xml" SHOULD be processed as follows:
619
620 For cases defined in +xml, where the fragment identifier
621 resolves per the +xml rules, then process as specified in +xml.
622
623 For cases defined in +xml, where the fragment identifier does
624 not resolve per the +xml rules, then process as specified in
625 "xxx/yyy+xml".
626
627 For cases not defined in +xml, then process as specified in
628 "xxx/yyy+xml".
629
630 Interoperability considerations: See [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].
631
632 Security considerations: See [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]
633
634 Contact: Apps Area Working Group ([email protected])
635
636 Author/Change controller:
637
638 The Apps Area Working Group. IESG has change control over this
639 registration.
640
641 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
642
643 See the Security Considerations sections found in the media type
644 structured syntax suffix registration forms from Sections <a href="#section-3">3</a> and <a href="#section-4">4</a>.
645
646 When updating a +&lt;suffix&gt; registration, care should be taken to
647 review all previously-registered xxx/yyy+&lt;suffix&gt; media types as to
648 whether they might be affected by the updated +&lt;suffix&gt; registration.
649 Because the generic fragment identifier processing rules take
650 precedence over media-type-specific rules, introducing new or
651 changing existing definitions may break the existing registrations of
652 specific media types, as well as particular implementations of
653 applications that process affected media types. Such changes can
654 introduce interoperability and security issues.
655
656 When updating the fragment identifier processing rules for a specific
657 xxx/yyy+&lt;suffix&gt; media type, care should be taken to review the
658 generic fragment identifier processing rules for the +&lt;suffix&gt;
659 registration and not introduce any conflicts. Because the generic
660 fragment identifier processing rules take precedence over media-type-
661 specific rules, such conflicting processing requirements should be
662 ignored by an implementation, but such conflicts can introduce
663 interoperability and security issues.
664
665
666
667
668 <span class="grey">Hansen &amp; Melnikov Informational [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
671
672
673 Note that [<a href="#ref-FRAGID-BP">FRAGID-BP</a>] provides additional advice to designers of
674 fragment identifier rules for media type suffixes and specific media
675 types.
676
677 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
678
679 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative References</span>
680
681 [<a id="ref-RFC4627">RFC4627</a>] Crockford, D., "The application/json Media Type for
682 JavaScript Object Notation (JSON)", <a href="./rfc4627">RFC 4627</a>, July 2006.
683
684 [<a id="ref-ITU.X690.2008">ITU.X690.2008</a>]
685 International Telecommunications Union, "Recommendation
686 ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.1 encoding rules:
687 Specification of basic encoding Rules (BER), Canonical
688 encoding rules (CER) and Distinguished encoding rules
689 (DER)", ITU-T Recommendation X.690, November 2008.
690
691 [<a id="ref-ITU.X891.2005">ITU.X891.2005</a>]
692 International Telecommunications Union, "Recommendation
693 ITU-T X.891 | ISO/IEC 24824-1 (2007), Generic applications
694 of ASN.1: Fast infoset", ITU-T Recommendation X.891,
695 May 2005.
696
697 [<a id="ref-WBXML">WBXML</a>] Open Mobile Alliance, "Binary XML Content Format
698 Specification", OMA Wireless Access Protocol WAP-192-
699 WBXML-20010725-a, July 2001.
700
701 [<a id="ref-ZIP">ZIP</a>] PKWARE, Inc., "APPNOTE.TXT - .ZIP File Format
702 Specification", PKWARE .ZIP File Format Specification -
703 Version 6.3.2, September 2007.
704
705 [<a id="ref-RFC2045">RFC2045</a>] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
706 Extensions (MIME) Part One: Format of Internet Message
707 Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.
708
709 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
710 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
711
712 [<a id="ref-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
713 Types", <a href="./rfc3023">RFC 3023</a>, January 2001.
714
715 <span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative References</span>
716
717 [<a id="ref-RFC6838">RFC6838</a>] Freed, N., Klensin, J., and T. Hansen, "Media Type
718 Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>,
719 <a href="./rfc6838">RFC 6838</a>, January 2013.
720
721
722
723
724 <span class="grey">Hansen &amp; Melnikov Informational [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc6839">RFC 6839</a> Additional Media Type Suffixes January 2013</span>
727
728
729 [<a id="ref-FRAGID-BP">FRAGID-BP</a>]
730 Tennison, J., "Best Practices for Fragment Identifiers and
731 Media Type Definitions", July 2012,
732 &lt;<a href="http://www.w3.org/TR/fragid-best-practices/">http://www.w3.org/TR/fragid-best-practices/</a>&gt;.
733
734 [<a id="ref-XML-MEDIATYPES">XML-MEDIATYPES</a>]
735 Lilley, C., Makoto, M., Melnikov, A., and H. Thompson,
736 "XML Media Types", Work in Progress, November 2012.
737
738 Authors' Addresses
739
740 Tony Hansen
741 AT&amp;T Laboratories
742 200 Laurel Ave. South
743 Middletown, NJ 07748
744 USA
745
746 EMail: [email protected]
747
748
749 Alexey Melnikov
750 Isode Ltd
751 5 Castle Business Village
752 36 Station Road
753 Hampton, Middlesex TW12 2BX
754 UK
755
756 EMail: [email protected]
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780 Hansen &amp; Melnikov Informational [Page 14]
781 </pre>