Changeset 1701

Timestamp:

03/07/12 03:03:34 (10 years ago)

Author:

mnot@…

Message:

Add considerations for new cache directives. See #360.

Location:

draft-ietf-httpbis/latest

Files:

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

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

@@ -452 +452 @@
   } 
   @bottom-center {
-       content: "Expires January 2, 2013"; 
+       content: "Expires January 4, 2013"; 
   } 
   @bottom-right {
@@ -487 +487 @@
       <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.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
+      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, 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.">
@@ -494 +494 @@
       <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="2012-07-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2012-07-03">
       <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. HTTP has been in use by the World Wide Web global information initiative since 1990. 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.">
@@ -520 +520 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 2, 2013</td>
+               <td class="left">Expires: January 4, 2013</td>
                <td class="right">M. Nottingham, Editor</td>
             </tr>
@@ -537 +537 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 1, 2012</td>
+               <td class="right">July 3, 2012</td>
             </tr>
          </tbody>
@@ -567 +567 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 2, 2013.</p>
+      <p>This Internet-Draft will expire on January 4, 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>
@@ -1458 +1458 @@
          minimally correct even if the cache does not understand the extension(s).
       </p>
-      <p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
-      <p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields: 
+      <p id="rfc.section.3.2.3.p.7">New extension directives ought to consider defining:</p>
+      <p id="rfc.section.3.2.3.p.8"> </p>
+      <ul>
+         <li>What it means for a directive to be specified multiple times,</li>
+         <li>When the directive does not take an argument, what it means when an argument is present,</li>
+         <li>When the directive requires an argument, what it means when it is missing.</li>
+      </ul>
+      <p id="rfc.section.3.2.3.p.9">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
+      <p id="rfc.section.3.2.3.p.10">A registration <em class="bcp14">MUST</em> include the following fields: 
       </p>
       <ul>
@@ -1465 +1472 @@
          <li>Pointer to specification text</li>
       </ul>
-      <p id="rfc.section.3.2.3.p.9">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
-      </p>
-      <p id="rfc.section.3.2.3.p.10">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
+      <p id="rfc.section.3.2.3.p.11">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
+      </p>
+      <p id="rfc.section.3.2.3.p.12">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>&gt;.
       </p>
       <div id="rfc.iref.e.2"></div>

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

@@ -1631 +1631 @@
 </t>
 <t>
+   New extension directives ought to consider defining:
+</t>
+<t>
+   <list style="symbols">
+      <t>What it means for a directive to be specified multiple times,</t>
+      <t>When the directive does not take an argument, what it means when an
+      argument is present,</t>
+      <t>When the directive requires an argument, what it means when it is
+      missing.</t>
+   </list>
+</t>
+<t>
    The HTTP Cache Directive Registry defines the name space for the cache
    directives.