Changeset 795 for draft-ietf-httpbis/latest

Timestamp:

Mar 22, 2010, 10:51:48 AM (10 years ago)

Author:

julian.reschke@…

Message:

make age calculation a bit less conservative - mention this in "Changes from RFC 2616" (related to #29)

Location:

draft-ietf-httpbis/latest

Files:

• p6-cache.html (modified) (5 diffs)
• p6-cache.xml (modified) (1 diff)

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

@@ -402 +402 @@
       <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="2010-03-17">
+      <meta name="dct.issued" scheme="ISO8601" content="2010-03-22">
       <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, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
@@ -428 +428 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 18, 2010</td>
+               <td class="left">Expires: September 23, 2010</td>
                <td class="right">J. Mogul</td>
             </tr>
@@ -489 +489 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 17, 2010</td>
+               <td class="right">March 22, 2010</td>
             </tr>
          </tbody>
@@ -519 +519 @@
       <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
       </p>
-      <p>This Internet-Draft will expire in September 18, 2010.</p>
+      <p>This Internet-Draft will expire in September 23, 2010.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -1569 +1569 @@
       </p>
       <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
-      <p id="rfc.section.A.2.p.1">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
+      <p id="rfc.section.A.2.p.1">Make the specified age calculation algorithm less conservative. (<a href="#age.calculations" title="Calculating Age">Section&nbsp;2.3.2</a>)
+      </p>
+      <p id="rfc.section.A.2.p.2">Remove requirement to consider Content-Location in successful responses in order to determine the appropriate response to
          use. (<a href="#validation.model" title="Validation Model">Section&nbsp;2.4</a>)
       </p>
-      <p id="rfc.section.A.2.p.2">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
-      </p>
-      <p id="rfc.section.A.2.p.3">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.
+      <p id="rfc.section.A.2.p.3">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
+      </p>
+      <p id="rfc.section.A.2.p.4">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.
          (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>)
       </p>

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

@@ -2032 +2032 @@
 <section anchor="changes.from.rfc.2616" title="Changes from RFC 2616">
 <t>
+  Make the specified age calculation algorithm less conservative.
+  (<xref target="age.calculations"/>)
+</t>
+<t>
   Remove requirement to consider Content-Location in successful responses
   in order to determine the appropriate response to use.