idnits 2.17.1 draft-hansen-media-type-suffix-regs-02.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 60 lines 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 (April 19, 2012) is 4388 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) ** Obsolete normative reference: RFC 4627 (Obsoleted by RFC 7158, RFC 7159) -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.X690.2008' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.X891.2005' -- Possible downref: Non-RFC (?) normative reference: ref. 'WBXML' -- Possible downref: Non-RFC (?) normative reference: ref. 'ZIP' -- Obsolete informational reference (is this intentional?): RFC 3023 (Obsoleted by RFC 7303) == Outdated reference: A later version (-14) exists of draft-ietf-appsawg-media-type-regs-05 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Hansen 3 Internet-Draft AT&T Laboratories 4 Intended status: Standards Track April 19, 2012 5 Expires: October 19, 2012 7 Additional Media Type Structured Syntax Suffixes 8 draft-hansen-media-type-suffix-regs-02 10 Abstract 12 This document defines several Structured Syntax Suffixes for use with 13 media type registrations. In particular, it defines and registers 14 the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" 15 Structured Syntax Suffixes. 17 Status of this Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on October 19, 2012. 34 Copyright Notice 36 Copyright (c) 2012 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents (http://trustee.ietf.org/ 41 license-info) in effect on the date of publication of this document. 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. Code Components 44 extracted from this document must include Simplified BSD License text 45 as described in Section 4.e of the Trust Legal Provisions and are 46 provided without warranty as described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. When to Use these Structured Syntax Suffixes . . . . . . . . . 2 52 3. The +json Structured Syntax Suffix . . . . . . . . . . . . . . 2 53 4. The +ber and +der Structured Syntax Suffixes . . . . . . . . . 3 54 5. The +fastinfoset Structured Syntax Suffix . . . . . . . . . . 4 55 6. The +wbxml Structured Syntax Suffix . . . . . . . . . . . . . 4 56 7. The +zip Structured Syntax Suffix . . . . . . . . . . . . . . 5 57 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 58 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 59 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 60 10.1. Normative References . . . . . . . . . . . . . . . . . . 6 61 10.2. Informative References . . . . . . . . . . . . . . . . . 6 62 Appendix A. Change History . . . . . . . . . . . . . . . . . . . . 7 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7 65 1. Introduction 67 [RFC3023] created the +xml suffix convention that may be used by 68 media types whose representation uses XML underneath, that is, they 69 could have been successfully parsed as if the media type had been 70 application/xml in addition to their being parsed as their media type 71 that is using the +xml suffix. [I-D.ietf-appsawg-media-type-regs] 72 defines a registry to be used for future Structured Syntax Suffixes. 74 A variety of Structured Syntax Suffixes have already been used in 75 some Media Type registration, in particular "+json", "+der", 76 "+fastinfoset" and "+wbxml". This document defines and registers 77 these Structured Syntax Suffixes in the Structured Syntax Suffix 78 registry, along with "+ber" and "+zip". 80 Discussion of this document should occur in the Apps Area Working 81 Group (apps-discuss@ietf.org). [RFC Editor note: remove this 82 paragraph.] 84 2. When to Use these Structured Syntax Suffixes 86 Each of the Structured Syntax Suffixes defined in this document are 87 appropriate for use when the media type identifies the semantics of 88 the protocol payload. That is, knowing the semantics of the specific 89 media type provides for more specific processing of the content than 90 that afforded by generic processing of the underlying representation. 92 At the same time, using the suffix provides receivers of the media 93 types to do generic processing of the underlying representation in 94 cases where 1) they do not need to handle specially the particular 95 semantics of the exact media type, and, 2) there is no special 96 knowledge needed by such a generic processor in order to parse that 97 underlying representation other than what would be needed to parse 98 any example of that underlying representation. 100 3. The +json Structured Syntax Suffix 102 [RFC4627] defines the "application/json" media type. The suffix 103 "+json" may be used with any media type whose representation follows 104 that established for "application/json". The Message Type Structured 105 Syntax Suffix registration form follows: 107 Name JavaScript Object Notation (JSON) 109 +suffix +json 110 References [RFC4627] 112 Encoding considerations Per [RFC4627], JSON may be represented using 113 UTF-8, UTF-16, or UTF-32. When JSON is written 114 in UTF-8, JSON is 8bit compatible. When JSON is 115 written in UTF-16 or UTF-32, JSON is binary. 117 Interoperability considerations n/a 119 Security considerations See [RFC4627] 121 Contact Apps Area Working Group (apps-discuss@ietf.org) 123 Author/Change controller The Apps Area Working Group has change 124 control over this registration. 126 4. The +ber and +der Structured Syntax Suffixes 128 The ITU defined the Basic Encoding Rules (BER) and Distinguished 129 Encoding Rules (DER) message transfer syntaxes in [ITU.X690.2008]. 130 The suffix "+ber" may be used with any media type whose 131 representation follows the BER message transfer syntax. The suffix 132 "+der" may be used with any media type whose representation follows 133 the DER message transfer syntax. The Message Type Structured Syntax 134 Suffix registration forms follows: 136 Name Basic Encoding Rules (BER) message transfer 137 syntax 139 +suffix +ber 141 References [ITU.X690.2008] 143 Encoding considerations BER is a binary encoding. 145 Interoperability considerations n/a 147 Security considerations There are no security considerations inherent 148 in BER. Each individual media type registered 149 with a +ber suffix may have additional security 150 considerations. 152 Contact Apps Area Working Group (apps-discuss@ietf.org) 154 Author/Change controller The Apps Area Working Group has change 155 control over this registration. 157 Name Distinguished Encoding Rules (DER) message 158 transfer syntax 160 +suffix +der 162 References [ITU.X690.2008] 163 Encoding considerations DER is a binary encoding. 165 Interoperability considerations n/a 167 Security considerations There are no security considerations inherent 168 in DER. Each individual media type registered 169 with a +der suffix may have additional security 170 considerations. 172 Contact Apps Area Working Group (apps-discuss@ietf.org) 174 Author/Change controller The Apps Area Working Group has change 175 control over this registration. 177 5. The +fastinfoset Structured Syntax Suffix 179 The ITU defined the Fast Infoset document format as a binary 180 representation of the XML Information Set in [ITU.X891.2005]. These 181 documents further define the "application/fastinfoset" media type. 182 The suffix "+fastinfoset" may be used with any media type whose 183 representation follows that established for "application/ 184 fastinfoset". The Message Type Structured Syntax Suffix registration 185 form follows: 187 Name Fast Infoset document format 189 +suffix +fastinfoset 191 References [ITU.X891.2005] 193 Encoding considerations Fast Infoset is a binary encoding. The 194 binary, quoted-printable and base64 content- 195 transfer-encodings are suitable for use with Fast 196 Infoset. 198 Interoperability considerations n/a 200 Security considerations There are no security considerations inherent 201 in Fast Infoset. Each individual media type 202 registered with a +fastinfoset suffix may have 203 additional security considerations. 205 Contact Apps Area Working Group (apps-discuss@ietf.org) 207 Author/Change controller The Apps Area Working Group has change 208 control over this registration. 210 6. The +wbxml Structured Syntax Suffix 211 The WAP Forum has defined the WAP Binary XML (WBXML) document format 212 as a binary representation of XML in [WBXML]. This document further 213 defines the "application/vnd.wap.wbxml" media type. The suffix 214 "+wbxml" may be used with any media type whose representation follows 215 that established for "application/vnd.wap.wbxml". The Message Type 216 Structured Syntax Suffix registration form follows: 218 Name WAP Binary XML (WBXML) document format 220 +suffix +wbxml 222 References [WBXML] 224 Encoding considerations WBXML is a binary encoding. 226 Interoperability considerations n/a 228 Security considerations There are no security considerations inherent 229 in WBXML. Each individual media type registered 230 with a +wbxml suffix may have additional security 231 considerations. 233 Contact Apps Area Working Group (apps-discuss@ietf.org) 235 Author/Change controller The Apps Area Working Group has change 236 control over this registration. 238 7. The +zip Structured Syntax Suffix 240 The ZIP format is a public domain, cross-platform, interoperable file 241 storage and transfer format, originally defined by PKWARE, Inc.; it 242 supports compression and encryption and is used as the underlying 243 representation by a variety of file formats. The media type 244 "application/zip" has been registered for such files. The suffix 245 "+zip" may be used with any media type whose representation follows 246 that established for "application/zip". The Message Type Structured 247 Syntax Suffix registration form follows: 249 Name ZIP file storage and transfer format 251 +suffix +zip 253 References [ZIP] 255 Encoding considerations ZIP is a binary encoding. 257 Interoperability considerations n/a 258 Security considerations ZIP files support two forms of encryption: 259 Strong Encryption and AES 128-bit, 192-bit and 260 256-bit encryption; see the specification for 261 further details. Each individual media type 262 registered with a +zip suffix may have additional 263 security considerations. 265 Contact Apps Area Working Group (apps-discuss@ietf.org) 267 Author/Change controller The Apps Area Working Group has change 268 control over this registration. 270 8. IANA Considerations 272 See the Message Type Structured Syntax Suffix registration forms in 273 Section 3 - Section 7. 275 9. Security Considerations 277 See the Security considerations sections found in the Message Type 278 Structured Syntax Suffix registration forms from Section 3 - Section 279 6. 281 10. References 283 10.1. Normative References 285 [RFC4627] Crockford, D., "The application/json Media Type for 286 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 288 [ITU.X690.2008] 289 International Telecommunications Union, "Recommendation 290 ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.1 encoding rules: 291 Specification of basic encoding Rules (BER), Canonical 292 encoding rules (CER) and Distinguished encoding rules 293 (DER)", ITU-T Recommendation X.690, November 2008. 295 [ITU.X891.2005] 296 International Telecommunications Union, "Recommendation 297 ITU-T X.891 | ISO/IEC 24824-1 (2007), Generic applications 298 of ASN.1: Fast infoset", ITU-T Recommendation X.891, May 299 2005. 301 [WBXML] Open Mobile Alliance, "Binary XML Content Format 302 Specification", OMA Wireless Access Protocol 303 WAP-192-WBXML-20010725-a, July 2001. 305 [ZIP] PKWARE, Inc., "APPNOTE.TXT - .ZIP File Format 306 Specification", PKWARE .ZIP File Format Specification - 307 Version 6.3.2, September 2007. 309 10.2. Informative References 311 [RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media 312 Types", RFC 3023, January 2001. 314 [I-D.ietf-appsawg-media-type-regs] 315 Freed, N., Klensin, J. and T. Hansen, "Media Type 316 Specifications and Registration Procedures", Internet- 317 Draft draft-ietf-appsawg-media-type-regs-05, April 2012. 319 Appendix A. Change History 321 This section is to be removed before publication. 323 -02 Added +zip. 324 Fixed up the ISO document references. 325 Minor changes. 327 -01 Added +ber. 328 Minor changes. 330 Author's Address 332 Tony Hansen 333 AT&T Laboratories 334 200 Laurel Ave. South 335 Middletown, NJ 07748 336 USA 338 Email: tony+sss@maillennium.att.com