Changeset 2004

Timestamp:

28/11/12 08:05:31 (9 years ago)

Author:

fielding@…

Message:

update description of large-scale caches; addresses #389

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (5 diffs)
• p1-messaging.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires May 31, 2013"; 
+       content: "Expires June 1, 2013"; 
   } 
   @bottom-right {
@@ -491 +491 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2012-11-27">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-11-28">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -520 +520 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">November 27, 2012</td>
+               <td class="right">November 28, 2012</td>
             </tr>
             <tr>
-               <td class="left">Expires: May 31, 2013</td>
+               <td class="left">Expires: June 1, 2013</td>
                <td class="right"></td>
             </tr>
@@ -551 +551 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on May 31, 2013.</p>
+      <p>This Internet-Draft will expire on June 1, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -928 +928 @@
          can be used for a particular request. HTTP requirements for cache behavior and cacheable responses are defined in <a href="p6-cache.html#caching.overview" title="Overview of Cache Operation">Section 2</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>.
       </p>
-      <p id="rfc.section.2.4.p.5">There are a wide variety of architectures and configurations of caches and proxies deployed across the World Wide Web and
-         inside large organizations. These systems include national hierarchies of proxy caches to save transoceanic bandwidth, systems
-         that broadcast or multicast cache entries, organizations that distribute subsets of cached data via optical media, and so
-         on.
+      <p id="rfc.section.2.4.p.5">There are a wide variety of architectures and configurations of caches deployed across the World Wide Web and inside large
+         organizations. These include national hierarchies of proxy caches to save transoceanic bandwidth, collaborative systems that
+         broadcast or multicast cache entries, archives of pre-fetched cache entries for use in off-line or high-latency environments,
+         and so on.
       </p>
       <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="conformance" href="#conformance">Conformance and Error Handling</a></h2>

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -591 +591 @@
 <t>
    There are a wide variety of architectures and configurations
-   of caches and proxies deployed across the World Wide Web and
-   inside large organizations. These systems include national hierarchies
-   of proxy caches to save transoceanic bandwidth, systems that
-   broadcast or multicast cache entries, organizations that distribute
-   subsets of cached data via optical media, and so on.
+   of caches deployed across the World Wide Web and
+   inside large organizations. These include national hierarchies
+   of proxy caches to save transoceanic bandwidth, collaborative systems that
+   broadcast or multicast cache entries, archives of pre-fetched cache
+   entries for use in off-line or high-latency environments, and so on.
 </t>
 </section>