Changeset 196 for draft-ietf-httpbis/latest/p5-range.html

Timestamp:

Feb 4, 2008, 4:57:41 PM (12 years ago)

Author:

fielding@…

Message:

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

File:

• draft-ietf-httpbis/latest/p5-range.html (modified) (7 diffs)

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

@@ -834 +834 @@
       <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References
       </h2>
-      <table summary="Informative References">  
+      <table summary="Informative References">    
          <tr>
             <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
             <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.
+            </td>
+         </tr>
+         <tr>
+            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
+            <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.
             </td>
          </tr>
@@ -861 +866 @@
       <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>
       <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
-         non-overlapping ranges), these are transmitted as a multipart message-body. The media type for this purpose is called "multipart/byteranges".
+         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>.
       </p>
       <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
@@ -868 +873 @@
       <p id="rfc.section.A.p.3"> </p>
       <dl>
-         <dt>Media Type name:</dt>
+         <dt>Type name:</dt>
          <dd>multipart</dd>
-         <dt>Media subtype name:</dt>
+         <dt>Subtype name:</dt>
          <dd>byteranges</dd>
          <dt>Required parameters:</dt>
@@ -880 +885 @@
          <dt>Security considerations:</dt>
          <dd>none</dd>
+         <dt>Interoperability considerations:</dt>
+         <dd>none</dd>
+         <dt>Published specification:</dt>
+         <dd>This specification (see <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>).
+         </dd>
+         <dt>Applications that use this media type:</dt>
+         <dt>Additional information:</dt>
+         <dd> 
+            <dl>
+               <dt>Magic number(s):</dt>
+               <dd>none</dd>
+               <dt>File extension(s):</dt>
+               <dd>none</dd>
+               <dt>Macintosh file type code(s):</dt>
+               <dd>none</dd>
+            </dl> 
+         </dd>
+         <dt>Person and email address to contact for further information:</dt>
+         <dd>See Authors Section.</dd>
+         <dt>Intended usage:</dt>
+         <dd>COMMON</dd>
+         <dt>Restrictions on usage:</dt>
+         <dd>none</dd>
+         <dt>Author/Change controller:</dt>
+         <dd>IESG</dd>
       </dl>
       <div id="rfc.figure.u.15"></div>
@@ -901 +931 @@
       <ol>
          <li>Additional CRLFs may precede the first boundary string in the entity.</li>
-         <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.
+         <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.
          </li>
          <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.
@@ -945 +975 @@
       <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p5-range-01
       </h2>
+      <p id="rfc.section.C.3.p.1">Updated media type registrations to use RFC4288 template.</p>
       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
       <p>Copyright © The IETF Trust (2008).</p>
@@ -1058 +1089 @@
             <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
                   <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>
-                  <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>
+                  <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>
                   <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>
                   <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>
+                  <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>
                </ul>
             </li>