Skip to main content

Additional Media Type Structured Syntax Suffixes
draft-hansen-media-type-suffix-regs-00

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Author Tony Hansen
Last updated 2012-04-04
Replaced by draft-ietf-appsawg-media-type-suffix-regs, RFC 6839
RFC stream (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date (None)
Responsible AD (None)
Send notices to (None)
draft-hansen-media-type-suffix-regs-00
Network Working Group                                          T. Hansen
Internet-Draft                                         AT&T Laboratories
Intended status: Standards Track                          April 05, 2012
Expires: October 05, 2012

            Additional Media Type Structured Syntax Suffixes
               draft-hansen-media-type-suffix-regs-00

Abstract

   This document defines several Structured Syntax Suffixes for use with
   media type registrations.  In particular, it defines and registers
   the "+json", "+der", "+fastinfoset" and "+wbxml" Structured Syntax
   Suffixes.

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 October 05, 2012.

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.  The +json Structured Syntax Suffix . . . . . . . . . . . . . .  2
   4.  The +der Structured Syntax Suffix  . . . . . . . . . . . . . .  3

Hansen                  Expires October 05, 2012                [Page 1]
Internet-Draft       Additional Media Type Suffixes           April 2012

   5.  The +fastinfoset Structured Syntax Suffix  . . . . . . . . . .  3
   6.  The +wbxml Structured Syntax Suffix  . . . . . . . . . . . . .  3
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  4
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     9.1.  Normative References . . . . . . . . . . . . . . . . . . .  4
     9.2.  Informative References . . . . . . . . . . . . . . . . . .  5
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  5

1.  Introduction

   [RFC3023] created the +xml suffix convention that may be used by
   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 a registry to be used for future Structured Syntax Suffixes.

   A variety of Structured Syntax Suffixes have already been used in
   some Media Type registration, in particular "+json", "+der",
   "+fastinfoset" and "+wbxml".  This document defines and registers
   these four Structured Syntax Suffixes in the Structured Syntax Suffix
   registry.

   Discussion of this document should occur in the Apps Area Working
   Group (apps-discuss@ietf.org).

2.  When to Use these Structured Syntax Suffixes

   Each of the Structured Syntax Suffixes defined in this document are
   appropriate for use when the media type identifies the semantics of
   the protocol payload.  That is, knowing the semantics of the specific
   media type provides for more specific processing of the content than
   that afforded by generic processing of the underlying representation.

   At the same time, using the suffix provides receivers of the media
   types to do generic processing of the underyling representation in
   cases where they do not need to handle specially the specific
   semantics of the exact media type.

3.  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 Structured Syntax
   Suffix registration form follows:

   Name                JavaScript Object Notation (JSON)
   +suffix             +json
   References          [RFC4627]
   Encoding considerations Per [RFC4627], JSON may be represented using
                       UTF-8, UTF-16, or UTF-32.  When JSON is written
                       in UTF-8, JSON is 8bit compatible.  When JSON is
                       written in UTF-16 or UTF-32, JSON is binary.
   Interoperability considerations n/a
   Security considerations See [RFC4627]

Hansen                  Expires October 05, 2012                [Page 2]
Internet-Draft       Additional Media Type Suffixes           April 2012

   Contact             Apps Area Working Group (apps-discuss@ietf.org)
   Author/Change controller The Apps Area Working Group has change
                       control over this registration.

4.  The +der Structured Syntax Suffix

   The CCITT defined the Distinguished Encoding Rules (DER) message
   transfer syntax in [CCITT.X690.2002].  The suffix "+der" may be used
   with any media type whose representation follows the DER message
   transfer syntax.  The Structured Syntax Suffix registration form
   follows:

   Name                Distinguished Encoding Rules (DER) message
                       transfer syntax
   +suffix             +der
   References          [CCITT.X690.2002]
   Encoding considerations DER is a binary encoding.
   Interoperability considerations n/a
   Security considerations There are no security considerations inherent
                       in DER. Each individual media type registered
                       with a +der suffix may have additional security
                       considerations.
   Contact             Apps Area Working Group (apps-discuss@ietf.org)
   Author/Change controller The Apps Area Working Group has change
                       control over this registration.

5.  The +fastinfoset Structured Syntax Suffix

   The ITU-T and ISO have defined the Fast Infoset document format as a
   binary representation of the XML Information Set in [ITU.X891.2005]
   and [ISO.IEC.24824-1.2007].  These documents further define the
   "application/fastinfoset" media type.  The suffix "+fastinfoset" may
   be used with any media type whose representation follows that
   established for "application/fastinfoset".  The Structured Syntax
   Suffix registration form follows:

   Name                Fast Infoset document format
   +suffix             +infoset
   References          [ITU.X891.2005] and [ISO.IEC.24824-1.2007]
   Encoding considerations Fast Infoset is a binary encoding.  The
                       binary, quoted-printable and base64 content-
                       transfer-encodings are suitable for use with Fast
                       Infoset.
   Interoperability considerations n/a
   Security considerations There are no security considerations inherent
                       in Fast Infoset.  Each individual media type
                       registered with a +der suffix may have additional
                       security considerations.
   Contact             Apps Area Working Group (apps-discuss@ietf.org)
   Author/Change controller The Apps Area Working Group has change
                       control over this registration.

6.  The +wbxml Structured Syntax Suffix

Hansen                  Expires October 05, 2012                [Page 3]
Internet-Draft       Additional Media Type Suffixes           April 2012

   The WAP Forum has defined the WAP Binary XML (WBXML) document format
   as a binary representation of XML in [WBXML].  This document further
   defines the "application/vnd.wap.wbxml" media type.  The suffix
   "+wbxml" may be used with any media type whose representation follows
   that established for "application/vnd.wap.wbxml".  The Structured
   Syntax Suffix registration form follows:

   Name                WAP Binary XML (WBXML) document format
   +suffix             +wbxml
   References          [WBXML]
   Encoding considerations WBXML is a binary encoding.
   Interoperability considerations n/a
   Security considerations There are no security considerations inherent
                       in WBXML.  Each individual media type registered
                       with a +der suffix may have additional security
                       considerations.
   Contact             Apps Area Working Group (apps-discuss@ietf.org)
   Author/Change controller The Apps Area Working Group has change
                       control over this registration.

7.  IANA Considerations

   See the Structured Syntax Suffix registration forms in sections 2-5.

8.  Security Considerations

   See the Security considerations sections found in the Structured
   Syntax Suffix registration forms from sections 2-5.

9.  References

9.1.  Normative References

   [1]        Crockford, D., "The application/json Media Type for
              JavaScript Object Notation (JSON)", RFC 4627, July 2006.

   [2]        International International Telephone and Telegraph
              Consultative Committee, "AASN.1 encoding rules:
              Specification of basic encoding Rules (BER), Canonical
              encoding rules (CER) and Distinguished encoding rules
              (DER)", CCITT Recommendation X.680, July 2002.

   [3]        International Telecommunications Union, "Information
              Technology - Generic applications of ASN.1: Fast infoset",
              ITU-T Recommendation X.891, May 2005.

   [4]        International Organization for Standardization,
              "Information Technology - Generic applications of ASN.1:
              Fast infoset", ISO Standard 24824-1, May 2007.

   [5]        Open Mobile Alliance, "Binary XML Content Format
              Specification", OMA Wireless Access Protocol
              WAP-192-WBXML-20010725-a, July 2001.

Hansen                  Expires October 05, 2012                [Page 4]
Internet-Draft       Additional Media Type Suffixes           April 2012

9.2.  Informative References

   [1]        Murata, M., St.  Laurent, S. and D. Kohn, "XML Media
              Types", RFC 3023, January 2001.

   [2]        Freed, N., Klensin, J. and T. Hansen, "Media Type
              Specifications and Registration Procedures", Internet-
              Draft draft-ietf-appsawg-media-type-regs-04, April 2012.

Author's Address

   Tony Hansen
   AT&T Laboratories
   200 Laurel Ave. South
   Middletown, NJ 07748
   USA
   
   Email: tony+sss@maillennium.att.com

Hansen                  Expires October 05, 2012                [Page 5]