Ignore:
Timestamp:
Jul 9, 2012, 11:04:50 AM (7 years ago)
Author:
julian.reschke@…
Message:

Minor fine-tuning of multipart/byteranges IANA registration template.

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.html

    r1748 r1749  
    11911191         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>, <a href="http://tools.ietf.org/html/rfc2046#section-5.1">Section 5.1</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>.
    11921192      </p>
    1193       <div class="note" id="rfc.section.A.p.2">
    1194          <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    1195          </p>
    1196       </div>
    1197       <p id="rfc.section.A.p.3">The multipart/byteranges media type includes one or more parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body-part.
    1198       </p>
    1199       <p id="rfc.section.A.p.4"> </p>
     1193      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> and <a href="#header.content-range" class="smpl">Content-Range</a> fields. The required boundary parameter specifies the boundary string used to separate each body-part.
     1194      </p>
     1195      <p id="rfc.section.A.p.3"> </p>
    12001196      <dl>
    12011197         <dt>Type name:</dt>
     
    12171213         </dd>
    12181214         <dt>Applications that use this media type:</dt>
     1215         <dd>HTTP components supporting multiple ranges in a single request.</dd>
    12191216         <dt>Additional information:</dt>
    12201217         <dd>
     
    12371234         <dd>IESG</dd>
    12381235      </dl>
     1236      <div class="note" id="rfc.section.A.p.4">
     1237         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1238         </p>
     1239      </div>
    12391240      <div id="rfc.figure.u.24"></div>
    12401241      <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
     
    12551256  --THIS_STRING_SEPARATES--
    12561257</pre><div id="rfc.figure.u.25"></div>
    1257       <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
     1258      <p>Another example, using the "exampleunit" range unit:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
    12581259  Date: Tue, 14 Nov 1995 06:25:24 GMT
    12591260  Last-Modified: Tue, 14 July 04:58:08 GMT
  • draft-ietf-httpbis/latest/p5-range.xml

    r1748 r1749  
    12641264   "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
    12651265</t>
    1266 <x:note>
    1267   <t>
    1268     &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    1269   </t>
    1270 </x:note>
    12711266<t>
    12721267   The multipart/byteranges media type includes one or more parts, each
     
    13021297    </t>
    13031298    <t hangText="Applications that use this media type:">
     1299      HTTP components supporting multiple ranges in a single request.
    13041300    </t>
    13051301    <t hangText="Additional information:">
     
    13241320  </list>
    13251321</t>
     1322<x:note>
     1323  <t>
     1324    &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1325  </t>
     1326</x:note>
    13261327<figure><preamble>
    13271328   For example:
     
    13451346</artwork></figure>
    13461347<figure><preamble>
    1347    Other example:
     1348   Another example, using the "exampleunit" range unit:
    13481349</preamble>
    13491350<artwork type="example">
     
    13671368</figure>
    13681369<t>
    1369       Notes:
     1370  Notes:
    13701371  <list style="numbers">
    13711372      <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>
Note: See TracChangeset for help on using the changeset viewer.