Changeset 196


Ignore:
Timestamp:
05/02/08 00:57:41 (15 years ago)
Author:
fielding@…
Message:

Update multipart/byteranges media type template to RFC4288
and note that RFC2046 is normative.

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p5-range.html

    r189 r196  
    834834      <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
    835835      </h2>
    836       <table summary="Informative References"> 
     836      <table summary="Informative References">   
    837837         <tr>
    838838            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    839839            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     840            </td>
     841         </tr>
     842         <tr>
     843            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
     844            <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    840845            </td>
    841846         </tr>
    … …  
    861866      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="internet.media.type.multipart.byteranges" href="#internet.media.type.multipart.byteranges">Internet Media Type multipart/byteranges</a></h1>
    862867      <p id="rfc.section.A.p.1">When an HTTP 206 (Partial Content) response message includes the content of multiple ranges (a response to a request for multiple
    863          non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
     868         non-overlapping ranges), these are transmitted as a multipart message-body <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>. The media type for this purpose is called "multipart/byteranges". The following is to be registered with IANA <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>.
    864869      </p>
    865870      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes two or more parts, each with its own Content-Type and Content-Range fields. The
    … …  
    868873      <p id="rfc.section.A.p.3"> </p>
    869874      <dl>
    870          <dt>Media Type name:</dt>
     875         <dt>Type name:</dt>
    871876         <dd>multipart</dd>
    872          <dt>Media subtype name:</dt>
     877         <dt>Subtype name:</dt>
    873878         <dd>byteranges</dd>
    874879         <dt>Required parameters:</dt>
    … …  
    880885         <dt>Security considerations:</dt>
    881886         <dd>none</dd>
     887         <dt>Interoperability considerations:</dt>
     888         <dd>none</dd>
     889         <dt>Published specification:</dt>
     890         <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
     891         </dd>
     892         <dt>Applications that use this media type:</dt>
     893         <dt>Additional information:</dt>
     894         <dd>
     895            <dl>
     896               <dt>Magic number(s):</dt>
     897               <dd>none</dd>
     898               <dt>File extension(s):</dt>
     899               <dd>none</dd>
     900               <dt>Macintosh file type code(s):</dt>
     901               <dd>none</dd>
     902            </dl>
     903         </dd>
     904         <dt>Person and email address to contact for further information:</dt>
     905         <dd>See Authors Section.</dd>
     906         <dt>Intended usage:</dt>
     907         <dd>COMMON</dd>
     908         <dt>Restrictions on usage:</dt>
     909         <dd>none</dd>
     910         <dt>Author/Change controller:</dt>
     911         <dd>IESG</dd>
    882912      </dl>
    883913      <div id="rfc.figure.u.15"></div>
    … …  
    901931      <ol>
    902932         <li>Additional CRLFs may precede the first boundary string in the entity.</li>
    903          <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
     933         <li>Although <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> permits the boundary string to be quoted, some existing implementations handle a quoted boundary string incorrectly.
    904934         </li>
    905935         <li>A number of browsers and servers were coded to an early draft of the byteranges specification to use a media type of multipart/x-byteranges<span id="rfc.iref.m.3"></span><span id="rfc.iref.m.4"></span>, which is almost, but not quite compatible with the version documented in HTTP/1.1.
    … …  
    945975      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
    946976      </h2>
     977      <p id="rfc.section.C.3.p.1">Updated media type registrations to use RFC4288 template.</p>
    947978      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    948979      <p>Copyright © The IETF Trust (2008).</p>
    … …  
    10581089            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    10591090                  <li class="indline1">Range header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.range.1">2</a>, <a class="iref" href="#rfc.xref.header.range.2">3.1</a>, <a class="iref" href="#rfc.xref.header.range.3">3.2</a>, <a class="iref" href="#rfc.iref.r.1"><b>5.4</b></a></li>
    1060                   <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a></li>
     1091                  <li class="indline1"><em>RFC2046</em>&nbsp;&nbsp;<a class="iref" href="#RFC2046"><b>9.1</b></a>, <a class="iref" href="#rfc.xref.RFC2046.1">A</a>, <a class="iref" href="#rfc.xref.RFC2046.2">A</a></li>
    10611092                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>9.1</b></a></li>
    10621093                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
     1094                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#RFC4288"><b>9.2</b></a>, <a class="iref" href="#rfc.xref.RFC4288.1">A</a></li>
    10631095               </ul>
    10641096            </li>

  • draft-ietf-httpbis/latest/p5-range.xml

    r182 r196  
    10101010</reference>
    10111011
     1012<reference anchor="RFC4288">
     1013  <front>
     1014    <title>Media Type Specifications and Registration Procedures</title>
     1015    <author initials="N." surname="Freed" fullname="N. Freed">
     1016      <organization>Sun Microsystems</organization>
     1017      <address>
     1018        <email>ned.freed@mrochek.com</email>
     1019      </address>
     1020    </author>
     1021    <author initials="J." surname="Klensin" fullname="J. Klensin">
     1022      <organization/>
     1023      <address>
     1024        <email>klensin+ietf@jck.com</email>
     1025      </address>
     1026    </author>
     1027    <date year="2005" month="December"/>
     1028  </front>
     1029  <seriesInfo name="BCP" value="13"/>
     1030  <seriesInfo name="RFC" value="4288"/>
     1031</reference>
     1032
    10121033</references>
    10131034
    … …  
    10191040   content of multiple ranges (a response to a request for multiple
    10201041   non-overlapping ranges), these are transmitted as a multipart
    1021    message-body. The media type for this purpose is called
    1022    "multipart/byteranges".
     1042   message-body <xref target="RFC2046"/>. The media type for this purpose is called
     1043   "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
    10231044</t><t>
    10241045   The multipart/byteranges media type includes two or more parts, each
    … …  
    10291050<t>
    10301051  <list style="hanging" x:indent="12em">
    1031     <t hangText="Media Type name:">
     1052    <t hangText="Type name:">
    10321053      multipart
    10331054    </t>
    1034     <t hangText="Media subtype name:">
     1055    <t hangText="Subtype name:">
    10351056      byteranges
    10361057    </t>
    … …  
    10461067    <t hangText="Security considerations:">
    10471068      none
     1069    </t>
     1070    <t hangText="Interoperability considerations:">
     1071      none
     1072    </t>
     1073    <t hangText="Published specification:">
     1074      This specification (see <xref target="internet.media.type.multipart.byteranges"/>).
     1075    </t>
     1076    <t hangText="Applications that use this media type:">
     1077    </t>
     1078    <t hangText="Additional information:">
     1079      <list style="hanging">
     1080        <t hangText="Magic number(s):">none</t>
     1081        <t hangText="File extension(s):">none</t>
     1082        <t hangText="Macintosh file type code(s):">none</t>
     1083      </list>
     1084    </t>
     1085    <t hangText="Person and email address to contact for further information:">
     1086      See Authors Section.
     1087    </t>
     1088                <t hangText="Intended usage:">
     1089                  COMMON
     1090    </t>
     1091                <t hangText="Restrictions on usage:">
     1092                  none
     1093    </t>
     1094    <t hangText="Author/Change controller:">
     1095      IESG
    10481096    </t>
    10491097  </list>
    … …  
    11601208<section title="Since draft-ietf-httpbis-p5-range-01">
    11611209<t>
     1210   Updated media type registrations to use RFC4288 template.
    11621211</t>
    11631212</section>
Note: See TracChangeset for help on using the changeset viewer.