One document matched: draft-hansen-media-type-suffix-regs-00.xml

<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc='yes' ?>
<?rfc symrefs='no' ?>
<?rfc sortrefs='no'?>
<?rfc linkmailto='no'?>
<?rfc compact='yes'?>
<?rfc comments='yes'?>
<?rfc inline='yes'?>
<?rfc-ext parse-xml-in-artwork='yes' ?>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<rfc ipr='trust200902' docName='draft-hansen-media-type-suffix-regs' category='std'>
  <front>
    <title abbrev='Additional Media Type Suffixes'>Additional Media Type Structured Syntax Suffixes</title>
    <author initials='T.' surname='Hansen' fullname='Tony Hansen'>
      <organization>AT&T Laboratories</organization>
      <address>
        <postal>
          <street>200 Laurel Ave. South</street>
          <city>Middletown</city>
          <region>NJ</region>
          <code>07748</code>
          <country>USA</country>
        </postal>
        <email>tony+sss@maillennium.att.com</email>
      </address>
    </author>
    <date />
    <area>Applications</area>
    <abstract>
      <t>
	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.
      </t>
    </abstract>
  </front>
  <middle>
    <section title='Introduction'>
      <t>
	<xref target='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.
	<xref target='I-D.ietf-appsawg-media-type-regs'/> defines a registry to be used
	for future Structured Syntax Suffixes.
      </t>
      <t>
	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.
	<!--
	    <a>dssc+der</a>
	    
	    <a href="/assignments/media-types/application/soap+fastinfoset">soap+fastinfoset</a>
	    
	    <a href="/assignments/media-types/application/vnd.collection+json">vnd.collection+json</a>
	    <a href="/assignments/media-types/application/vnd.hal+json">vnd.hal+json</a>
	    <a href="/assignments/media-types/application/vnd.oftn.l10n+json">vnd.oftn.l10n+json</a>
	    
	    <a href="/assignments/media-types/application/vnd.nokia.conml+wbxml">vnd.nokia.conml+wbxml</a>
	    <a href="/assignments/media-types/application/vnd.nokia.landmark+wbxml">vnd.nokia.landmark+wbxml</a>
	    <a href="/assignments/media-types/application/vnd.nokia.pcd+wbxml">vnd.nokia.pcd+wbxml</a>
	    <a href="/assignments/media-types/application/vnd.syncml.dm+wbxml">vnd.syncml.dm+wbxml</a>
	    <a href="/assignments/media-types/application/vnd.wv.csp+wbxml">vnd.wv.csp+wbxml</a>
	    
	    -->
      </t>
      <t>
	Discussion of this document should occur in the Apps Area Working Group (apps-discuss@ietf.org).
      </t>
    </section>
    <section title='When to Use these Structured Syntax Suffixes'>
      <t>
	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.
      </t>
      <t>
	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.
      </t>
    </section>

    <section title='The +json Structured Syntax Suffix'>
      <t>
	<xref target='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:
	<list style='hanging' hangIndent='20'>
	  <t hangText='Name'>
	    JavaScript Object Notation (JSON)
	  </t>
	  <t hangText='+suffix'>
	    +json
	  </t>
	  <t hangText='References'>
	    <xref target='RFC4627'/>
	  </t>
	  <t hangText='Encoding considerations'>
	    Per <xref target='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.
	  </t>
	  <t hangText='Interoperability considerations'>
	    n/a
	  </t>
	  <t hangText='Security considerations'>
	    See <xref target='RFC4627'/>
	  </t>
	  <t hangText='Contact'>
	    Apps Area Working Group (apps-discuss@ietf.org)
	  </t>
	  <t hangText='Author/Change controller'>
	    The Apps Area Working Group has change control over this registration.
	  </t>
	</list>
      </t>
    </section>

    <section title='The +der Structured Syntax Suffix'>
      <t>
	The CCITT defined the Distinguished Encoding Rules (DER) message
	transfer syntax in <xref target='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:
	<list style='hanging' hangIndent='20'>
	  <t hangText='Name'>
	    Distinguished Encoding Rules (DER) message transfer syntax
	  </t>
	  <t hangText='+suffix'>
	    +der
	  </t>
	  <t hangText='References'>
	    <xref target='CCITT.X690.2002'/>
	  </t>
	  <t hangText='Encoding considerations'>
	    DER is a binary encoding.
	  </t>
	  <t hangText='Interoperability considerations'>
	    n/a
	  </t>
	  <t hangText='Security considerations'>
	    There are no security considerations inherent in DER. Each individual media type
	    registered with a +der suffix may have additional security considerations.
	  </t>
	  <t hangText='Contact'>
	    Apps Area Working Group (apps-discuss@ietf.org)
	  </t>
	  <t hangText='Author/Change controller'>
	    The Apps Area Working Group has change control over this registration.
	  </t>
	</list>
      </t>
    </section>

    <section title='The +fastinfoset Structured Syntax Suffix'>
      <t>
	The ITU-T and ISO have defined the Fast Infoset
	document format as a binary representation of the XML Information Set in
	<xref target='ITU.X891.2005'/> and <xref target='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:
	<list style='hanging' hangIndent='20'>
	  <t hangText='Name'>
	    Fast Infoset document format
	  </t>
	  <t hangText='+suffix'>
	    +infoset
	  </t>
	  <t hangText='References'>
	    <xref target='ITU.X891.2005'/> and <xref target='ISO.IEC.24824-1.2007'/>
	  </t>
	  <t hangText='Encoding considerations'>
	    Fast Infoset is a binary encoding. The binary, quoted-printable and base64 content-transfer-encodings
	    are suitable for use with Fast Infoset.
	  </t>
	  <t hangText='Interoperability considerations'>
	    n/a
	  </t>
	  <t hangText='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.
	  </t>
	  <t hangText='Contact'>
	    Apps Area Working Group (apps-discuss@ietf.org)
	  </t>
	  <t hangText='Author/Change controller'>
	    The Apps Area Working Group has change control over this registration.
	  </t>
	</list>
      </t>
    </section>

    <section title='The +wbxml Structured Syntax Suffix'>
      <t>
	The WAP Forum has defined the WAP Binary XML (WBXML) document format
	as a binary representation of XML in <xref target='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:
	<list style='hanging' hangIndent='20'>
	  <t hangText='Name'>
	    WAP Binary XML (WBXML) document format
	  </t>
	  <t hangText='+suffix'>
	    +wbxml
	  </t>
	  <t hangText='References'>
	    <xref target='WBXML'/>
	  </t>
	  <t hangText='Encoding considerations'>
	    WBXML is a binary encoding.
	  </t>
	  <t hangText='Interoperability considerations'>
	    n/a
	  </t>
	  <t hangText='Security considerations'>
	    There are no security considerations inherent in WBXML.
	    Each individual media type registered with a +der suffix may have additional security considerations.
	  </t>
	  <t hangText='Contact'>
	    Apps Area Working Group (apps-discuss@ietf.org)
	  </t>
	  <t hangText='Author/Change controller'>
	    The Apps Area Working Group has change control over this registration.
	  </t>
	</list>
      </t>
    </section>

    <section title='IANA Considerations'>
      <t>
	See the Structured Syntax Suffix registration forms in sections 2-5.
      </t>
    </section>

    <section title='Security Considerations'>
      <t>
	See the Security considerations sections found in the Structured Syntax 
	Suffix registration forms from sections 2-5.
      </t>
    </section>
  </middle>

  <back>
    <references title='Normative References'>
      <?rfc include='reference.RFC.4627' ?>
      <reference anchor="CCITT.X690.2002">
	<front>
	  <title>AASN.1 encoding rules:  Specification of basic
            encoding Rules (BER), Canonical encoding rules (CER) and
            Distinguished encoding rules (DER)</title>
	  <author>
	    <organization>International International Telephone and Telegraph Consultative Committee</organization>
	  </author>
	  <date month="July" year="2002" />
	</front>
	<seriesInfo name="CCITT" value="Recommendation X.680" />
	<!-- http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf -->
      </reference>
      
      <reference anchor="ITU.X891.2005">
	<front>
	  <title>Information Technology - Generic applications of ASN.1: Fast infoset</title>
	  <author>
	    <organization>International Telecommunications Union</organization>
	  </author>
	  <date month="May" year="2005" />
	</front>
	<seriesInfo name="ITU-T" value="Recommendation X.891" />
	<!-- http://www.itu.int/rec/T-REC-X.891-200505-I/en -->
      </reference>
      
      <reference anchor="ISO.IEC.24824-1.2007">
	<front>
	  <title>Information Technology - Generic applications of ASN.1: Fast infoset</title>
	  <author>
	    <organization>International Organization for Standardization</organization>
	  </author>
	  <date month="May" year="2007" />
	</front>
	<seriesInfo name="ISO" value="Standard 24824-1" />
	<!-- http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html -->
      </reference>
      
      <reference anchor="WBXML">
	<front>
	  <title>Binary XML Content Format Specification</title>
	  <author>
	    <organization>Open Mobile Alliance</organization>
	  </author>
	  <date month='July' year='2001'/>
	</front>
	<seriesInfo name='OMA' value='Wireless Access Protocol WAP-192-WBXML-20010725-a'/>
      </reference>
    </references>
    <references title='Informative References'>
      <?rfc include='reference.RFC.3023' ?>
      <?rfc include='reference.I-D.ietf-appsawg-media-type-regs' ?>
    </references>
  </back>
</rfc>