Changeset 332 for draft-ietf-httpbis

Timestamp:

02/11/08 16:32:36 (14 years ago)

Author:

julian.reschke@…

Message:

Resolve #133: multipart/byteranges can consist of a single part (closes #133).

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -473 +473 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">November 1, 2008</td>
+            <td class="header right">November 2, 2008</td>
          </tr>
       </table>
@@ -971 +971 @@
          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>, <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>
-      <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
+      <p id="rfc.section.A.p.2">The multipart/byteranges media type includes one or more parts, each with its own Content-Type and Content-Range fields. The
          required boundary parameter specifies the boundary string used to separate each body-part.
       </p>
@@ -1059 +1059 @@
       <p id="rfc.section.B.2.p.1">Clarify that it is not ok to use a weak cache validator in a 206 response. (<a href="#status.206" id="rfc.xref.status.206.2" title="206 Partial Content">Section&nbsp;4.1</a>)
       </p>
+      <p id="rfc.section.B.2.p.2">Clarify that multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
+      </p>
       <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
       <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
@@ -1095 +1097 @@
       <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p5-range-03</a></h2>
       <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p5-range-04</a></h2>
+      <p id="rfc.section.C.6.p.1">Closed issues: </p>
+      <ul>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/133">http://tools.ietf.org/wg/httpbis/trac/ticket/133</a>&gt;: "multipart/byteranges minimum number of parts"
+         </li>
+      </ul>
       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
       <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the

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

@@ -1157 +1157 @@
    "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
 </t><t>
-   The multipart/byteranges media type includes two or more parts, each
+   The multipart/byteranges media type includes one or more parts, each
    with its own Content-Type and Content-Range fields. The required
    boundary parameter specifies the boundary string used to separate
@@ -1287 +1287 @@
   (<xref target="status.206"/>)
 </t>
+<t>
+  Clarify that multipart/byteranges can consist of a single part.
+  (<xref target="internet.media.type.multipart.byteranges"/>)
+</t>
+
 </section>
 
@@ -1359 +1364 @@
 <section title="Since draft-ietf-httpbis-p5-range-04" anchor="changes.since.04">
 <t>
+  Closed issues:
+  <list style="symbols"> 
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/133"/>:
+      "multipart/byteranges minimum number of parts"
+    </t>
+  </list>
 </t>
 </section>