idnits 2.17.00 (12 Aug 2021) /tmp/idnits4618/draft-hansen-media-type-suffix-regs-00.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 05, 2012) is 3697 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) -- Looks like a reference, but probably isn't: 'RFC3023' on line 65 -- Looks like a reference, but probably isn't: 'I-D.ietf-appsawg-media-type-regs' on line 69 -- Looks like a reference, but probably isn't: 'RFC4627' on line 109 -- Looks like a reference, but probably isn't: 'ITU.X891.2005' on line 148 -- Looks like a reference, but probably isn't: 'WBXML' on line 172 == Unused Reference: '1' is defined on line 219, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 222, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 205, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 209, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 213, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3023 (ref. '1') (Obsoleted by RFC 7303) == Outdated reference: draft-ietf-appsawg-media-type-regs has been published as RFC 6838 -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 1 error (**), 0 flaws (~~), 8 warnings (==), 9 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 05, 2012 5 Expires: October 05, 2012 7 Additional Media Type Structured Syntax Suffixes 8 draft-hansen-media-type-suffix-regs-00 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", "+der", "+fastinfoset" and "+wbxml" Structured Syntax 15 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 05, 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 +der Structured Syntax Suffix . . . . . . . . . . . . . . 3 54 5. The +fastinfoset Structured Syntax Suffix . . . . . . . . . . 3 55 6. The +wbxml Structured Syntax Suffix . . . . . . . . . . . . . 3 56 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 57 8. Security Considerations . . . . . . . . . . . . . . . . . . . 4 58 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 9.1. Normative References . . . . . . . . . . . . . . . . . . . 4 60 9.2. Informative References . . . . . . . . . . . . . . . . . . 5 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 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 four Structured Syntax Suffixes in the Structured Syntax Suffix 76 registry. 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 Structured Syntax 99 Suffix registration form follows: 101 Name JavaScript Object Notation (JSON) 102 +suffix +json 103 References [RFC4627] 104 Encoding considerations Per [RFC4627], JSON may be represented using 105 UTF-8, UTF-16, or UTF-32. When JSON is written 106 in UTF-8, JSON is 8bit compatible. When JSON is 107 written in UTF-16 or UTF-32, JSON is binary. 108 Interoperability considerations n/a 109 Security considerations See [RFC4627] 110 Contact Apps Area Working Group (apps-discuss@ietf.org) 111 Author/Change controller The Apps Area Working Group has change 112 control over this registration. 114 4. The +der Structured Syntax Suffix 116 The CCITT defined the Distinguished Encoding Rules (DER) message 117 transfer syntax in [CCITT.X690.2002]. The suffix "+der" may be used 118 with any media type whose representation follows the DER message 119 transfer syntax. The Structured Syntax Suffix registration form 120 follows: 122 Name Distinguished Encoding Rules (DER) message 123 transfer syntax 124 +suffix +der 125 References [CCITT.X690.2002] 126 Encoding considerations DER is a binary encoding. 127 Interoperability considerations n/a 128 Security considerations There are no security considerations inherent 129 in DER. Each individual media type registered 130 with a +der suffix may have additional security 131 considerations. 132 Contact Apps Area Working Group (apps-discuss@ietf.org) 133 Author/Change controller The Apps Area Working Group has change 134 control over this registration. 136 5. The +fastinfoset Structured Syntax Suffix 138 The ITU-T and ISO have defined the Fast Infoset document format as a 139 binary representation of the XML Information Set in [ITU.X891.2005] 140 and [ISO.IEC.24824-1.2007]. These documents further define the 141 "application/fastinfoset" media type. The suffix "+fastinfoset" may 142 be used with any media type whose representation follows that 143 established for "application/fastinfoset". The Structured Syntax 144 Suffix registration form follows: 146 Name Fast Infoset document format 147 +suffix +infoset 148 References [ITU.X891.2005] and [ISO.IEC.24824-1.2007] 149 Encoding considerations Fast Infoset is a binary encoding. The 150 binary, quoted-printable and base64 content- 151 transfer-encodings are suitable for use with Fast 152 Infoset. 153 Interoperability considerations n/a 154 Security considerations There are no security considerations inherent 155 in Fast Infoset. Each individual media type 156 registered with a +der suffix may have additional 157 security considerations. 158 Contact Apps Area Working Group (apps-discuss@ietf.org) 159 Author/Change controller The Apps Area Working Group has change 160 control over this registration. 162 6. The +wbxml Structured Syntax Suffix 163 The WAP Forum has defined the WAP Binary XML (WBXML) document format 164 as a binary representation of XML in [WBXML]. This document further 165 defines the "application/vnd.wap.wbxml" media type. The suffix 166 "+wbxml" may be used with any media type whose representation follows 167 that established for "application/vnd.wap.wbxml". The Structured 168 Syntax Suffix registration form follows: 170 Name WAP Binary XML (WBXML) document format 171 +suffix +wbxml 172 References [WBXML] 173 Encoding considerations WBXML is a binary encoding. 174 Interoperability considerations n/a 175 Security considerations There are no security considerations inherent 176 in WBXML. Each individual media type registered 177 with a +der suffix may have additional security 178 considerations. 179 Contact Apps Area Working Group (apps-discuss@ietf.org) 180 Author/Change controller The Apps Area Working Group has change 181 control over this registration. 183 7. IANA Considerations 185 See the Structured Syntax Suffix registration forms in sections 2-5. 187 8. Security Considerations 189 See the Security considerations sections found in the Structured 190 Syntax Suffix registration forms from sections 2-5. 192 9. References 194 9.1. Normative References 196 [1] Crockford, D., "The application/json Media Type for 197 JavaScript Object Notation (JSON)", RFC 4627, July 2006. 199 [2] International International Telephone and Telegraph 200 Consultative Committee, "AASN.1 encoding rules: 201 Specification of basic encoding Rules (BER), Canonical 202 encoding rules (CER) and Distinguished encoding rules 203 (DER)", CCITT Recommendation X.680, July 2002. 205 [3] International Telecommunications Union, "Information 206 Technology - Generic applications of ASN.1: Fast infoset", 207 ITU-T Recommendation X.891, May 2005. 209 [4] International Organization for Standardization, 210 "Information Technology - Generic applications of ASN.1: 211 Fast infoset", ISO Standard 24824-1, May 2007. 213 [5] Open Mobile Alliance, "Binary XML Content Format 214 Specification", OMA Wireless Access Protocol 215 WAP-192-WBXML-20010725-a, July 2001. 217 9.2. Informative References 219 [1] Murata, M., St. Laurent, S. and D. Kohn, "XML Media 220 Types", RFC 3023, January 2001. 222 [2] Freed, N., Klensin, J. and T. Hansen, "Media Type 223 Specifications and Registration Procedures", Internet- 224 Draft draft-ietf-appsawg-media-type-regs-04, April 2012. 226 Author's Address 228 Tony Hansen 229 AT&T Laboratories 230 200 Laurel Ave. South 231 Middletown, NJ 07748 232 USA 234 Email: tony+sss@maillennium.att.com