Ignore:
Timestamp:
Jul 2, 2012, 8:03:34 PM (7 years ago)
Author:
mnot@…
Message:

Add considerations for new cache directives. See #360.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r1697 r1701  
    452452  }
    453453  @bottom-center {
    454        content: "Expires January 2, 2013";
     454       content: "Expires January 4, 2013";
    455455  }
    456456  @bottom-right {
     
    487487      <link href="p5-range.html" rel="prev">
    488488      <link href="p7-auth.html" rel="next">
    489       <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/">
     489      <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/">
    490490      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    491491      <meta name="dct.creator" content="Fielding, R.">
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2012-07-01">
     496      <meta name="dct.issued" scheme="ISO8601" content="2012-07-03">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <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.">
     
    520520            </tr>
    521521            <tr>
    522                <td class="left">Expires: January 2, 2013</td>
     522               <td class="left">Expires: January 4, 2013</td>
    523523               <td class="right">M. Nottingham, Editor</td>
    524524            </tr>
     
    537537            <tr>
    538538               <td class="left"></td>
    539                <td class="right">July 1, 2012</td>
     539               <td class="right">July 3, 2012</td>
    540540            </tr>
    541541         </tbody>
     
    567567         in progress”.
    568568      </p>
    569       <p>This Internet-Draft will expire on January 2, 2013.</p>
     569      <p>This Internet-Draft will expire on January 4, 2013.</p>
    570570      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    571571      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    14581458         minimally correct even if the cache does not understand the extension(s).
    14591459      </p>
    1460       <p id="rfc.section.3.2.3.p.7">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
    1461       <p id="rfc.section.3.2.3.p.8">A registration <em class="bcp14">MUST</em> include the following fields:
     1460      <p id="rfc.section.3.2.3.p.7">New extension directives ought to consider defining:</p>
     1461      <p id="rfc.section.3.2.3.p.8"> </p>
     1462      <ul>
     1463         <li>What it means for a directive to be specified multiple times,</li>
     1464         <li>When the directive does not take an argument, what it means when an argument is present,</li>
     1465         <li>When the directive requires an argument, what it means when it is missing.</li>
     1466      </ul>
     1467      <p id="rfc.section.3.2.3.p.9">The HTTP Cache Directive Registry defines the name space for the cache directives.</p>
     1468      <p id="rfc.section.3.2.3.p.10">A registration <em class="bcp14">MUST</em> include the following fields:
    14621469      </p>
    14631470      <ul>
     
    14651472         <li>Pointer to specification text</li>
    14661473      </ul>
    1467       <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>).
    1468       </p>
    1469       <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;.
     1474      <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>).
     1475      </p>
     1476      <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;.
    14701477      </p>
    14711478      <div id="rfc.iref.e.2"></div>
Note: See TracChangeset for help on using the changeset viewer.