idnits 2.17.00 (12 Aug 2021) /tmp/idnits2575/draft-hansen-media-type-suffix-regs-01.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 06, 2012) is 3696 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.X891.2005' -- Possible downref: Non-RFC (?) normative reference: ref. 'WBXML' -- Obsolete informational reference (is this intentional?): RFC 3023 (Obsoleted by RFC 7303) == Outdated reference: draft-ietf-appsawg-media-type-regs has been published as RFC 6838 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 4 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 06, 2012 5 Expires: October 06, 2012 7 Additional Media Type Structured Syntax Suffixes 8 draft-hansen-media-type-suffix-regs-01 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" and "+wbxml" Structured 15 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 06, 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 8. Security Considerations . . . . . . . . . . . . . . . . . . . 5 58 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 9.1. Normative References . . . . . . . . . . . . . . . . . . . 5 60 9.2. Informative References . . . . . . . . . . . . . . . . . . 6 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 1. Introduction 65 [RFC3023] created the +xml suffix convention that may be used by 66 media types whose representation uses XML underneath, that is, they 67 could have been successfully parsed as if the media type had been 68 application/xml in addition to their being parsed as their media type 69 that is using the +xml suffix. [I-D.ietf-appsawg-media-type-regs] 70 defines a registry to be used for future Structured Syntax Suffixes. 72 A variety of Structured Syntax Suffixes have already been used in 73 some Media Type registration, in particular "+json", "+der", 74 "+fastinfoset" and "+wbxml". This document defines and registers 75 these Structured Syntax Suffixes in the Structured Syntax Suffix 76 registry, along with "+ber". 78 Discussion of this document should occur in the Apps Area Working 79 Group (apps-discuss@ietf.org). 81 2. When to Use these Structured Syntax Suffixes 83 Each of the Structured Syntax Suffixes defined in this document are 84 appropriate for use when the media type identifies the semantics of 85 the protocol payload. That is, knowing the semantics of the specific 86 media type provides for more specific processing of the content than 87 that afforded by generic processing of the underlying representation. 89 At the same time, using the suffix provides receivers of the media 90 types to do generic processing of the underyling representation in 91 cases where they do not need to handle specially the specific 92 semantics of the exact media type. 94 3. The +json Structured Syntax Suffix 96 [RFC4627] defines the "application/json" media type. The suffix 97 "+json" may be used with any media type whose representation follows 98 that established for "application/json". The Message Type Structured 99 Syntax Suffix registration form follows: 101 Name JavaScript Object Notation (JSON) 103 +suffix +json 105 References [RFC4627] 106 Encoding considerations Per [RFC4627], JSON may be represented using 107 UTF-8, UTF-16, or UTF-32. When JSON is written 108 in UTF-8, JSON is 8bit compatible. When JSON is 109 written in UTF-16 or UTF-32, JSON is binary. 111 Interoperability considerations n/a 113 Security considerations See [RFC4627] 115 Contact Apps Area Working Group (apps-discuss@ietf.org) 117 Author/Change controller The Apps Area Working Group has change 118 control over this registration. 120 4. The +ber and +der Structured Syntax Suffixes 122 The CCITT defined the Basic Encoding Rules (BER) and Distinguished 123 Encoding Rules (DER) message transfer syntaxes in [CCITT.X690.2002]. 124 The suffix "+ber" may be used with any media type whose 125 representation follows the BER message transfer syntax. The suffix 126 "+der" may be used with any media type whose representation follows 127 the DER message transfer syntax. The Message Type Structured Syntax 128 Suffix registration forms follows: 130 Name Basic Encoding Rules (BER) message transfer 131 syntax 133 +suffix +ber 135 References [CCITT.X690.2002] 137 Encoding considerations BER is a binary encoding. 139 Interoperability considerations n/a 141 Security considerations There are no security considerations inherent 142 in BER. Each individual media type registered 143 with a +ber suffix may have additional security 144 considerations. 146 Contact Apps Area Working Group (apps-discuss@ietf.org) 148 Author/Change controller The Apps Area Working Group has change 149 control over this registration. 151 Name Distinguished Encoding Rules (DER) message 152 transfer syntax 154 +suffix +der 156 References [CCITT.X690.2002] 158 Encoding considerations DER is a binary encoding. 160 Interoperability considerations n/a 162 Security considerations There are no security considerations inherent 163 in DER. Each individual media type registered 164 with a +der suffix may have additional security 165 considerations. 167 Contact Apps Area Working Group (apps-discuss@ietf.org) 169 Author/Change controller The Apps Area Working Group has change 170 control over this registration. 172 5. The +fastinfoset Structured Syntax Suffix 174 The ITU-T and ISO have defined the Fast Infoset document format as a 175 binary representation of the XML Information Set in [ITU.X891.2005] 176 and [ISO.IEC.24824-1.2007]. These documents further define the 177 "application/fastinfoset" media type. The suffix "+fastinfoset" may 178 be used with any media type whose representation follows that 179 established for "application/fastinfoset". The Message Type 180 Structured Syntax Suffix registration form follows: 182 Name Fast Infoset document format 184 +suffix +infoset 186 References [ITU.X891.2005] and [ISO.IEC.24824-1.2007] 188 Encoding considerations Fast Infoset is a binary encoding. The 189 binary, quoted-printable and base64 content- 190 transfer-encodings are suitable for use with Fast 191 Infoset. 193 Interoperability considerations n/a 195 Security considerations There are no security considerations inherent 196 in Fast Infoset. Each individual media type 197 registered with a +der suffix may have additional 198 security considerations. 200 Contact Apps Area Working Group (apps-discuss@ietf.org) 202 Author/Change controller The Apps Area Working Group has change 203 control over this registration. 205 6. The +wbxml Structured Syntax Suffix 207 The WAP Forum has defined the WAP Binary XML (WBXML) document format 208 as a binary representation of XML in [WBXML]. This document further 209 defines the "application/vnd.wap.wbxml" media type. The suffix 210 "+wbxml" may be used with any media type whose representation follows 211 that established for "application/vnd.wap.wbxml". The Message Type 212 Structured Syntax Suffix registration form follows: 214 Name WAP Binary XML (WBXML) document format 216 +suffix +wbxml 218 References [WBXML] 220 Encoding considerations WBXML is a binary encoding. 222 Interoperability considerations n/a 224 Security considerations There are no security considerations inherent 225 in WBXML. Each individual media type registered 226 with a +der suffix may have additional security 227 considerations. 229 Contact Apps Area Working Group (apps-discuss@ietf.org) 231 Author/Change controller The Apps Area Working Group has change 232 control over this registration. 234 7. IANA Considerations 236 See the Message Type Structured Syntax Suffix registration forms in 237 Section 3 - Section 6. 239 8. Security Considerations 241 See the Security considerations sections found in the Message Type 242 Structured Syntax Suffix registration forms from Section 3 - Section 243 6. 245 9. References 247 9.1. Normative References 249 [RFC4627] Crockford, D., "The application/json Media Type for 250 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 252 [CCITT.X690.2002] 253 International International Telephone and Telegraph 254 Consultative Committee, "AASN.1 encoding rules: 255 Specification of basic encoding Rules (BER), Canonical 256 encoding rules (CER) and Distinguished encoding rules 257 (DER)", CCITT Recommendation X.680, July 2002. 259 [ITU.X891.2005] 260 International Telecommunications Union, "Information 261 Technology - Generic applications of ASN.1: Fast infoset", 262 ITU-T Recommendation X.891, May 2005. 264 [ISO.IEC.24824-1.2007] 265 International Organization for Standardization, 266 "Information Technology - Generic applications of ASN.1: 267 Fast infoset", ISO Standard 24824-1, May 2007. 269 [WBXML] Open Mobile Alliance, "Binary XML Content Format 270 Specification", OMA Wireless Access Protocol 271 WAP-192-WBXML-20010725-a, July 2001. 273 9.2. Informative References 275 [RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media 276 Types", RFC 3023, January 2001. 278 [I-D.ietf-appsawg-media-type-regs] 279 Freed, N., Klensin, J. and T. Hansen, "Media Type 280 Specifications and Registration Procedures", Internet- 281 Draft draft-ietf-appsawg-media-type-regs-04, April 2012. 283 Author's Address 285 Tony Hansen 286 AT&T Laboratories 287 200 Laurel Ave. South 288 Middletown, NJ 07748 289 USA 291 Email: tony+sss@maillennium.att.com