One document matched: draft-shelby-exi-registration-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3023 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3023.xml">
<!ENTITY RFC4288 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4288.xml">
<!ENTITY RFC4289 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4289.xml">

<!ENTITY W3C.REC-exi-20110310 SYSTEM "http://xml.resource.org/public/rfc/bibxml4/reference.W3C.REC-exi-20110310">

<!ENTITY I-D.murata-kohn-lilley-xml SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.murata-kohn-lilley-xml.xml">
<!ENTITY I-D.ietf-appsawg-media-type-regs SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-appsawg-media-type-regs.xml">

]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
     (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="3"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="std" ipr="trust200902" docName="draft-shelby-exi-registration-00">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>

    <front>
        <title>The +exi Media Type Suffix</title>

        <author initials="Z" surname="Shelby" fullname="Zach Shelby">
          <organization>
             Sensinode
          </organization>
          <address>
            <postal>
             <street>Kidekuja 2</street>
             <city>Vuokatti</city>
             <code>88600</code>
             <country>FINLAND</country>
            </postal>
            <phone>+358407796297</phone>
            <email>zach@sensinode.com</email>
          </address>
        </author>

  <date year="2012"/>

  <area>Internet</area>

  <workgroup>Appsawg</workgroup>
  <keyword>EXI, Media Type</keyword>

    <abstract>
    <t>
	Efficient XML Interchange (EXI) is an XML representation 
	technique specified by the W3C to provie a binary alternative to the standard text XML 
	representation. This document defines a new Structure Syntax Suffix "+exi" for use in a specific 
	class of protocols, where "exi" content-type encoding or the generic "application/exi" Media Type are 
    not applicable.
	</t> 
    
    </abstract>
    </front>

    <middle>


  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <section anchor='introduction' title="Introduction">

    <t>
	Efficient XML Interchange (EXI) <xref target="W3C.REC-exi-20110310"/> is an XML representation 
	technique specified by the W3C to provie a binary alternative to the standard text XML 
	representation. EXI is not a generic compression technique like gzip or deflate, but an encoding 
	technique specifically for XML that uses either learnt or pre-informed schema information. 
    </t>
    
    <t>
    This document defines a new Structure Syntax Suffix "+exi" for use in a specific class of 
    protocols, where the "exi" content-type encoding or generic "application/exi" Media Type defined 
    in <xref target="W3C.REC-exi-20110310"/> are not applicable. 
    </t>

  </section>

  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <section anchor='when' title="When to Use the +exi Suffix">

	<t>
	The EXI standard already defines both an "exi" content-type encoding and an 
	"application/exi" Media Type. This sections discusses when it is appropriate 
	to use the new "+exi" Structured Syntax Suffix when registring a Media Type.
	</t>

	<t>
	Appendix F.1 of <xref target="W3C.REC-exi-20110310"/> clearly describes when the 
	exi content-type encoding should be used: "Protocols that can identify and 
	negotiate the content coding of XML information independent of its media 
	type, SHOULD use the content coding "exi" (case-insensitive) to convey the 
	acceptance or actual use of EXI encoding for XML information." 
	</t>
	
	<t>
	Thus when a protocol depends on the media type to identify that the payload is EXI, it 
	can make use of the "application/exi" Media Type defined in Appendix F.2 of <xref target="W3C.REC-exi-20110310"/>. 
	This works particularly well for applications
	using EXI in a generic way, and in particular in non Schema-informed mode, where protocol specific 
	information is not needed to process the payload, in particular the XML schema used. In these 
	cases it is recommended to use the "application/exi" Media Type or "exi" content-type encoding.
	</t>
	
	<t>
	The "+exi" Structure Syntax Suffix defined in this document is appropriate for use with protocols 
	that:
	
	<list style="symbols">
		<t>Make use of a Media Type to identify the semantics of the protocol payload, and offer 
		more that one serialization of the payloads. For example, some protocols may offer JSON, XML 
		and EXI representations. </t>
		
		<t>Use EXI as a native encoding (without the use of XML as an interemediate) in Strict 
		Schema-informed mode, and the base Media Type indicates to the protocol the Schema that 
		was used to produce the EXI grammar.</t>
	</list>
	</t>
	
  </section>

  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->

  <section anchor='security' title="Security Considerations">
         <t> 
         Security considerations are discussed in <xref target="iana"/>.
     	 </t>

  </section>


  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->

  <section anchor='iana' title="IANA Considerations">

	<t>
	This document requests registration of the Structured Syntax Suffix "+exi" as follows, 
	following the registration template from Section 6.2 of 
	<xref target="I-D.ietf-appsawg-media-type-regs"/>.
	</t>
	
	<t>

	<list style="hanging">
     <t hangText="Name:">
       Efficient XML Interchange
       </t>
       
     <t hangText="+suffix:">
       "+exi"
       </t>

	 <t hangText="References:">
       The EXI standard is defined in <xref target="W3C.REC-exi-20110310"/>, in particular
       Schema-informed Grammars are defined in Section 8.5 and the "applicatio/exi" Media Type 
       is defined in Appendix F.2.
       
       </t>

	 <t hangText="Encoding considerations:">
       Binary
       </t>

	 <t hangText="Interoperability considerations:">
       The registration of a Media Type using this suffix MUST reference the XML Schema that is 
       used to encode/decode a payload identified by that Media Type. If multi versions of this 
       Schema will evolve during the lifetime of the protocol, the protocol MUST either register 
       multiple Media Types (one for each version) or use the Schema ID option of EXI  
       to indicate the version of the Schema. 
       </t>

	 <t hangText="Security considerations:">
       The "+exi" suffix shares the same security considerations as XML, described in
       <xref target="RFC3023"/>, Section 10. In addition, the security considerations discussed 
       in the Media Type registration for "application/exi" apply as defined in Appendix F.2 of 
       <xref target="W3C.REC-exi-20110310"/>. 
       </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="Acknowledgments">

	<t>
	This draft is the result of discussions on the Apps Area Working Group mailing list.
	</t>

</section>

  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->
  <!-- **************************************************************** -->

  <section title="Changelog">

  </section>

    </middle>

    <back>
    <references title='Normative References'>
    	&W3C.REC-exi-20110310;
    	&I-D.ietf-appsawg-media-type-regs;
       
    </references>

    <references title='Informative References'>
		&RFC3023;
       
    </references>
    </back>

</rfc>