<pre>Internet Engineering Task Force (IETF)                         T. Hansen
Request for Comments: 6839                             AT&amp;T Laboratories
Updates: <a href="./rfc3023">3023</a>                                                A. Melnikov
Category: Informational                                        Isode Ltd
ISSN: 2070-1721                                             January 2013


            <span class="h1">Additional Media Type Structured Syntax Suffixes</span>

Abstract

   A content media type name sometimes includes partitioned meta-
   information distinguished 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 provides a media type structured syntax suffix
   registration form for the "+xml" structured syntax suffix.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc6839">http://www.rfc-editor.org/info/rfc6839</a>.
















<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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

   <a href="#section-1">1</a>.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  <a href="#page-3">3</a>
   <a href="#section-2">2</a>.  When to Use These Structured Syntax Suffixes . . . . . . . . .  <a href="#page-3">3</a>
   <a href="#section-3">3</a>.  Initial Structured Syntax Suffix Definitions . . . . . . . . .  <a href="#page-4">4</a>
     <a href="#section-3.1">3.1</a>.  The +json Structured Syntax Suffix . . . . . . . . . . . .  <a href="#page-4">4</a>
     <a href="#section-3.2">3.2</a>.  The +ber Structured Syntax Suffix  . . . . . . . . . . . .  <a href="#page-5">5</a>
     <a href="#section-3.3">3.3</a>.  The +der Structured Syntax Suffix  . . . . . . . . . . . .  <a href="#page-6">6</a>
     <a href="#section-3.4">3.4</a>.  The +fastinfoset Structured Syntax Suffix  . . . . . . . .  <a href="#page-7">7</a>
     <a href="#section-3.5">3.5</a>.  The +wbxml Structured Syntax Suffix  . . . . . . . . . . .  <a href="#page-9">9</a>
     <a href="#section-3.6">3.6</a>.  The +zip Structured Syntax Suffix  . . . . . . . . . . . . <a href="#page-10">10</a>
   <a href="#section-4">4</a>.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
     <a href="#section-4.1">4.1</a>.  The +xml Structured Syntax Suffix  . . . . . . . . . . . . <a href="#page-11">11</a>
   <a href="#section-5">5</a>.  Security Considerations  . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
   <a href="#section-6">6</a>.  References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
     <a href="#section-6.1">6.1</a>.  Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
     <a href="#section-6.2">6.2</a>.  Informative References . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>



















<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   [<a id="ref-RFC3023">RFC3023</a>] 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.  [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>]
   defines the media type "Structured Syntax Suffix 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 [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>] to formally register the "+xml" structured syntax
   suffix according to the procedure defined in [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  When to Use These Structured Syntax Suffixes</span>

   Each of the structured syntax suffixes defined in this document is
   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 allows receivers of the media
   types to do generic processing of the underlying representation in
   cases where

      they do not need to perform special handling of the particular
      semantics of the exact media type, and

      there is no special knowledge needed by such a generic processor
      in order to parse that underlying representation other than what
      would be needed to parse any example of that underlying
      representation.










<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Initial Structured Syntax Suffix Definitions</span>

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  The +json Structured Syntax Suffix</span>

   [<a id="ref-RFC4627">RFC4627</a>] 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 media type structured
   syntax suffix registration form follows.  See [<a href="./rfc6838" title="&quot;Media Type Specifications and Registration Procedures&quot;">RFC6838</a>] for
   definitions of each of the registration form headings.

   Name:  JavaScript Object Notation (JSON)

   +suffix:  +json

   References:  [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>]

   Encoding considerations:

      Per [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>], 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 ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).  When JSON is written in UTF-16 or UTF-32,
      JSON is binary ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).

   Fragment identifier considerations:

      The syntax and semantics of fragment identifiers specified for
      +json SHOULD be as specified for "application/json".  (At
      publication of this document, there is no fragment identification
      syntax defined for "application/json".)

      The syntax and semantics for fragment identifiers for a specific
      "xxx/yyy+json" SHOULD be processed as follows:

      For cases defined in +json, where the fragment identifier resolves
      per the +json rules, then process as specified in +json.

         For cases defined in +json, where the fragment identifier does
         not resolve per the +json rules, then process as specified in
         "xxx/yyy+json".

         For cases not defined in +json, then process as specified in
         "xxx/yyy+json".

   Interoperability considerations:  n/a

   Security considerations:  See [<a href="./rfc4627" title="&quot;The application/json Media Type for JavaScript Object Notation (JSON)&quot;">RFC4627</a>]

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)



<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  The +ber Structured Syntax Suffix</span>

   The ITU defined the Basic Encoding Rules (BER) transfer syntax in
   [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>].  The suffix "+ber" MAY be used with any media type
   whose representation follows the BER transfer syntax.  (The Expert
   Reviewer for media type structured syntax suffix registrations ought
   to be aware of the relationship between BER and DER to aid in
   selecting the proper suffix.)  The media type structured syntax
   suffix registration form for +ber follows:

   Name:  Basic Encoding Rules (BER) transfer syntax

   +suffix:  +ber

   References:  [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]

   Encoding considerations:  BER is a binary encoding.

   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 process as specified in +ber.

         For cases defined in +ber, where the fragment identifier does
         not resolve per the +ber rules, then process as specified in
         "xxx/yyy+ber".

         For cases not defined in +ber, then process 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 considerations.




<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


      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.

      BER allows for arbitrary levels of nesting, which may make it
      possible to construct malicious content that will cause a stack
      overflow.

      Interpreters of the BER structures should be aware of these issues
      and should take appropriate measures to guard against buffer
      overflows and stack overruns in particular and malicious content
      in general.

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)

   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  The +der Structured Syntax Suffix</span>

   The ITU defined the Distinguished Encoding Rules (DER) transfer
   syntax in [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>].  The suffix "+der" MAY be used with any
   media type whose representation follows the DER transfer syntax.
   (The Expert Reviewer for media type structured syntax suffix
   registrations ought to be aware of the relationship between BER and
   DER to aid in selecting the proper suffix.)  The media type
   structured syntax suffix registration form for +der follows:

   Name:  Distinguished Encoding Rules (DER) transfer syntax

   +suffix:  +der

   References:  [<a href="#ref-ITU.X690.2008">ITU.X690.2008</a>]

   Encoding considerations:  DER is a binary encoding.

   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 process as specified in +der.



<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


         For cases defined in +der, where the fragment identifier does
         not resolve per the +der rules, then process as specified in
         "xxx/yyy+der".

         For cases not defined in +der, then process as specified in
         "xxx/yyy+der".

   Interoperability considerations:  n/a

   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.

      DER allows for arbitrary levels of nesting, which may make it
      possible to construct malicious content that will cause a stack
      overflow.

      Interpreters of the DER structures should be aware of these issues
      and should take appropriate measures to guard against buffer
      overflows and stack overruns in particular and malicious content
      in general.

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)

   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.

<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  The +fastinfoset Structured Syntax Suffix</span>

   The ITU defined the Fast Infoset document format as a binary
   representation of the XML Information Set in [<a href="#ref-ITU.X891.2005">ITU.X891.2005</a>].  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 media type structured syntax suffix registration
   form follows:

   Name:  Fast Infoset document format

   +suffix:  +fastinfoset




<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   References:  [<a href="#ref-ITU.X891.2005">ITU.X891.2005</a>]

   Encoding considerations:

      Fast Infoset is a binary encoding.  The binary, quoted-printable,
      and base64 content-transfer-encodings are suitable for use with
      Fast Infoset.

   Fragment identifier considerations:

      The syntax and semantics of fragment identifiers specified for
      +fastinfoset SHOULD be as specified for "application/fastinfoset".
      (At publication of this document, there is no fragment
      identification syntax defined for "application/fastinfoset".)

      The syntax and semantics for fragment identifiers for a specific
      "xxx/ yyy+fastinfoset" SHOULD be processed as follows:

         For cases defined in +fastinfoset, where the fragment
         identifier resolves per the +fastinfoset rules, then process as
         specified in +fastinfoset.

         For cases defined in +fastinfoset, where the fragment
         identifier does not resolve per the +fastinfoset rules, then
         process as specified in "xxx/yyy+fastinfoset".

         For cases not defined in +fastinfoset, then process as
         specified in "xxx/ yyy+fastinfoset".

   Interoperability considerations:  n/a

   Security considerations:

      There are no security considerations inherent in Fast Infoset.
      Each individual media type registered with a +fastinfoset suffix
      can have additional security considerations.

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)

   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.








<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>.  The +wbxml Structured Syntax Suffix</span>

   The Wireless Application Protocol (WAP) Forum has defined the WAP
   Binary XML (WBXML) document format as a binary representation of XML
   in [<a href="#ref-WBXML" title="&quot;Binary XML Content Format Specification&quot;">WBXML</a>].  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 media type structured syntax suffix
   registration form follows:

   Name:  WAP Binary XML (WBXML) document format

   +suffix:  +wbxml

   References:  [<a href="#ref-WBXML" title="&quot;Binary XML Content Format Specification&quot;">WBXML</a>]

   Encoding considerations:  WBXML is a binary encoding.

   Fragment identifier considerations:

      The syntax and semantics of fragment identifiers specified for
      +wbxml SHOULD be as specified for "application/vnd.wap.wbxml".
      (At publication of this document, there is no fragment
      identification syntax defined for "application/vnd.wap.wbxml".)

      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 process as specified in
         +wbxml.

         For cases defined in +wbxml, where the fragment identifier does
         not resolve per the +wbxml rules, then process as specified in
         "xxx/yyy+wbxml".

         For cases not defined in +wbxml, then process 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.

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)



<span class="grey">Hansen &amp; Melnikov             Informational                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.

<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>.  The +zip Structured Syntax Suffix</span>

   The ZIP format is a public domain, cross-platform, interoperable file
   storage and transfer format, originally defined by PKWARE, Inc.; it
   supports compression and encryption and is used as the underlying
   representation by a variety of file formats.  The media type
   "application/zip" has been registered for such files.  The suffix
   "+zip" MAY be used with any media type whose representation follows
   that established for "application/zip".  The media type structured
   syntax suffix registration form follows:

   Name:  ZIP file storage and transfer format

   +suffix:  +zip

   References:  [<a href="#ref-ZIP" title="&quot;APPNOTE.TXT - .ZIP File Format Specification&quot;">ZIP</a>]

   Encoding considerations:  ZIP is a binary encoding.

   Fragment identifier considerations:

      The syntax and semantics of fragment identifiers specified for
      +zip SHOULD be as specified for "application/zip".  (At
      publication of this document, there is no fragment identification
      syntax defined for "application/zip".)

      The syntax and semantics for fragment identifiers for a specific
      "xxx/yyy+zip" SHOULD be processed as follows:

         For cases defined in +zip, where the fragment identifier
         resolves per the +zip rules, then process as specified in +zip.

         For cases defined in +zip, where the fragment identifier does
         not resolve per the +zip rules, then process as specified in
         "xxx/yyy+zip".

         For cases not defined in +zip, then process as specified in
         "xxx/yyy+zip".

   Interoperability considerations:  n/a






<span class="grey">Hansen &amp; Melnikov             Informational                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   Security considerations:

      IP files support two forms of encryption: Strong Encryption and
      AES 128-bit, 192-bit, and 256-bit encryption; see the
      specification for further details.  Each individual media type
      registered with a +zip suffix can have additional security
      considerations.

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)

   Author/Change controller:  The Apps Area Working Group.  IESG has
      change control over this registration.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   See the media type structured syntax suffix registration forms in
   Sections <a href="#section-3.1">3.1</a> - <a href="#section-3.6">3.6</a>.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  The +xml Structured Syntax Suffix</span>

   The following structured syntax suffix registration for "+xml" shall
   be used to reflect the information found in [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>], with the
   addition of fragment identifier considerations.  (Note that [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]
   is in the process of being updated by [<a href="#ref-XML-MEDIATYPES">XML-MEDIATYPES</a>].)

   Name:  Extensible Markup Language (XML)

   +suffix:  +xml

   References:  [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]

   Encoding considerations:

      Per [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>], XML is allowed to be represented using both 7-bit
      and 8-bit encodings.  When XML is written in UTF-8, XML is 8bit
      compatible ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).  When XML is written in UTF-16 or UTF-32,
      XML is binary ([<a href="./rfc2045" title="&quot;Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies&quot;">RFC2045</a>]).

   Fragment identifier considerations:

      The syntax and semantics of fragment identifiers specified for
      +xml SHOULD be as specified for "application/xml".  (At
      publication of this document, the fragment identification syntax
      considerations for "application/xml" are defined in [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>],
      Sections <a href="#section-5">5</a> and <a href="#section-7">7</a>.)






<span class="grey">Hansen &amp; Melnikov             Informational                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


      The syntax and semantics for fragment identifiers for a specific
      "xxx/yyy+xml" SHOULD be processed as follows:

         For cases defined in +xml, where the fragment identifier
         resolves per the +xml rules, then process as specified in +xml.

         For cases defined in +xml, where the fragment identifier does
         not resolve per the +xml rules, then process as specified in
         "xxx/yyy+xml".

         For cases not defined in +xml, then process as specified in
         "xxx/yyy+xml".

   Interoperability considerations:  See [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>].

   Security considerations:  See [<a href="./rfc3023" title="&quot;XML Media Types&quot;">RFC3023</a>]

   Contact:  Apps Area Working Group (apps-discuss@ietf.org)

   Author/Change controller:

      The Apps Area Working Group.  IESG has change control over this
      registration.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   See the Security Considerations sections found in the media type
   structured syntax suffix registration forms from Sections <a href="#section-3">3</a> and <a href="#section-4">4</a>.

   When updating a +&lt;suffix&gt; registration, care should be taken to
   review all previously-registered xxx/yyy+&lt;suffix&gt; media types as to
   whether they might be affected by the updated +&lt;suffix&gt; registration.
   Because the generic fragment identifier processing rules take
   precedence over media-type-specific rules, introducing new or
   changing existing definitions may break the 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.

   When updating the fragment identifier processing rules for a specific
   xxx/yyy+&lt;suffix&gt; media type, care should be taken to review the
   generic fragment identifier processing rules for the +&lt;suffix&gt;
   registration and not introduce any conflicts.  Because the generic
   fragment identifier processing rules take precedence over media-type-
   specific rules, such conflicting processing requirements should be
   ignored by an implementation, but such conflicts can introduce
   interoperability and security issues.




<span class="grey">Hansen &amp; Melnikov             Informational                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   Note that [<a href="#ref-FRAGID-BP">FRAGID-BP</a>] provides additional advice to designers of
   fragment identifier rules for media type suffixes and specific media
   types.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  References</span>

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  Normative References</span>

   [<a id="ref-RFC4627">RFC4627</a>]  Crockford, D., "The application/json Media Type for
              JavaScript Object Notation (JSON)", <a href="./rfc4627">RFC 4627</a>, July 2006.

   [<a id="ref-ITU.X690.2008">ITU.X690.2008</a>]
              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.

   [<a id="ref-ITU.X891.2005">ITU.X891.2005</a>]
              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.

   [<a id="ref-WBXML">WBXML</a>]    Open Mobile Alliance, "Binary XML Content Format
              Specification", OMA Wireless Access Protocol WAP-192-
              WBXML-20010725-a, July 2001.

   [<a id="ref-ZIP">ZIP</a>]      PKWARE, Inc., "APPNOTE.TXT - .ZIP File Format
              Specification", PKWARE .ZIP File Format Specification -
              Version 6.3.2, September 2007.

   [<a id="ref-RFC2045">RFC2045</a>]  Freed, N. and N. Borenstein, "Multipurpose Internet Mail
              Extensions (MIME) Part One: Format of Internet Message
              Bodies", <a href="./rfc2045">RFC 2045</a>, November 1996.

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC3023">RFC3023</a>]  Murata, M., St. Laurent, S., and D. Kohn, "XML Media
              Types", <a href="./rfc3023">RFC 3023</a>, January 2001.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Informative References</span>

   [<a id="ref-RFC6838">RFC6838</a>]  Freed, N., Klensin, J., and T. Hansen, "Media Type
              Specifications and Registration Procedures", <a href="https://www.rfc-editor.org/bcp/bcp13">BCP 13</a>,
              <a href="./rfc6838">RFC 6838</a>, January 2013.




<span class="grey">Hansen &amp; Melnikov             Informational                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6839">RFC 6839</a>             Additional Media Type Suffixes         January 2013</span>


   [<a id="ref-FRAGID-BP">FRAGID-BP</a>]
              Tennison, J., "Best Practices for Fragment Identifiers and
              Media Type Definitions", July 2012,
              &lt;<a href="http://www.w3.org/TR/fragid-best-practices/">http://www.w3.org/TR/fragid-best-practices/</a>&gt;.

   [<a id="ref-XML-MEDIATYPES">XML-MEDIATYPES</a>]
              Lilley, C., Makoto, M., Melnikov, A., and H. Thompson,
              "XML Media Types", Work in Progress, November 2012.

Authors' Addresses

   Tony Hansen
   AT&amp;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























Hansen &amp; Melnikov             Informational                    [Page 14]
</pre>