Changeset 2290 for draft-ietf-httpbis

Timestamp:

11/06/13 14:42:10 (8 years ago)

Author:

ylafon@…

Message:

Changes wording to use 'generate' to make distinction between generating clients and proxies (See #485)

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -449 +449 @@
   }
   @bottom-center {
-       content: "Expires December 5, 2013";
+       content: "Expires December 13, 2013";
   }
   @bottom-right {
@@ -492 +492 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-06-11">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
@@ -518 +518 @@
             </tr>
             <tr>
-               <td class="left">Expires: December 5, 2013</td>
+               <td class="left">Expires: December 13, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -527 +527 @@
             <tr>
                <td class="left"></td>
-               <td class="right">June 3, 2013</td>
+               <td class="right">June 11, 2013</td>
             </tr>
          </tbody>
@@ -552 +552 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on December 5, 2013.</p>
+      <p>This Internet-Draft will expire on December 13, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -777 +777 @@
       </p>
       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
-</pre><p id="rfc.section.3.2.p.4">Clients <em class="bcp14">MUST NOT</em> use an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> use a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified date it does have
+</pre><p id="rfc.section.3.2.p.4">Clients <em class="bcp14">MUST NOT</em> generate an entity-tag marked as weak in an If-Range field value and <em class="bcp14">MUST NOT</em> generate a <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a> date in an If-Range field value unless it has no entity-tag for the representation and the Last-Modified date it does have
          for the representation is strong in the sense defined by <a href="p4-conditional.html#lastmod.comparison" title="Comparison">Section 2.2.2</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>.
       </p>
@@ -835 +835 @@
          support multipart responses. However, a server <em class="bcp14">MAY</em> generate a multipart/byteranges payload with only a single body part if multiple ranges were requested and only one range
          was found to be satisfiable or only one range remained after coalescing. A client that cannot process a multipart/byteranges
-         response <em class="bcp14">MUST NOT</em> ask for multiple ranges in a single request.
+         response <em class="bcp14">MUST NOT</em> generate requests asking for multiple ranges in one single request.
       </p>
       <p id="rfc.section.4.1.p.9">When a multipart response payload is generated, the server <em class="bcp14">SHOULD</em> send the parts in the same order that the corresponding byte-range-spec appeared in the received <a href="#header.range" class="smpl">Range</a> header field, excluding those ranges that were deemed unsatisfiable or that were coalesced into other ranges. A client that
@@ -1348 +1348 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/438">http://tools.ietf.org/wg/httpbis/trac/ticket/438</a>&gt;: "media type registration template issues"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/485">http://tools.ietf.org/wg/httpbis/trac/ticket/485</a>&gt;: "MUSTs and other feedback"
          </li>
       </ul>

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

@@ -465 +465 @@
 </artwork></figure>
 <t>
-   Clients &MUST-NOT; use an entity-tag marked as weak in an If-Range
-   field value and &MUST-NOT; use a <x:ref>Last-Modified</x:ref> date in an
+   Clients &MUST-NOT; generate an entity-tag marked as weak in an If-Range
+   field value and &MUST-NOT; generate a <x:ref>Last-Modified</x:ref> date in an
    If-Range field value unless it has no entity-tag for the representation and
    the Last-Modified date it does have for the representation is strong
@@ -584 +584 @@
    ranges were requested and only one range was found to be satisfiable or
    only one range remained after coalescing.
-   A client that cannot process a multipart/byteranges response &MUST-NOT; ask
-   for multiple ranges in a single request.
+   A client that cannot process a multipart/byteranges response &MUST-NOT; 
+   generate requests asking for multiple ranges in one single request.
 </t>
 <t>
@@ -1571 +1571 @@
       "media type registration template issues"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/485"/>:
+      "MUSTs and other feedback"
+    </t>
   </list>
 </t>