Changeset 2250 for draft-ietf-httpbis/latest

Timestamp:

17/05/13 01:45:39 (10 years ago)

Author:

mnot@…

Message:

Fix misused SHOULDs in p6 for #472

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (9 diffs)
• p6-cache.xml (modified) (3 diffs)

draft-ietf-httpbis/latest/p6-cache.html

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires November 9, 2013"; 
+       content: "Expires November 18, 2013"; 
   } 
   @bottom-right {
@@ -492 +492 @@
       <link href="p5-range.html" rel="prev">
       <link href="p7-auth.html" rel="next">
-      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.594, 2013/04/30 16:11:28, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
       <link rel="schema.dct" href="http://purl.org/dc/terms/">
       <meta name="dct.creator" content="Fielding, R.">
@@ -498 +498 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-05-08">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-05-17">
       <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 requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -524 +524 @@
             </tr>
             <tr>
-               <td class="left">Expires: November 9, 2013</td>
+               <td class="left">Expires: November 18, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -533 +533 @@
             <tr>
                <td class="left"></td>
-               <td class="right">May 8, 2013</td>
+               <td class="right">May 17, 2013</td>
             </tr>
          </tbody>
@@ -559 +559 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on November 9, 2013.</p>
+      <p>This Internet-Draft will expire on November 18, 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>
@@ -985 +985 @@
   corrected_age_value = age_value + response_delay;  
 </pre><div id="rfc.figure.u.4"></div>
-      <p>These <em class="bcp14">SHOULD</em> be combined as
-      </p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
+      <p>These are combined as</p><pre class="text">  corrected_initial_age = max(apparent_age, corrected_age_value);
 </pre><p id="rfc.section.4.1.3.p.11">unless the cache is confident in the value of the <a href="#header.age" class="smpl">Age</a> header field (e.g., because there are no HTTP/1.0 hops in the <a href="p1-messaging.html#header.via" class="smpl">Via</a> header field), in which case the corrected_age_value <em class="bcp14">MAY</em> be used as the corrected_initial_age.
       </p>
@@ -1008 +1007 @@
       </p>
       <div id="rfc.iref.f.3"></div>
-      <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache shouldn't attempt to validate a response simply because
+      <p id="rfc.section.4.1.4.p.5">Note that if a cache receives a <dfn>first-hand</dfn> response (one where the freshness model is not in use; i.e., its age is 0, whether it is an entire response, or a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response) that it would normally forward to the requesting client, and the received response is no longer fresh, the cache <em class="bcp14">MAY</em> forward it to the requesting client without adding a new <a href="#header.warning" class="smpl">Warning</a> (but without removing any existing Warning header fields). A cache ought not attempt to validate a response simply because
          that response became stale in transit.
       </p>
@@ -1023 +1022 @@
       </p>
       <p id="rfc.section.4.2.p.4">Another is the <a href="p4-conditional.html#header.if-none-match" class="smpl">If-None-Match</a> header field, whose value is that of the <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> header field(s) from relevant responses stored for the primary cache key, if present. However, if any of the stored responses
-         contains only partial content, the cache shouldn't include its entity-tag in the If-None-Match header field unless the request
+         contains only partial content, the cache ought not include its entity-tag in the If-None-Match header field unless the request
          is for a range that would be fully satisfied by that stored response.
       </p>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -708 +708 @@
 </figure>
 <figure>
-<preamble>These &SHOULD; be combined as</preamble>
+<preamble>These are combined as</preamble>
 <artwork type="code">
   corrected_initial_age = max(apparent_age, corrected_age_value);
@@ -762 +762 @@
    response is no longer fresh, the cache &MAY; forward it to the requesting
    client without adding a new <x:ref>Warning</x:ref> (but without removing
-   any existing Warning header fields). A cache shouldn't attempt to validate
+   any existing Warning header fields). A cache ought not attempt to validate
    a response simply because that response became stale in transit.
 </t>
@@ -796 +796 @@
    relevant responses stored for the primary cache key, if present. However,
    if any of the stored responses contains only partial content, the cache
-   shouldn't include its entity-tag in the If-None-Match header field unless
+   ought not include its entity-tag in the If-None-Match header field unless
    the request is for a range that would be fully satisfied by that stored
    response.