Changeset 1749

Timestamp:

09/07/12 18:04:50 (8 years ago)

Author:

julian.reschke@…

Message:

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

Location:

draft-ietf-httpbis/latest

Files:

• p5-range.html (modified) (4 diffs)
• p5-range.xml (modified) (5 diffs)

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

@@ -1191 +1191 @@
          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>.
       </p>
-      <div class="note" id="rfc.section.A.p.2"> 
-         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
-         </p> 
-      </div>
-      <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.
-      </p>
-      <p id="rfc.section.A.p.4"> </p>
+      <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.
+      </p>
+      <p id="rfc.section.A.p.3"> </p>
       <dl>
          <dt>Type name:</dt>
@@ -1217 +1213 @@
          </dd>
          <dt>Applications that use this media type:</dt>
+         <dd>HTTP components supporting multiple ranges in a single request.</dd>
          <dt>Additional information:</dt>
          <dd> 
@@ -1237 +1234 @@
          <dd>IESG</dd>
       </dl>
+      <div class="note" id="rfc.section.A.p.4"> 
+         <p> <b>Note:</b> Despite the name "multipart/byteranges" is not limited to the byte ranges only.
+         </p> 
+      </div>
       <div id="rfc.figure.u.24"></div>
       <p>For example:</p><pre class="text">  HTTP/1.1 206 Partial Content
@@ -1255 +1256 @@
   --THIS_STRING_SEPARATES--
 </pre><div id="rfc.figure.u.25"></div>
-      <p>Other example:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
+      <p>Another example, using the "exampleunit" range unit:</p>  <pre class="text">  HTTP/1.1 206 Partial Content
   Date: Tue, 14 Nov 1995 06:25:24 GMT
   Last-Modified: Tue, 14 July 04:58:08 GMT

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

@@ -1264 +1264 @@
    "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
 </t>
-<x:note>
-  <t>
-    &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
-  </t>
-</x:note>
 <t>
    The multipart/byteranges media type includes one or more parts, each
@@ -1302 +1297 @@
     </t>
     <t hangText="Applications that use this media type:">
+      HTTP components supporting multiple ranges in a single request.
     </t>
     <t hangText="Additional information:">
@@ -1324 +1320 @@
   </list>
 </t>
+<x:note>
+  <t>
+    &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
+  </t>
+</x:note>
 <figure><preamble>
    For example:
@@ -1345 +1346 @@
 </artwork></figure>
 <figure><preamble>
-   Other example:
+   Another example, using the "exampleunit" range unit:
 </preamble>
 <artwork type="example">
@@ -1367 +1368 @@
 </figure>
 <t>
-      Notes:
+  Notes:
   <list style="numbers">
       <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>