Changeset 2244 for draft-ietf-httpbis/latest
- Timestamp:
- 07/05/13 16:05:23 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.html
r2243 r2244 659 659 </ul> 660 660 </li> 661 <li><a href="#rfc.section.9.2">9.2</a> <a href="#warn.code.registration">Warn Code Registry</a></li> 661 <li><a href="#rfc.section.9.2">9.2</a> <a href="#warn.code.registry">Warn Code Registry</a><ul> 662 <li><a href="#rfc.section.9.2.1">9.2.1</a> <a href="#warn.code.registry.procedure">Procedure</a></li> 663 <li><a href="#rfc.section.9.2.2">9.2.2</a> <a href="#warn.code.registration">Registrations</a></li> 664 </ul> 665 </li> 662 666 <li><a href="#rfc.section.9.3">9.3</a> <a href="#header.field.registration">Header Field Registration</a></li> 663 667 </ul> … … 1496 1500 </p> 1497 1501 <h3 id="rfc.section.7.5.8"><a href="#rfc.section.7.5.8">7.5.8</a> <a id="warn.code.extensions" href="#warn.code.extensions">Warn Code Extensions</a></h3> 1498 <p id="rfc.section.7.5.8.p.1">The HTTP Warn Code Registry defines the name space for warn codes.</p> 1499 <p id="rfc.section.7.5.8.p.2">A registration <em class="bcp14">MUST</em> include the following fields: 1502 <p id="rfc.section.7.5.8.p.1">Extension warn codes can be defined; see <a href="#warn.code.registry.procedure" title="Procedure">Section 9.2.1</a> for details. 1503 </p> 1504 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="history.lists" href="#history.lists">History Lists</a></h1> 1505 <p id="rfc.section.8.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation 1506 retrieved earlier in a session. 1507 </p> 1508 <p id="rfc.section.8.p.2">The freshness model (<a href="#expiration.model" title="Freshness">Section 4.1</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if 1509 it has expired. 1510 </p> 1511 <p id="rfc.section.8.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives 1512 (e.g., Cache-Control: no-store). 1513 </p> 1514 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1> 1515 <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a> <a id="cache.directive.registry" href="#cache.directive.registry">Cache Directive Registry</a></h2> 1516 <p id="rfc.section.9.1.p.1">The HTTP Cache Directive Registry defines the name space for the cache directives. It will be created and maintained at <<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>>. 1517 </p> 1518 <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a> <a id="cache.directive.registry.procedure" href="#cache.directive.registry.procedure">Procedure</a></h3> 1519 <p id="rfc.section.9.1.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields: 1520 </p> 1521 <ul> 1522 <li>Cache Directive Name</li> 1523 <li>Pointer to specification text</li> 1524 </ul> 1525 <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>). 1526 </p> 1527 <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a> <a id="cache.directive.registration" href="#cache.directive.registration">Registrations</a></h3> 1528 <p id="rfc.section.9.1.2.p.1">The HTTP Cache Directive Registry shall be populated with the registrations below:</p> 1529 <div id="rfc.table.1"> 1530 <div id="iana.cache.directive.registration.table"></div> 1531 <table class="tt full left" cellpadding="3" cellspacing="0"> 1532 <thead> 1533 <tr> 1534 <th>Cache Directive</th> 1535 <th>Reference</th> 1536 </tr> 1537 </thead> 1538 <tbody> 1539 <tr> 1540 <td class="left">max-age</td> 1541 <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section 7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.8</a> 1542 </td> 1543 </tr> 1544 <tr> 1545 <td class="left">max-stale</td> 1546 <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section 7.2.1.2</a> 1547 </td> 1548 </tr> 1549 <tr> 1550 <td class="left">min-fresh</td> 1551 <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section 7.2.1.3</a> 1552 </td> 1553 </tr> 1554 <tr> 1555 <td class="left">must-revalidate</td> 1556 <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section 7.2.2.1</a> 1557 </td> 1558 </tr> 1559 <tr> 1560 <td class="left">no-cache</td> 1561 <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section 7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.2</a> 1562 </td> 1563 </tr> 1564 <tr> 1565 <td class="left">no-store</td> 1566 <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section 7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section 7.2.2.3</a> 1567 </td> 1568 </tr> 1569 <tr> 1570 <td class="left">no-transform</td> 1571 <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section 7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section 7.2.2.4</a> 1572 </td> 1573 </tr> 1574 <tr> 1575 <td class="left">only-if-cached</td> 1576 <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section 7.2.1.7</a> 1577 </td> 1578 </tr> 1579 <tr> 1580 <td class="left">private</td> 1581 <td class="left"> <a href="#cache-response-directive.private" title="private">Section 7.2.2.6</a> 1582 </td> 1583 </tr> 1584 <tr> 1585 <td class="left">proxy-revalidate</td> 1586 <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section 7.2.2.7</a> 1587 </td> 1588 </tr> 1589 <tr> 1590 <td class="left">public</td> 1591 <td class="left"> <a href="#cache-response-directive.public" title="public">Section 7.2.2.5</a> 1592 </td> 1593 </tr> 1594 <tr> 1595 <td class="left">s-maxage</td> 1596 <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section 7.2.2.9</a> 1597 </td> 1598 </tr> 1599 <tr> 1600 <td class="left">stale-if-error</td> 1601 <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a> 1602 </td> 1603 </tr> 1604 <tr> 1605 <td class="left">stale-while-revalidate</td> 1606 <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a> 1607 </td> 1608 </tr> 1609 </tbody> 1610 </table> 1611 </div> 1612 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="warn.code.registry" href="#warn.code.registry">Warn Code Registry</a></h2> 1613 <p id="rfc.section.9.2.p.1">The HTTP Warn Code Registry defines the value space for warn codes. It will be created and maintained at <<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>>. 1614 </p> 1615 <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a> <a id="warn.code.registry.procedure" href="#warn.code.registry.procedure">Procedure</a></h3> 1616 <p id="rfc.section.9.2.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields: 1500 1617 </p> 1501 1618 <ul> … … 1504 1621 <li>Pointer to specification text</li> 1505 1622 </ul> 1506 <p id="rfc.section.7.5.8.p.3">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>). 1507 </p> 1508 <p id="rfc.section.7.5.8.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>>. 1509 </p> 1510 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="history.lists" href="#history.lists">History Lists</a></h1> 1511 <p id="rfc.section.8.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay a representation 1512 retrieved earlier in a session. 1513 </p> 1514 <p id="rfc.section.8.p.2">The freshness model (<a href="#expiration.model" title="Freshness">Section 4.1</a>) does not necessarily apply to history mechanisms. I.e., a history mechanism can display a previous representation even if 1515 it has expired. 1516 </p> 1517 <p id="rfc.section.8.p.3">This does not prohibit the history mechanism from telling the user that a view might be stale, or from honoring cache directives 1518 (e.g., Cache-Control: no-store). 1519 </p> 1520 <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a> <a id="iana.considerations" href="#iana.considerations">IANA Considerations</a></h1> 1521 <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a> <a id="cache.directive.registry" href="#cache.directive.registry">Cache Directive Registry</a></h2> 1522 <p id="rfc.section.9.1.p.1">The HTTP Cache Directive Registry defines the name space for the cache directives. It will be created and maintained at <<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>>. 1523 </p> 1524 <h3 id="rfc.section.9.1.1"><a href="#rfc.section.9.1.1">9.1.1</a> <a id="cache.directive.registry.procedure" href="#cache.directive.registry.procedure">Procedure</a></h3> 1525 <p id="rfc.section.9.1.1.p.1">The HTTP Cache Directive Registry defines the name space for the cache directives.</p> 1526 <p id="rfc.section.9.1.1.p.2">A registration <em class="bcp14">MUST</em> include the following fields: 1527 </p> 1528 <ul> 1529 <li>Cache Directive Name</li> 1530 <li>Pointer to specification text</li> 1531 </ul> 1532 <p id="rfc.section.9.1.1.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><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>). 1533 </p> 1534 <h3 id="rfc.section.9.1.2"><a href="#rfc.section.9.1.2">9.1.2</a> <a id="cache.directive.registration" href="#cache.directive.registration">Registrations</a></h3> 1535 <p id="rfc.section.9.1.2.p.1">The HTTP Cache Directive shall be populated with the registrations below:</p> 1536 <div id="rfc.table.1"> 1537 <div id="iana.cache.directive.registration.table"></div> 1538 <table class="tt full left" cellpadding="3" cellspacing="0"> 1539 <thead> 1540 <tr> 1541 <th>Cache Directive</th> 1542 <th>Reference</th> 1543 </tr> 1544 </thead> 1545 <tbody> 1546 <tr> 1547 <td class="left">max-age</td> 1548 <td class="left"> <a href="#cache-request-directive.max-age" title="max-age">Section 7.2.1.1</a>, <a href="#cache-response-directive.max-age" title="max-age">Section 7.2.2.8</a> 1549 </td> 1550 </tr> 1551 <tr> 1552 <td class="left">max-stale</td> 1553 <td class="left"> <a href="#cache-request-directive.max-stale" title="max-stale">Section 7.2.1.2</a> 1554 </td> 1555 </tr> 1556 <tr> 1557 <td class="left">min-fresh</td> 1558 <td class="left"> <a href="#cache-request-directive.min-fresh" title="min-fresh">Section 7.2.1.3</a> 1559 </td> 1560 </tr> 1561 <tr> 1562 <td class="left">must-revalidate</td> 1563 <td class="left"> <a href="#cache-response-directive.must-revalidate" title="must-revalidate">Section 7.2.2.1</a> 1564 </td> 1565 </tr> 1566 <tr> 1567 <td class="left">no-cache</td> 1568 <td class="left"> <a href="#cache-request-directive.no-cache" title="no-cache">Section 7.2.1.4</a>, <a href="#cache-response-directive.no-cache" title="no-cache">Section 7.2.2.2</a> 1569 </td> 1570 </tr> 1571 <tr> 1572 <td class="left">no-store</td> 1573 <td class="left"> <a href="#cache-request-directive.no-store" title="no-store">Section 7.2.1.5</a>, <a href="#cache-response-directive.no-store" title="no-store">Section 7.2.2.3</a> 1574 </td> 1575 </tr> 1576 <tr> 1577 <td class="left">no-transform</td> 1578 <td class="left"> <a href="#cache-request-directive.no-transform" title="no-transform">Section 7.2.1.6</a>, <a href="#cache-response-directive.no-transform" title="no-transform">Section 7.2.2.4</a> 1579 </td> 1580 </tr> 1581 <tr> 1582 <td class="left">only-if-cached</td> 1583 <td class="left"> <a href="#cache-request-directive.only-if-cached" title="only-if-cached">Section 7.2.1.7</a> 1584 </td> 1585 </tr> 1586 <tr> 1587 <td class="left">private</td> 1588 <td class="left"> <a href="#cache-response-directive.private" title="private">Section 7.2.2.6</a> 1589 </td> 1590 </tr> 1591 <tr> 1592 <td class="left">proxy-revalidate</td> 1593 <td class="left"> <a href="#cache-response-directive.proxy-revalidate" title="proxy-revalidate">Section 7.2.2.7</a> 1594 </td> 1595 </tr> 1596 <tr> 1597 <td class="left">public</td> 1598 <td class="left"> <a href="#cache-response-directive.public" title="public">Section 7.2.2.5</a> 1599 </td> 1600 </tr> 1601 <tr> 1602 <td class="left">s-maxage</td> 1603 <td class="left"> <a href="#cache-response-directive.s-maxage" title="s-maxage">Section 7.2.2.9</a> 1604 </td> 1605 </tr> 1606 <tr> 1607 <td class="left">stale-if-error</td> 1608 <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.1"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-4">Section 4</a> 1609 </td> 1610 </tr> 1611 <tr> 1612 <td class="left">stale-while-revalidate</td> 1613 <td class="left"> <a href="#RFC5861" id="rfc.xref.RFC5861.2"><cite title="HTTP Cache-Control Extensions for Stale Content">[RFC5861]</cite></a>, <a href="http://tools.ietf.org/html/rfc5861#section-3">Section 3</a> 1614 </td> 1615 </tr> 1616 </tbody> 1617 </table> 1618 </div> 1619 <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a> <a id="warn.code.registration" href="#warn.code.registration">Warn Code Registry</a></h2> 1620 <p id="rfc.section.9.2.p.1">The registration procedure for HTTP Warn Codes is defined by <a href="#warn.code.extensions" title="Warn Code Extensions">Section 7.5.8</a> of this document. 1621 </p> 1622 <p id="rfc.section.9.2.p.2">The HTTP Warn Code Registry shall be created at <<a href="http://www.iana.org/assignments/http-cache-directives">http://www.iana.org/assignments/http-cache-directives</a>> and be populated with the registrations below: 1623 </p> 1623 <p id="rfc.section.9.2.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><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>). 1624 </p> 1625 <h3 id="rfc.section.9.2.2"><a href="#rfc.section.9.2.2">9.2.2</a> <a id="warn.code.registration" href="#warn.code.registration">Registrations</a></h3> 1626 <p id="rfc.section.9.2.2.p.1">The HTTP Warn Code Registry shall be populated with the registrations below:</p> 1624 1627 <div id="rfc.table.2"> 1625 1628 <div id="iana.warn.code.registration.table"></div> … … 2005 2008 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/436">http://tools.ietf.org/wg/httpbis/trac/ticket/436</a>>: "explain list expansion in ABNF appendices" 2006 2009 </li> 2010 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/464">http://tools.ietf.org/wg/httpbis/trac/ticket/464</a>>: "placement of extension point considerations" 2011 </li> 2007 2012 </ul> 2008 2013 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> … … 2012 2017 <ul class="ind"> 2013 2018 <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul> 2014 <li>110 Response is Stale (warn code) <a href="#rfc.iref.50"><b>7.5.1</b></a>, <a href="#rfc.xref.warn.110.1">9.2 </a></li>2015 <li>111 Revalidation Failed (warn code) <a href="#rfc.iref.50"><b>7.5.2</b></a>, <a href="#rfc.xref.warn.111.1">9.2 </a></li>2016 <li>112 Disconnected Operation (warn code) <a href="#rfc.iref.50"><b>7.5.3</b></a>, <a href="#rfc.xref.warn.112.1">9.2 </a></li>2017 <li>113 Heuristic Expiration (warn code) <a href="#rfc.iref.50"><b>7.5.4</b></a>, <a href="#rfc.xref.warn.113.1">9.2 </a></li>2018 <li>199 Miscellaneous Warning (warn code) <a href="#rfc.iref.50"><b>7.5.5</b></a>, <a href="#rfc.xref.warn.199.1">9.2 </a></li>2019 <li>110 Response is Stale (warn code) <a href="#rfc.iref.50"><b>7.5.1</b></a>, <a href="#rfc.xref.warn.110.1">9.2.2</a></li> 2020 <li>111 Revalidation Failed (warn code) <a href="#rfc.iref.50"><b>7.5.2</b></a>, <a href="#rfc.xref.warn.111.1">9.2.2</a></li> 2021 <li>112 Disconnected Operation (warn code) <a href="#rfc.iref.50"><b>7.5.3</b></a>, <a href="#rfc.xref.warn.112.1">9.2.2</a></li> 2022 <li>113 Heuristic Expiration (warn code) <a href="#rfc.iref.50"><b>7.5.4</b></a>, <a href="#rfc.xref.warn.113.1">9.2.2</a></li> 2023 <li>199 Miscellaneous Warning (warn code) <a href="#rfc.iref.50"><b>7.5.5</b></a>, <a href="#rfc.xref.warn.199.1">9.2.2</a></li> 2019 2024 </ul> 2020 2025 </li> 2021 2026 <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> 2022 <li>214 Transformation Applied (warn code) <a href="#rfc.iref.50"><b>7.5.6</b></a>, <a href="#rfc.xref.warn.214.1">9.2 </a></li>2023 <li>299 Miscellaneous Persistent Warning (warn code) <a href="#rfc.iref.50"><b>7.5.7</b></a>, <a href="#rfc.xref.warn.299.1">9.2 </a></li>2027 <li>214 Transformation Applied (warn code) <a href="#rfc.iref.50"><b>7.5.6</b></a>, <a href="#rfc.xref.warn.214.1">9.2.2</a></li> 2028 <li>299 Miscellaneous Persistent Warning (warn code) <a href="#rfc.iref.50"><b>7.5.7</b></a>, <a href="#rfc.xref.warn.299.1">9.2.2</a></li> 2024 2029 </ul> 2025 2030 </li> … … 2142 2147 </ul> 2143 2148 </li> 2144 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1"> 7.5.8</a>, <a href="#rfc.xref.RFC5226.2">9.1.1</a>, <a href="#RFC5226"><b>12.2</b></a><ul>2145 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1"> 7.5.8</a>, <a href="#rfc.xref.RFC5226.2">9.1.1</a></li>2149 <li><em>RFC5226</em> <a href="#rfc.xref.RFC5226.1">9.1.1</a>, <a href="#rfc.xref.RFC5226.2">9.2.1</a>, <a href="#RFC5226"><b>12.2</b></a><ul> 2150 <li><em>Section 4.1</em> <a href="#rfc.xref.RFC5226.1">9.1.1</a>, <a href="#rfc.xref.RFC5226.2">9.2.1</a></li> 2146 2151 </ul> 2147 2152 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r2243 r2244 1762 1762 <section title="Warn Code Extensions" anchor="warn.code.extensions"> 1763 1763 <t> 1764 The HTTP Warn Code Registry defines the name space for warn codes. 1765 </t> 1766 <t> 1767 A registration &MUST; include the following fields: 1768 <list style="symbols"> 1769 <t>Warn Code (3 digits)</t> 1770 <t>Short Description</t> 1771 <t>Pointer to specification text</t> 1772 </list> 1773 </t> 1774 <t> 1775 Values to be added to this name space require IETF Review (see <xref 1776 target="RFC5226" x:fmt="," x:sec="4.1"/>). 1777 </t> 1778 <t> 1779 The registry itself is maintained at <eref 1780 target="http://www.iana.org/assignments/http-warn-codes"/>. 1764 Extension warn codes can be defined; see <xref target="warn.code.registry.procedure"/> 1765 for details. 1781 1766 </t> 1782 1767 </section> … … 1813 1798 1814 1799 <section title="Procedure" anchor="cache.directive.registry.procedure"> 1815 <t>1816 The HTTP Cache Directive Registry defines the name space for the cache1817 directives.1818 </t>1819 1800 <t> 1820 1801 A registration &MUST; include the following fields: … … 1832 1813 <section title="Registrations" anchor="cache.directive.registration"> 1833 1814 <t> 1834 The HTTP Cache Directive shall be populated with the registrations below:1815 The HTTP Cache Directive Registry shall be populated with the registrations below: 1835 1816 </t> 1836 1817 <?BEGININC p6-cache.cache-directives ?> … … 1903 1884 </section> 1904 1885 1905 <section title="Warn Code Registry" 1906 anchor="warn.code.registration"> 1907 <t> 1908 The registration procedure for HTTP Warn Codes is defined by <xref 1909 target="warn.code.extensions"/> of this document. 1910 </t> 1911 <t> 1912 The HTTP Warn Code Registry shall be created at <eref 1913 target="http://www.iana.org/assignments/http-cache-directives"/> and be 1914 populated with the registrations below: 1886 <section title="Warn Code Registry" anchor="warn.code.registry"> 1887 <t> 1888 The HTTP Warn Code Registry defines the value space for warn codes. 1889 It will be created and maintained at 1890 <eref target="http://www.iana.org/assignments/http-warn-codes"/>. 1891 </t> 1892 1893 <section title="Procedure" anchor="warn.code.registry.procedure"> 1894 <t> 1895 A registration &MUST; include the following fields: 1896 <list style="symbols"> 1897 <t>Warn Code (3 digits)</t> 1898 <t>Short Description</t> 1899 <t>Pointer to specification text</t> 1900 </list> 1901 </t> 1902 <t> 1903 Values to be added to this name space require IETF Review (see <xref 1904 target="RFC5226" x:fmt="," x:sec="4.1"/>). 1905 </t> 1906 </section> 1907 1908 <section title="Registrations" anchor="warn.code.registration"> 1909 <t> 1910 The HTTP Warn Code Registry shall be populated with the registrations below: 1915 1911 </t> 1916 1912 <?BEGININC p6-cache.iana-warn-codes ?> … … 1959 1955 <?ENDINC p6-cache.iana-warn-codes ?> 1960 1956 </section> 1957 </section> 1961 1958 1962 1959 <section title="Header Field Registration" anchor="header.field.registration"> … … 2646 2643 "explain list expansion in ABNF appendices" 2647 2644 </t> 2648 <!--<t>2645 <t> 2649 2646 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/464"/>: 2650 2647 "placement of extension point considerations" 2651 </t> -->2648 </t> 2652 2649 </list> 2653 2650 </t>
Note: See TracChangeset
for help on using the changeset viewer.