Changeset 969 for draft-ietf-httpbis/latest/p6-cache.xml

Timestamp:

Jul 30, 2010, 6:06:01 PM (9 years ago)

Author:

fielding@…

Message:

Replace lowercase should with less normative words, where possible.

File:

• draft-ietf-httpbis/latest/p6-cache.xml (modified) (5 diffs)

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

@@ -280 +280 @@
    <list>
       <t>The time at which the origin server intends that a representation
-      should no longer be returned by a cache without further validation.</t>
+      no longer be returned by a cache without further validation.</t>
    </list>
 </t>
@@ -566 +566 @@
 <t>
    If an origin server wishes to force a cache to validate every request, it
-   can assign an explicit expiration time in the past. This means that the
-   response is always stale, so that caches should validate it before using it
-   for subsequent requests. <cref anchor="TODO-response-stale">This wording
-   might cause confusion, because the response might still be served
-   stale.</cref>
+   can assign an explicit expiration time in the past to indicate that the
+   response is already stale.  Compliant caches will validate the cached response
+   before reusing it for subsequent requests.
 </t>
 <t>
@@ -1741 +1739 @@
 </t>
 <t>
-   The HTTP Cache Directive Registry should be created at <eref
+   The HTTP Cache Directive Registry shall be created at <eref
    target="http://www.iana.org/assignments/http-cache-directives"/> and be
    populated with the registrations below:
@@ -1817 +1815 @@
   The Message Header Field Registry located at <eref  
   target="http://www.iana.org/assignments/message-headers/message-header-index.html" />
-  should be updated with the permanent registrations below (see <xref target="RFC3864" />):
+  shall be updated with the permanent registrations below (see <xref target="RFC3864" />):
 </t>
 <?BEGININC p6-cache.iana-headers ?>
@@ -1881 +1879 @@
    on the cache can reveal information long after a user believes that the
    information has been removed from the network. Therefore, cache contents
-   should be protected as sensitive information.
+   need to be protected as sensitive information.
 </t>
 </section>