Ignore:
Timestamp:
07/05/13 16:47:33 (10 years ago)
Author:
julian.reschke@…
Message:

Consistency in registration descriptions, also add required fields for status code registrations (related to #464).

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r2233 r2246  
    449449  }
    450450  @bottom-center {
    451        content: "Expires November 2, 2013";
     451       content: "Expires November 8, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-05-01">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-05-07">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">May 1, 2013</td>
     522               <td class="right">May 7, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: November 2, 2013</td>
     525               <td class="left">Expires: November 8, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
    … …  
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on November 2, 2013.</p>
     553      <p>This Internet-Draft will expire on November 8, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    665665                  </ul>
    666666               </li>
    667                <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registry">Transfer Coding Registry</a></li>
    668                <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registration">Transfer Coding Registration</a></li>
    669                <li><a href="#rfc.section.7.6">7.6</a>&nbsp;&nbsp;&nbsp;<a href="#upgrade.token.registry">Upgrade Token Registry</a></li>
    670                <li><a href="#rfc.section.7.7">7.7</a>&nbsp;&nbsp;&nbsp;<a href="#upgrade.token.registration">Upgrade Token Registration</a></li>
     667               <li><a href="#rfc.section.7.4">7.4</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registry">Transfer Coding Registry</a><ul>
     668                     <li><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registry.procedure">Procedure</a></li>
     669                     <li><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#transfer.coding.registration">Registration</a></li>
     670                  </ul>
     671               </li>
     672               <li><a href="#rfc.section.7.5">7.5</a>&nbsp;&nbsp;&nbsp;<a href="#upgrade.token.registry">Upgrade Token Registry</a><ul>
     673                     <li><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;&nbsp;&nbsp;<a href="#upgrade.token.registry.procedure">Procedure</a></li>
     674                     <li><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;&nbsp;&nbsp;<a href="#upgrade.token.registration">Upgrade Token Registration</a></li>
     675                  </ul>
     676               </li>
    671677            </ul>
    672678         </li>
    … …  
    21372143      <p id="rfc.section.6.7.p.10">This specification only defines the protocol name "HTTP" for use by the family of Hypertext Transfer Protocols, as defined
    21382144         by the HTTP version rules of <a href="#http.version" title="Protocol Versioning">Section&nbsp;2.6</a> and future updates to this specification. Additional tokens ought to be registered with IANA using the registration procedure
    2139          defined in <a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.6</a>.
     2145         defined in <a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.5</a>.
    21402146      </p>
    21412147      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    21422148      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    2143       <p id="rfc.section.7.1.p.1">HTTP header fields are registered within the Message Header Field Registry <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a> maintained by IANA at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     2149      <p id="rfc.section.7.1.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
    21442150      </p>
    21452151      <p id="rfc.section.7.1.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
    2146          the permanent registrations below:
     2152         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    21472153      </p>
    21482154      <div id="rfc.table.1">
    … …  
    23902396      </dl>
    23912397      <h2 id="rfc.section.7.4"><a href="#rfc.section.7.4">7.4</a>&nbsp;<a id="transfer.coding.registry" href="#transfer.coding.registry">Transfer Coding Registry</a></h2>
    2392       <p id="rfc.section.7.4.p.1">The HTTP Transfer Coding Registry defines the name space for transfer coding names.</p>
    2393       <p id="rfc.section.7.4.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
     2398      <p id="rfc.section.7.4.p.1">The HTTP Transfer Coding Registry defines the name space for transfer coding names. It is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     2399      </p>
     2400      <h3 id="rfc.section.7.4.1"><a href="#rfc.section.7.4.1">7.4.1</a>&nbsp;<a id="transfer.coding.registry.procedure" href="#transfer.coding.registry.procedure">Procedure</a></h3>
     2401      <p id="rfc.section.7.4.1.p.1">Registrations <em class="bcp14">MUST</em> include the following fields:
    23942402      </p>
    23952403      <ul>
    … …  
    23982406         <li>Pointer to specification text</li>
    23992407      </ul>
    2400       <p id="rfc.section.7.4.p.3">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
    2401       </p>
    2402       <p id="rfc.section.7.4.p.4">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this section. Use of program names for the identification of encoding
    2403          formats is not desirable and is discouraged for future encodings.
    2404       </p>
    2405       <p id="rfc.section.7.4.p.5">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    2406       </p>
    2407       <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="transfer.coding.registration" href="#transfer.coding.registration">Transfer Coding Registration</a></h2>
    2408       <p id="rfc.section.7.5.p.1">The HTTP Transfer Coding Registry shall be updated with the registrations below:</p>
     2408      <p id="rfc.section.7.4.1.p.2">Names of transfer codings <em class="bcp14">MUST NOT</em> overlap with names of content codings (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>) unless the encoding transformation is identical, as is the case for the compression codings defined in <a href="#compression.codings" title="Compression Codings">Section&nbsp;4.2</a>.
     2409      </p>
     2410      <p id="rfc.section.7.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of transfer coding defined in this specification.
     2411      </p>
     2412      <p id="rfc.section.7.4.1.p.4">Use of program names for the identification of encoding formats is not desirable and is discouraged for future encodings.</p>
     2413      <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a>&nbsp;<a id="transfer.coding.registration" href="#transfer.coding.registration">Registration</a></h3>
     2414      <p id="rfc.section.7.4.2.p.1">The HTTP Transfer Coding Registry shall be updated with the registrations below:</p>
    24092415      <div id="rfc.table.2">
    24102416         <div id="iana.transfer.coding.registration.table"></div>
    … …  
    24462452         </table>
    24472453      </div>
    2448       <h2 id="rfc.section.7.6"><a href="#rfc.section.7.6">7.6</a>&nbsp;<a id="upgrade.token.registry" href="#upgrade.token.registry">Upgrade Token Registry</a></h2>
    2449       <p id="rfc.section.7.6.p.1">The HTTP Upgrade Token Registry defines the name space for protocol-name tokens used to identify protocols in the <a href="#header.upgrade" class="smpl">Upgrade</a> header field. Each registered protocol name is associated with contact information and an optional set of specifications that
    2450          details how the connection will be processed after it has been upgraded.
    2451       </p>
    2452       <p id="rfc.section.7.6.p.2">Registrations happen on a "First Come First Served" basis (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>) and are subject to the following rules:
     2454      <h2 id="rfc.section.7.5"><a href="#rfc.section.7.5">7.5</a>&nbsp;<a id="upgrade.token.registry" href="#upgrade.token.registry">Upgrade Token Registry</a></h2>
     2455      <p id="rfc.section.7.5.p.1">The HTTP Upgrade Token Registry defines the name space for protocol-name tokens used to identify protocols in the <a href="#header.upgrade" class="smpl">Upgrade</a> header field. The registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-upgrade-tokens">http://www.iana.org/assignments/http-upgrade-tokens</a>&gt;.
     2456      </p>
     2457      <h3 id="rfc.section.7.5.1"><a href="#rfc.section.7.5.1">7.5.1</a>&nbsp;<a id="upgrade.token.registry.procedure" href="#upgrade.token.registry.procedure">Procedure</a></h3>
     2458      <p id="rfc.section.7.5.1.p.1">Each registered protocol name is associated with contact information and an optional set of specifications that details how
     2459         the connection will be processed after it has been upgraded.
     2460      </p>
     2461      <p id="rfc.section.7.5.1.p.2">Registrations happen on a "First Come First Served" basis (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>) and are subject to the following rules:
    24532462      </p>
    24542463      <ol>
    … …  
    24682477         </li>
    24692478      </ol>
    2470       <p id="rfc.section.7.6.p.3">This registration procedure for HTTP Upgrade Tokens replaces that previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
    2471       </p>
    2472       <h2 id="rfc.section.7.7"><a href="#rfc.section.7.7">7.7</a>&nbsp;<a id="upgrade.token.registration" href="#upgrade.token.registration">Upgrade Token Registration</a></h2>
    2473       <p id="rfc.section.7.7.p.1">The HTTP Upgrade Token Registry shall be updated with the registration below:</p>
     2479      <p id="rfc.section.7.5.1.p.3">This registration procedure for HTTP Upgrade Tokens replaces that previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
     2480      </p>
     2481      <h3 id="rfc.section.7.5.2"><a href="#rfc.section.7.5.2">7.5.2</a>&nbsp;<a id="upgrade.token.registration" href="#upgrade.token.registration">Upgrade Token Registration</a></h3>
     2482      <p id="rfc.section.7.5.2.p.1">The HTTP Upgrade Token Registry shall be updated with the registration below:</p>
    24742483      <div id="rfc.table.u.3">
    24752484         <table class="tt full left" cellpadding="3" cellspacing="0">
    … …  
    24922501         </table>
    24932502      </div>
    2494       <p id="rfc.section.7.7.p.2">The responsible party is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     2503      <p id="rfc.section.7.5.2.p.2">The responsible party is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    24952504      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    24962505      <p id="rfc.section.8.p.1">This section is meant to inform developers, information providers, and users of known security concerns relevant to HTTP/1.1
    … …  
    29212930      <p id="rfc.section.A.2.p.34">The meaning of the "deflate" content coding has been clarified. (<a href="#deflate.coding" title="Deflate Coding">Section&nbsp;4.2.2</a>)
    29222931      </p>
    2923       <p id="rfc.section.A.2.p.35">This specification now defines the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.6</a>)
     2932      <p id="rfc.section.A.2.p.35">This specification now defines the Upgrade Token Registry, previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.2">Section 7.2</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#upgrade.token.registry" title="Upgrade Token Registry">Section&nbsp;7.5</a>)
    29242933      </p>
    29252934      <p id="rfc.section.A.2.p.36">Empty list elements in list productions (e.g., a list header containing ", ,") have been deprecated. (<a href="#abnf.extension" title="ABNF list extension: #rule">Appendix&nbsp;B</a>)
    … …  
    33243333            </li>
    33253334            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
    3326                   <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.1</a>, <a href="#rfc.xref.Part2.3">2.3</a>, <a href="#rfc.xref.Part2.4">2.7</a>, <a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.6">3.1.1</a>, <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a>, <a href="#rfc.xref.Part2.9">3.2</a>, <a href="#rfc.xref.Part2.10">3.2.1</a>, <a href="#rfc.xref.Part2.11">3.3</a>, <a href="#rfc.xref.Part2.12">3.3</a>, <a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.14">3.3.2</a>, <a href="#rfc.xref.Part2.15">3.3.2</a>, <a href="#rfc.xref.Part2.16">3.3.2</a>, <a href="#rfc.xref.Part2.17">4.3</a>, <a href="#rfc.xref.Part2.18">5.1</a>, <a href="#rfc.xref.Part2.19">5.3</a>, <a href="#rfc.xref.Part2.20">5.3</a>, <a href="#rfc.xref.Part2.21">5.6</a>, <a href="#rfc.xref.Part2.22">5.7.2</a>, <a href="#rfc.xref.Part2.23">6.3.1</a>, <a href="#rfc.xref.Part2.24">6.3.2</a>, <a href="#rfc.xref.Part2.25">6.3.2</a>, <a href="#rfc.xref.Part2.26">6.7</a>, <a href="#rfc.xref.Part2.27">7.4</a>, <a href="#rfc.xref.Part2.28">8.3</a>, <a href="#rfc.xref.Part2.29">8.3</a>, <a href="#Part2"><b>10.1</b></a><ul>
     3335                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.1</a>, <a href="#rfc.xref.Part2.3">2.3</a>, <a href="#rfc.xref.Part2.4">2.7</a>, <a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.6">3.1.1</a>, <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a>, <a href="#rfc.xref.Part2.9">3.2</a>, <a href="#rfc.xref.Part2.10">3.2.1</a>, <a href="#rfc.xref.Part2.11">3.3</a>, <a href="#rfc.xref.Part2.12">3.3</a>, <a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.14">3.3.2</a>, <a href="#rfc.xref.Part2.15">3.3.2</a>, <a href="#rfc.xref.Part2.16">3.3.2</a>, <a href="#rfc.xref.Part2.17">4.3</a>, <a href="#rfc.xref.Part2.18">5.1</a>, <a href="#rfc.xref.Part2.19">5.3</a>, <a href="#rfc.xref.Part2.20">5.3</a>, <a href="#rfc.xref.Part2.21">5.6</a>, <a href="#rfc.xref.Part2.22">5.7.2</a>, <a href="#rfc.xref.Part2.23">6.3.1</a>, <a href="#rfc.xref.Part2.24">6.3.2</a>, <a href="#rfc.xref.Part2.25">6.3.2</a>, <a href="#rfc.xref.Part2.26">6.7</a>, <a href="#rfc.xref.Part2.27">7.4.1</a>, <a href="#rfc.xref.Part2.28">8.3</a>, <a href="#rfc.xref.Part2.29">8.3</a>, <a href="#Part2"><b>10.1</b></a><ul>
    33273336                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.4">2.7</a></li>
    33283337                        <li><em>Section 3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.14">3.3.2</a></li>
    3329                         <li><em>Section 3.1.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.27">7.4</a></li>
     3338                        <li><em>Section 3.1.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.27">7.4.1</a></li>
    33303339                        <li><em>Section 3.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.22">5.7.2</a></li>
    33313340                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.6">3.1.1</a></li>
    … …  
    33733382                  <li><em>RFC1919</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1919.1">2.3</a>, <a href="#RFC1919"><b>10.2</b></a></li>
    33743383                  <li><em>RFC1945</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">2.6</a>, <a href="#rfc.xref.RFC1945.2">9</a>, <a href="#RFC1945"><b>10.2</b></a>, <a href="#rfc.xref.RFC1945.3">A</a></li>
    3375                   <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">4.2.2</a>, <a href="#rfc.xref.RFC1950.2">7.5</a>, <a href="#RFC1950"><b>10.1</b></a></li>
    3376                   <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">4.2.2</a>, <a href="#rfc.xref.RFC1951.2">7.5</a>, <a href="#RFC1951"><b>10.1</b></a></li>
    3377                   <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">4.2.3</a>, <a href="#rfc.xref.RFC1952.2">7.5</a>, <a href="#RFC1952"><b>10.1</b></a></li>
     3384                  <li><em>RFC1950</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1950.1">4.2.2</a>, <a href="#rfc.xref.RFC1950.2">7.4.2</a>, <a href="#RFC1950"><b>10.1</b></a></li>
     3385                  <li><em>RFC1951</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1951.1">4.2.2</a>, <a href="#rfc.xref.RFC1951.2">7.4.2</a>, <a href="#RFC1951"><b>10.1</b></a></li>
     3386                  <li><em>RFC1952</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1952.1">4.2.3</a>, <a href="#rfc.xref.RFC1952.2">7.4.2</a>, <a href="#RFC1952"><b>10.1</b></a></li>
    33783387                  <li><em>RFC2045</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2045.1">2.1</a>, <a href="#rfc.xref.RFC2045.2">3.3.1</a>, <a href="#RFC2045"><b>10.2</b></a><ul>
    33793388                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2045.2">3.3.1</a></li>
    … …  
    33913400                     </ul>
    33923401                  </li>
    3393                   <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">1</a>, <a href="#rfc.xref.RFC2817.2">7.6</a>, <a href="#RFC2817"><b>10.2</b></a>, <a href="#rfc.xref.RFC2817.3">A.2</a>, <a href="#rfc.xref.RFC2817.4">A.2</a><ul>
    3394                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.2">7.6</a>, <a href="#rfc.xref.RFC2817.4">A.2</a></li>
     3402                  <li><em>RFC2817</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.1">1</a>, <a href="#rfc.xref.RFC2817.2">7.5.1</a>, <a href="#RFC2817"><b>10.2</b></a>, <a href="#rfc.xref.RFC2817.3">A.2</a>, <a href="#rfc.xref.RFC2817.4">A.2</a><ul>
     3403                        <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2817.2">7.5.1</a>, <a href="#rfc.xref.RFC2817.4">A.2</a></li>
    33953404                     </ul>
    33963405                  </li>
    … …  
    34173426                  <li><em>RFC4033</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4033.1">8.1</a>, <a href="#RFC4033"><b>10.2</b></a></li>
    34183427                  <li><em>RFC4559</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4559.1">2.3</a>, <a href="#RFC4559"><b>10.2</b></a></li>
    3419                   <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.4</a>, <a href="#rfc.xref.RFC5226.2">7.6</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
    3420                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.4</a>, <a href="#rfc.xref.RFC5226.2">7.6</a></li>
     3428                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.4.1</a>, <a href="#rfc.xref.RFC5226.2">7.5.1</a>, <a href="#RFC5226"><b>10.2</b></a><ul>
     3429                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">7.4.1</a>, <a href="#rfc.xref.RFC5226.2">7.5.1</a></li>
    34213430                     </ul>
    34223431                  </li>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2233 r2246  
    31603160<t>
    31613161   HTTP header fields are registered within the Message Header Field Registry
    3162    <xref target="BCP90"/> maintained by IANA at
     3162   maintained at
    31633163   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
    31643164</t>
    … …  
    31663166   This document defines the following HTTP header fields, so their
    31673167   associated registry entries shall be updated according to the permanent
    3168    registrations below:
     3168   registrations below (see <xref target="BCP90"/>):
    31693169</t>
    31703170<?BEGININC p1-messaging.iana-headers ?>
    … …  
    34353435<t>
    34363436   The HTTP Transfer Coding Registry defines the name space for transfer
    3437    coding names.
    3438 </t>
     3437   coding names. It is maintained at <eref target="http://www.iana.org/assignments/http-parameters"/>.
     3438</t>
     3439
     3440<section title="Procedure" anchor="transfer.coding.registry.procedure">
    34393441<t>
    34403442   Registrations &MUST; include the following fields:
    … …  
    34543456   Values to be added to this name space require IETF Review (see
    34553457   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
    3456    conform to the purpose of transfer coding defined in this section.
     3458   conform to the purpose of transfer coding defined in this specification.
     3459</t>
     3460<t>
    34573461   Use of program names for the identification of encoding formats
    34583462   is not desirable and is discouraged for future encodings.
    34593463</t>
    3460 <t>
    3461    The registry itself is maintained at
    3462    <eref target="http://www.iana.org/assignments/http-parameters"/>.
    3463 </t>
    3464 </section>
    3465 
    3466 <section title="Transfer Coding Registration" anchor="transfer.coding.registration">
     3464</section>
     3465
     3466<section title="Registration" anchor="transfer.coding.registration">
    34673467<t>
    34683468   The HTTP Transfer Coding Registry shall be updated with the registrations
    … …  
    34973497</texttable>
    34983498</section>
     3499</section>
    34993500
    35003501<section title="Upgrade Token Registry" anchor="upgrade.token.registry">
    … …  
    35023503   The HTTP Upgrade Token Registry defines the name space for protocol-name
    35033504   tokens used to identify protocols in the <x:ref>Upgrade</x:ref> header
    3504    field. Each registered protocol name is associated with contact information
     3505   field. The registry is maintained at <eref target="http://www.iana.org/assignments/http-upgrade-tokens"/>.
     3506</t>
     3507
     3508<section title="Procedure" anchor="upgrade.token.registry.procedure">   
     3509<t>
     3510   Each registered protocol name is associated with contact information
    35053511   and an optional set of specifications that details how the connection
    35063512   will be processed after it has been upgraded.
    … …  
    35523558   The responsible party is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
    35533559</t>
     3560</section>
    35543561</section>
    35553562

  • draft-ietf-httpbis/latest/p2-semantics.html

    r2232 r2246  
    449449  }
    450450  @bottom-center {
    451        content: "Expires November 2, 2013";
     451       content: "Expires November 8, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2013-05-01">
     496      <meta name="dct.issued" scheme="ISO8601" content="2013-05-07">
    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. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
    … …  
    522522            <tr>
    523523               <td class="left">Intended status: Standards Track</td>
    524                <td class="right">May 1, 2013</td>
     524               <td class="right">May 7, 2013</td>
    525525            </tr>
    526526            <tr>
    527                <td class="left">Expires: November 2, 2013</td>
     527               <td class="left">Expires: November 8, 2013</td>
    528528               <td class="right"></td>
    529529            </tr>
    … …  
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on November 2, 2013.</p>
     555      <p>This Internet-Draft will expire on November 8, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    739739         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    740740               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul>
    741                      <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.procedure">Procedure</a></li>
     741                     <li><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#method.registry.procedure">Procedure</a></li>
    742742                     <li><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    743743                     <li><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#method.registration">Registrations</a></li>
    … …  
    745745               </li>
    746746               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a><ul>
    747                      <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.procedure">Procedure</a></li>
     747                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registry.procedure">Procedure</a></li>
    748748                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></li>
    749749                     <li><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Registrations</a></li>
    … …  
    30643064         <li>
    30653065            <p>To inform cache recipients that they <em class="bcp14">MUST NOT</em> use this response to satisfy a later request unless the later request has the same values for the listed fields as the original
    3066                request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry.
     3066               request (<a href="p6-cache.html#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>). In other words, Vary expands the cache key required to match a new request to the stored cache entry.
    30673067            </p>
    30683068         </li>
    … …  
    31923192      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    31933193      <h2 id="rfc.section.8.1"><a href="#rfc.section.8.1">8.1</a>&nbsp;<a id="method.registry" href="#method.registry">Method Registry</a></h2>
    3194       <p id="rfc.section.8.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;4</a>). The method registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    3195       </p>
    3196       <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="method.procedure" href="#method.procedure">Procedure</a></h3>
     3194      <p id="rfc.section.8.1.p.1">The HTTP Method Registry defines the name space for the request method token (<a href="#methods" title="Request Methods">Section&nbsp;4</a>). The method registry will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
     3195      </p>
     3196      <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="method.registry.procedure" href="#method.registry.procedure">Procedure</a></h3>
    31973197      <p id="rfc.section.8.1.1.p.1">HTTP method registrations <em class="bcp14">MUST</em> include the following fields:
    31983198      </p>
    … …  
    33043304      <p id="rfc.section.8.2.p.1">The HTTP Status Code Registry defines the name space for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>). The status code registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    33053305      </p>
    3306       <p id="rfc.section.8.2.p.2">This section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
    3307       </p>
    3308       <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.code.procedure" href="#status.code.procedure">Procedure</a></h3>
    3309       <p id="rfc.section.8.2.1.p.1">Values to be added to the HTTP status code 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>).
     3306      <p id="rfc.section.8.2.p.2">This Section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
     3307      </p>
     3308      <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.code.registry.procedure" href="#status.code.registry.procedure">Procedure</a></h3>
     3309      <p id="rfc.section.8.2.1.p.1">A registration <em class="bcp14">MUST</em> include the following fields:
     3310      </p>
     3311      <ul>
     3312         <li>Status Code (3 digits)</li>
     3313         <li>Short Description</li>
     3314         <li>Pointer to specification text</li>
     3315      </ul>
     3316      <p id="rfc.section.8.2.1.p.2">Values to be added to the HTTP status code 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>).
    33103317      </p>
    33113318      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="considerations.for.new.status.codes" href="#considerations.for.new.status.codes">Considerations for New Status Codes</a></h3>
    … …  
    36353642         </li>
    36363643         <li>
    3637             <p>That when the header is used in requests and affects response selection (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), it ought to be listed in the <a href="#header.vary" class="smpl">Vary</a> response header field (<a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a>).
     3644            <p>That when the header is used in requests and affects response selection (<a href="p6-cache.html#caching.negotiated.responses" title="Calculating Secondary Keys with Vary">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.29"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), it ought to be listed in the <a href="#header.vary" class="smpl">Vary</a> response header field (<a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;7.1.4</a>).
    36383645            </p>
    36393646         </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2232 r2246  
    41754175  The HTTP Method Registry defines the name space for the request method
    41764176  token (<xref target="methods"/>).
    4177   The method registry is maintained at
     4177  The method registry will be created and maintained at
    41784178  <eref target="http://www.iana.org/assignments/http-methods"/>.
    41794179</t>
    41804180
    4181 <section title="Procedure" anchor="method.procedure">
     4181<section title="Procedure" anchor="method.registry.procedure">
    41824182<t>
    41834183  HTTP method registrations &MUST; include the following fields:
    … …  
    43034303<t>
    43044304   The HTTP Status Code Registry defines the name space for the response
    4305    status-code token (<xref target="status.codes"/>).
    4306    The status code registry is maintained at
    4307    <eref target="http://www.iana.org/assignments/http-status-codes"/>.
    4308 </t>
    4309 <t>
    4310    This section replaces the registration procedure for HTTP Status Codes
     4305   status-code token (<xref target="status.codes"/>). The status code registry
     4306   is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
     4307</t>
     4308<t>
     4309   This Section replaces the registration procedure for HTTP Status Codes
    43114310   previously defined in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>.
    43124311</t>
    43134312
    4314 <section title="Procedure" anchor="status.code.procedure">
     4313<section title="Procedure" anchor="status.code.registry.procedure">
     4314<t>
     4315   A registration &MUST; include the following fields:
     4316   <list style="symbols">
     4317      <t>Status Code (3 digits)</t>
     4318      <t>Short Description</t>
     4319      <t>Pointer to specification text</t>
     4320   </list>
     4321</t>
    43154322<t>
    43164323   Values to be added to the HTTP status code name space require IETF Review

  • draft-ietf-httpbis/latest/p4-conditional.html

    r2232 r2246  
    449449  }
    450450  @bottom-center {
    451        content: "Expires November 2, 2013";
     451       content: "Expires November 8, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-05-01">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-05-07">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
    … …  
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: November 2, 2013</td>
    520                <td class="right">May 1, 2013</td>
     519               <td class="left">Expires: November 8, 2013</td>
     520               <td class="right">May 7, 2013</td>
    521521            </tr>
    522522         </tbody>
    … …  
    545545         in progress”.
    546546      </p>
    547       <p>This Internet-Draft will expire on November 2, 2013.</p>
     547      <p>This Internet-Draft will expire on November 8, 2013.</p>
    548548      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    549549      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    10561056         cache updates (e.g., <a href="#header.last-modified" class="smpl">Last-Modified</a> might be useful if the response does not have an <a href="#header.etag" class="smpl">ETag</a> field).
    10571057      </p>
    1058       <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Responses with 304 Not Modified">Section 4.2.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
     1058      <p id="rfc.section.4.1.p.4">Requirements on a cache that receives a 304 response are defined in <a href="p6-cache.html#freshening.responses" title="Freshening Stored Responses upon Validation">Section 4.2.1</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>. If the conditional request originated with an outbound client, such as a user agent with its own cache sending a conditional
    10591059         GET to a shared proxy, then the proxy <em class="bcp14">SHOULD</em> forward the 304 response to that client.
    10601060      </p>
    … …  
    11681168      </div>
    11691169      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1170       <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     1170      <p id="rfc.section.6.2.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     1171      </p>
     1172      <p id="rfc.section.6.2.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
     1173         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    11711174      </p>
    11721175      <div id="rfc.table.2">
    … …  
    12271230         </table>
    12281231      </div>
    1229       <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1232      <p id="rfc.section.6.2.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    12301233      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    12311234      <p id="rfc.section.7.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2232 r2246  
    10981098<section title="Header Field Registration" anchor="header.field.registration">
    10991099<t>
    1100    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    1101    with the permanent registrations below (see <xref target="BCP90"/>):
     1100   HTTP header fields are registered within the Message Header Field Registry
     1101   maintained at
     1102   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
     1103</t>
     1104<t>
     1105   This document defines the following HTTP header fields, so their
     1106   associated registry entries shall be updated according to the permanent
     1107   registrations below (see <xref target="BCP90"/>):
    11021108</t>
    11031109<?BEGININC p4-conditional.iana-headers ?>

  • draft-ietf-httpbis/latest/p5-range.html

    r2232 r2246  
    449449  }
    450450  @bottom-center {
    451        content: "Expires November 2, 2013";
     451       content: "Expires November 8, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2013-05-01">
     494      <meta name="dct.issued" scheme="ISO8601" content="2013-05-07">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
    … …  
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: November 2, 2013</td>
     520               <td class="left">Expires: November 8, 2013</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
    … …  
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">May 1, 2013</td>
     529               <td class="right">May 7, 2013</td>
    530530            </tr>
    531531         </tbody>
    … …  
    552552         in progress”.
    553553      </p>
    554       <p>This Internet-Draft will expire on November 2, 2013.</p>
     554      <p>This Internet-Draft will expire on November 8, 2013.</p>
    555555      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    556556      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    942942      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2>
    943943      <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.
    944          The registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
     944         The registry will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    945945      </p>
    946946      <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="range.unit.registry.procedure" href="#range.unit.registry.procedure">Procedure</a></h3>
    … …  
    10111011      </div>
    10121012      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1013       <p id="rfc.section.5.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     1013      <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     1014      </p>
     1015      <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
     1016         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    10141017      </p>
    10151018      <div id="rfc.table.3">
    … …  
    10561059         </table>
    10571060      </div>
    1058       <p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1061      <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    10591062      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    10601063      <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1

  • draft-ietf-httpbis/latest/p5-range.xml

    r2232 r2246  
    844844   The HTTP Range Unit Registry defines the name space for the range
    845845   unit names and refers to their corresponding specifications.
    846    The registry is maintained at
     846   The registry will be created and maintained at
    847847   <eref target="http://www.iana.org/assignments/http-parameters"/>.
    848848</t>
    … …  
    915915<section title="Header Field Registration" anchor="header.field.registration">
    916916<t>
    917    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    918    with the permanent registrations below (see <xref target="BCP90"/>):
     917   HTTP header fields are registered within the Message Header Field Registry
     918   maintained at
     919   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
     920</t>
     921<t>
     922   This document defines the following HTTP header fields, so their
     923   associated registry entries shall be updated according to the permanent
     924   registrations below (see <xref target="BCP90"/>):
    919925</t>
    920926<?BEGININC p5-range.iana-headers ?>

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

    r2244 r2246  
    16111611      </div>
    16121612      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<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 &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.
     1613      <p id="rfc.section.9.2.p.1">The HTTP Warn Code Registry defines the name space for warn codes. It will be created and maintained at &lt;<a href="http://www.iana.org/assignments/http-warn-codes">http://www.iana.org/assignments/http-warn-codes</a>&gt;.
    16141614      </p>
    16151615      <h3 id="rfc.section.9.2.1"><a href="#rfc.section.9.2.1">9.2.1</a>&nbsp;<a id="warn.code.registry.procedure" href="#warn.code.registry.procedure">Procedure</a></h3>
    … …  
    16821682      </div>
    16831683      <h2 id="rfc.section.9.3"><a href="#rfc.section.9.3">9.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    1684       <p id="rfc.section.9.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     1684      <p id="rfc.section.9.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     1685      </p>
     1686      <p id="rfc.section.9.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
     1687         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    16851688      </p>
    16861689      <div id="rfc.table.3">
    … …  
    17341737         </table>
    17351738      </div>
    1736       <p id="rfc.section.9.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1739      <p id="rfc.section.9.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    17371740      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    17381741      <p id="rfc.section.10.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to HTTP/1.1

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

    r2244 r2246  
    18861886<section title="Warn Code Registry" anchor="warn.code.registry">
    18871887<t>
    1888    The HTTP Warn Code Registry defines the value space for warn codes.
     1888   The HTTP Warn Code Registry defines the name space for warn codes.
    18891889   It will be created and maintained at
    18901890   <eref target="http://www.iana.org/assignments/http-warn-codes"/>.
    … …  
    19591959<section title="Header Field Registration" anchor="header.field.registration">
    19601960<t>
    1961   The Message Header Field Registry located at <eref 
    1962   target="http://www.iana.org/assignments/message-headers/message-header-index.html" />
    1963   shall be updated with the permanent registrations below (see <xref target="BCP90" />):
     1961   HTTP header fields are registered within the Message Header Field Registry
     1962   maintained at
     1963   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
     1964</t>
     1965<t>
     1966   This document defines the following HTTP header fields, so their
     1967   associated registry entries shall be updated according to the permanent
     1968   registrations below (see <xref target="BCP90"/>):
    19641969</t>
    19651970<?BEGININC p6-cache.iana-headers ?>

  • draft-ietf-httpbis/latest/p7-auth.html

    r2245 r2246  
    882882      </div>
    883883      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    884       <p id="rfc.section.5.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     884      <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the Message Header Field Registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt;.
     885      </p>
     886      <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so their associated registry entries shall be updated according to
     887         the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    885888      </p>
    886889      <div id="rfc.table.2">
    … …  
    927930         </table>
    928931      </div>
    929       <p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     932      <p id="rfc.section.5.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    930933      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    931934      <p id="rfc.section.6.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to HTTP/1.1

  • draft-ietf-httpbis/latest/p7-auth.xml

    r2245 r2246  
    625625<section title="Header Field Registration" anchor="header.field.registration">
    626626<t>
    627    The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
    628    with the permanent registrations below (see <xref target="BCP90"/>):
     627   HTTP header fields are registered within the Message Header Field Registry
     628   maintained at
     629   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
     630</t>
     631<t>
     632   This document defines the following HTTP header fields, so their
     633   associated registry entries shall be updated according to the permanent
     634   registrations below (see <xref target="BCP90"/>):
    629635</t>
    630636<?BEGININC p7-auth.iana-headers ?>
Note: See TracChangeset for help on using the changeset viewer.