Ignore:
Timestamp:
04/06/13 04:36:01 (10 years ago)
Author:
mnot@…
Message:

Move considerations for new cache control extensions into IANA considerations; addresses #464.

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

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

    r2280 r2283  
    452452  }
    453453  @bottom-center {
    454        content: "Expires December 5, 2013";
     454       content: "Expires December 6, 2013";
    455455  }
    456456  @bottom-right {
    … …  
    492492      <link href="p5-range.html" rel="prev">
    493493      <link href="p7-auth.html" rel="next">
    494       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     494      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.597, 2013/05/27 06:39:42, XSLT vendor: SAXON 9.1.0.8 from Saxonica http://www.saxonica.com/">
    495495      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    496496      <meta name="dct.creator" content="Fielding, R.">
    … …  
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2013-06-03">
     500      <meta name="dct.issued" scheme="ISO8601" content="2013-06-04">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
    … …  
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: December 5, 2013</td>
     526               <td class="left">Expires: December 6, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
    … …  
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">June 3, 2013</td>
     535               <td class="right">June 4, 2013</td>
    536536            </tr>
    537537         </tbody>
    … …  
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on December 5, 2013.</p>
     561      <p>This Internet-Draft will expire on December 6, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    656656               <li><a href="#rfc.section.9.1">9.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry">Cache Directive Registry</a><ul>
    657657                     <li><a href="#rfc.section.9.1.1">9.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registry.procedure">Procedure</a></li>
    658                      <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Registrations</a></li>
     658                     <li><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></li>
     659                     <li><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#cache.directive.registration">Registrations</a></li>
    659660                  </ul>
    660661               </li>
    … …  
    13541355         minimally correct even if the cache does not understand the extension(s).
    13551356      </p>
    1356       <p id="rfc.section.7.2.3.p.9">New extension directives ought to consider defining:</p>
    1357       <p id="rfc.section.7.2.3.p.10"> </p>
    1358       <ul>
    1359          <li>What it means for a directive to be specified multiple times,</li>
    1360          <li>When the directive does not take an argument, what it means when an argument is present,</li>
    1361          <li>When the directive requires an argument, what it means when it is missing,</li>
    1362          <li>Whether the directive is specific to requests, responses, or able to be used in either.</li>
    1363       </ul>
    13641357      <div id="rfc.iref.e.2"></div>
    13651358      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="header.expires" href="#header.expires">Expires</a></h2>
    … …  
    15231516      <p id="rfc.section.9.1.1.p.2">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>).
    15241517      </p>
    1525       <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Registrations</a></h3>
    1526       <p id="rfc.section.9.1.2.p.1">The HTTP Cache Directive Registry shall be populated with the registrations below:</p>
     1518      <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a>&nbsp;<a id="cache.directive.considerations" href="#cache.directive.considerations">Considerations for New Cache Control Directives</a></h3>
     1519      <p id="rfc.section.9.1.2.p.1">New extension directives ought to consider defining:</p>
     1520      <p id="rfc.section.9.1.2.p.2"> </p>
     1521      <ul>
     1522         <li>What it means for a directive to be specified multiple times,</li>
     1523         <li>When the directive does not take an argument, what it means when an argument is present,</li>
     1524         <li>When the directive requires an argument, what it means when it is missing,</li>
     1525         <li>Whether the directive is specific to requests, responses, or able to be used in either.</li>
     1526      </ul>
     1527      <p id="rfc.section.9.1.2.p.3">See also <a href="#cache.control.extensions" title="Cache Control Extensions">Section&nbsp;7.2.3</a>.
     1528      </p>
     1529      <h3 id="rfc.section.9.1.3"><a href="#rfc.section.9.1.3">9.1.3</a>&nbsp;<a id="cache.directive.registration" href="#cache.directive.registration">Registrations</a></h3>
     1530      <p id="rfc.section.9.1.3.p.1">The HTTP Cache Directive Registry shall be populated with the registrations below:</p>
    15271531      <div id="rfc.table.1">
    15281532         <div id="iana.cache.directive.registration.table"></div>
    … …  
    21602164                     </ul>
    21612165                  </li>
    2162                   <li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">9.1.2</a>, <a href="#rfc.xref.RFC5861.2">9.1.2</a>, <a href="#RFC5861"><b>12.2</b></a><ul>
    2163                         <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">9.1.2</a></li>
    2164                         <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">9.1.2</a></li>
     2166                  <li><em>RFC5861</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">9.1.3</a>, <a href="#rfc.xref.RFC5861.2">9.1.3</a>, <a href="#RFC5861"><b>12.2</b></a><ul>
     2167                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.2">9.1.3</a></li>
     2168                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5861.1">9.1.3</a></li>
    21652169                     </ul>
    21662170                  </li>

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

    r2280 r2283  
    14861486   cache does not understand the extension(s).
    14871487</t>
    1488 <t>
    1489    New extension directives ought to consider defining:
    1490 </t>
    1491 <t>
    1492    <list style="symbols">
    1493       <t>What it means for a directive to be specified multiple times,</t>
    1494       <t>When the directive does not take an argument, what it means when an
    1495       argument is present,</t>
    1496       <t>When the directive requires an argument, what it means when it is
    1497       missing,</t>
    1498       <t>Whether the directive is specific to requests, responses, or able
    1499         to be used in either.</t>
    1500    </list>
    1501 </t>
    15021488</section>
    15031489
    … …  
    18101796   Values to be added to this name space require IETF Review (see <xref
    18111797   target="RFC5226" x:fmt="," x:sec="4.1"/>).
     1798</t>
     1799</section>
     1800
     1801<section title="Considerations for New Cache Control Directives" anchor="cache.directive.considerations">
     1802<t>
     1803   New extension directives ought to consider defining:
     1804</t>
     1805<t>
     1806   <list style="symbols">
     1807      <t>What it means for a directive to be specified multiple times,</t>
     1808      <t>When the directive does not take an argument, what it means when an
     1809      argument is present,</t>
     1810      <t>When the directive requires an argument, what it means when it is
     1811      missing,</t>
     1812      <t>Whether the directive is specific to requests, responses, or able
     1813        to be used in either.</t>
     1814   </list>
     1815</t>
     1816<t>
     1817  See also <xref target="cache.control.extensions"/>.
    18121818</t>
    18131819</section>
Note: See TracChangeset for help on using the changeset viewer.