--- 1/draft-ietf-appsawg-media-type-suffix-regs-02.txt 2012-09-11 21:14:05.417342583 +0200 +++ 2/draft-ietf-appsawg-media-type-suffix-regs-03.txt 2012-09-11 21:14:05.453341701 +0200 @@ -1,91 +1,92 @@ Network Working Group T. Hansen Internet-Draft AT&T Laboratories -Updates: 3023 (if approved) July 17, 2012 -Intended status: Best Current Practice -Expires: January 16, 2013 +Updates: 3023 (if approved) A. Melnikov +Intended status: BCP Isode Ltd +Expires: March 15, 2013 September 11, 2012 Additional Media Type Structured Syntax Suffixes - draft-ietf-appsawg-media-type-suffix-regs-02 + draft-ietf-appsawg-media-type-suffix-regs-03 Abstract A content media type name sometimes includes partitioned meta- information distinguish by a Structured Syntax, to permit noting an attribute of the media as a suffix to the name. This document defines several Structured Syntax Suffixes for use with media type registrations. In particular, it defines and registers the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" Structured Syntax Suffixes, and updates the "+xml" Message Type Structured Syntax Suffix registration. -Status of This Memo +Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on January 16, 2013. + This Internet-Draft will expire on March 15, 2013. Copyright Notice Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2. When to Use these Structured Syntax Suffixes . . . . . . . . . 2 - 3. Initial Structured Syntax Suffix Definitions . . . . . . . . . 3 - 3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 3 - 3.2. The +ber Structured Syntax Suffixes . . . . . . . . . . . 4 - 3.3. The +der Structured Syntax Suffixes . . . . . . . . . . . 5 - 3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 6 - 3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 7 - 3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 8 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 - 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 6.1. Normative References . . . . . . . . . . . . . . . . . . . 10 - 6.2. Informative References . . . . . . . . . . . . . . . . . . 10 - Appendix A. Change History . . . . . . . . . . . . . . . . . . . . 11 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2. When to Use these Structured Syntax Suffixes . . . . . . . . . 3 + 3. Initial Structured Syntax Suffix Definitions . . . . . . . . . 4 + 3.1. The +json Structured Syntax Suffix . . . . . . . . . . . . 4 + 3.2. The +ber Structured Syntax Suffixes . . . . . . . . . . . 5 + 3.3. The +der Structured Syntax Suffixes . . . . . . . . . . . 6 + 3.4. The +fastinfoset Structured Syntax Suffix . . . . . . . . 8 + 3.5. The +wbxml Structured Syntax Suffix . . . . . . . . . . . 9 + 3.6. The +zip Structured Syntax Suffix . . . . . . . . . . . . 10 + 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 + 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 + 6.1. Normative References . . . . . . . . . . . . . . . . . . . 13 + 6.2. Informative References . . . . . . . . . . . . . . . . . . 13 + Appendix A. Change History . . . . . . . . . . . . . . . . . . . 13 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14 1. Introduction [RFC3023] created the +xml suffix convention that can be used when defining names for media types whose representation uses XML underneath. That is, they could have been successfully parsed as if the media type had been application/xml in addition to their being - parsed as their media type that is using the +xml suffix. [I-D.ietf- - appsawg-media-type-regs] defines the Message Type Structured Syntax - Suffixes registry to be used for such Structured Syntax Suffixes. + parsed as their media type that is using the +xml suffix. + [I-D.ietf-appsawg-media-type-regs] defines the Message Type + Structured Syntax Suffixes registry to be used for such Structured + Syntax Suffixes. A variety of Structured Syntax Suffixes have already been used in some media type registrations, in particular "+json", "+der", "+fastinfoset" and "+wbxml". This document defines and registers these Structured Syntax Suffixes in the Structured Syntax Suffix registry, along with "+ber" and "+zip". In addition, this document updates the "+xml" Structured Syntax Suffix registration. Discussion of this document should occur in the Apps Area Working Group (apps-discuss@ietf.org). [RFC Editor note: remove this @@ -115,23 +116,23 @@ would be needed to parse any example of that underlying representation. 3. Initial Structured Syntax Suffix Definitions 3.1. The +json Structured Syntax Suffix [RFC4627] defines the "application/json" media type. The suffix "+json" MAY be used with any media type whose representation follows that established for "application/json". The Message Type Structured - Syntax Suffix registration form follows. See [I-D.ietf-appsawg- - media-type-regs] for definitions of each of the registration form - headings. + Syntax Suffix registration form follows. See + [I-D.ietf-appsawg-media-type-regs] for definitions of each of the + registration form headings. Name: JavaScript Object Notation (JSON) +suffix: +json References: [RFC4627] Encoding considerations: Per [RFC4627], JSON is allowed to be represented using UTF-8, UTF-16, or UTF-32. When JSON is written in UTF-8, JSON is 8bit compatible @@ -182,26 +183,46 @@ Name: Basic Encoding Rules (BER) message transfer syntax +suffix: +ber References: [ITU.X690.2008] Encoding considerations: BER is a binary encoding. - Fragment identifier considerations: n/a + Fragment identifier considerations: + + At publication of this document, there is no + fragment identification syntax defined for + +ber. + + The syntax and semantics for fragment + identifiers for a specific "xxx/yyy+ber" + SHOULD be processed as follows: + + For cases defined in +ber, where the + fragment identifier resolves per the +ber + rules, then as specified in +ber. + + For cases defined in +ber, where the + fragment identifier does not resolve per + the +ber rules, then as specified in "xxx/ + yyy+ber". + + For cases not defined in +ber, then as + specified in "xxx/yyy+ber". Interoperability considerations: n/a - Security considerations: Each individual media type registered with a - +ber suffix can have additional security + Security considerations: Each individual media type registered with + a +ber suffix can have additional security considerations. BER has a type-length-value structure, and it is easy to construct malicious content with invalid length fields that can cause buffer overrun conditions. Some BER schema allow for arbitrary levels of nesting, which may make it possible to construct malicious content that will cause a stack @@ -225,29 +246,48 @@ with any media type whose representation follows the DER message transfer syntax. The Message Type Structured Syntax Suffix registration form for +der follows: Name: Distinguished Encoding Rules (DER) message transfer syntax +suffix: +der References: [ITU.X690.2008] - Encoding considerations: DER is a binary encoding. - Fragment identifier considerations: n/a + Fragment identifier considerations: + + At publication of this document, there is no + fragment identification syntax defined for + +der. + + The syntax and semantics for fragment + identifiers for a specific "xxx/yyy+der" + SHOULD be processed as follows: + + For cases defined in +der, where the + fragment identifier resolves per the +der + rules, then as specified in +der. + + For cases defined in +der, where the + fragment identifier does not resolve per + the +der rules, then as specified in "xxx/ + yyy+der". + + For cases not defined in +der, then as + specified in "xxx/yyy+der". Interoperability considerations: n/a - Security considerations: Each individual media type registered with a - +ber suffix can have additional security + Security considerations: Each individual media type registered with + a +der suffix can have additional security considerations. DER has a type-length-value structure, and it is easy to construct malicious content with invalid length fields that can cause buffer overrun conditions. Some DER schema allow for arbitrary levels of nesting, which may make it possible to construct malicious content that will cause a stack @@ -353,22 +392,22 @@ The syntax and semantics for fragment identifiers for a specific "xxx/yyy+wbxml" SHOULD be processed as follows: For cases defined in +wbxml, where the fragment identifier resolves per the +wbxml rules, then as specified in +wbxml. For cases defined in +wbxml, where the fragment identifier does not resolve per - the +wbxml rules, then as specified in "xxx - /yyy+wbxml". + the +wbxml rules, then as specified in + "xxx/yyy+wbxml". For cases not defined in +wbxml, then as specified in "xxx/yyy+wbxml". Interoperability considerations: n/a Security considerations: There are no security considerations inherent in WBXML. Each individual media type registered with a +wbxml suffix can have additional security considerations. @@ -469,94 +507,109 @@ For cases not defined in +xml, then as specified in "xxx/yyy+xml". 5. Security Considerations See the Security considerations sections found in the Message Type Structured Syntax Suffix registration forms from Section 3.1 - Section 3.5. -6. References + When updating a + registration care should be taken to review + all previously registered xxx/yyy+ media types regarding + whether they might be affected by the updated + registration, + in particular by introduction of new or changing generic fragment + identifier processing rules, as such rules take precedence over + media-type-specific rules and thus might break existing registrations + of specific media types, as well as particular implementations of + applications that process affected media types. Such changes can + introduce interoperability and security issues. +6. References 6.1. Normative References [RFC4627] Crockford, D., "The application/json Media Type for JavaScript Object Notation (JSON)", RFC 4627, July 2006. [ITU.X690.2008] International Telecommunications Union, "Recommendation ITU-T X.690 | ISO/IEC 8825-1 (2008), ASN.1 encoding rules: Specification of basic encoding Rules (BER), Canonical encoding rules (CER) and Distinguished encoding rules (DER)", ITU-T Recommendation X.690, November 2008. [ITU.X891.2005] International Telecommunications Union, "Recommendation ITU-T X.891 | ISO/IEC 24824-1 (2007), Generic applications - of ASN.1: Fast infoset", ITU-T Recommendation X.891, May - 2005. + of ASN.1: Fast infoset", ITU-T Recommendation X.891, + May 2005. [WBXML] Open Mobile Alliance, "Binary XML Content Format - Specification", OMA Wireless Access Protocol - WAP-192-WBXML-20010725-a, July 2001. + Specification", OMA Wireless Access Protocol WAP-192- + WBXML-20010725-a, July 2001. [ZIP] PKWARE, Inc., "APPNOTE.TXT - .ZIP File Format Specification", PKWARE .ZIP File Format Specification - Version 6.3.2, September 2007. - [RFC2045] Freed, N. and N.S. Borenstein, "Multipurpose Internet Mail + [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. - [RFC3023] Murata, M., St. Laurent, S. and D. Kohn, "XML Media + [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001. 6.2. Informative References [I-D.ietf-appsawg-media-type-regs] - Freed, N., Klensin, J. and T. Hansen, "Media Type - Specifications and Registration Procedures", Internet- - Draft draft-ietf-appsawg-media-type-regs-14, June 2012. + Freed, N., Klensin, J., and T. Hansen, "Media Type + Specifications and Registration Procedures", + draft-ietf-appsawg-media-type-regs-14 (work in progress), + June 2012. Appendix A. Change History This section is to be removed before publication. draft-ietf-appsawg-media-type-suffix-regs-02 Added BER/DER security considerations. - Reworked fragment - identifier wording some more. + Reworked fragment identifier wording some more. draft-ietf-appsawg-media-type-suffix-regs-01 Reordered the sections. Cleaned up some MUSTard. Fixed some references. - Added encoding - considerations. - Reworked fragment - identifier wording. + Added encoding considerations. + Reworked fragment identifier wording. draft-ietf-appsawg-media-type-suffix-regs-00 Added the fragment identifier consideration sections. - Added a note about +xml - fragment identifier considerations. + Added a note about +xml fragment identifier + considerations. draft-hansen-media-type-suffix-regs-02 Added +zip. - Fixed up the ISO document - references. + Fixed up the ISO document references. Minor changes. draft-hansen-media-type-suffix-regs-01 Added +ber. Minor changes. -Author's Address +Authors' Addresses Tony Hansen AT&T Laboratories 200 Laurel Ave. South Middletown, NJ 07748 USA Email: tony+sss@maillennium.att.com + + Alexey Melnikov + Isode Ltd + 5 Castle Business Village + 36 Station Road + Hampton, Middlesex TW12 2BX + UK + + Email: Alexey.Melnikov@isode.com