Changeset 262


Ignore:
Timestamp:
Jun 12, 2008, 2:57:07 AM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #59: Take over HTTP Status Code Registry from RFC2817 (closes #59).

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/extract-status-code-defs.xslt

    r255 r262  
    1313  <t>
    1414    The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
    15     should be updated with the registrations below (see <xref target="RFC2817" x:sec="7.1" x:fmt=","/>).
     15    should be updated with the registrations below:
    1616  </t>
    1717  <texttable>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r261 r262  
    419419         </tr>
    420420         <tr>
     421            <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     422            </td>
     423            <td class="header right">J. Mogul</td>
     424         </tr>
     425         <tr>
    421426            <td class="header left">Intended status: Standards Track</td>
    422             <td class="header right">J. Mogul</td>
     427            <td class="header right">HP</td>
    423428         </tr>
    424429         <tr>
    425430            <td class="header left">Expires: December 2008</td>
    426             <td class="header right">HP</td>
    427          </tr>
    428          <tr>
    429             <td class="header left"></td>
    430431            <td class="header right">H. Frystyk</td>
    431432         </tr>
     
    476477         <tr>
    477478            <td class="header left"></td>
    478             <td class="header right">June 6, 2008</td>
     479            <td class="header right">June 12, 2008</td>
    479480         </tr>
    480481      </table>
     
    520521         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a></li>
    521522         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#request.header.fields">Request Header Fields</a></li>
    522          <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></li>
     523         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a><ul class="toc">
     524               <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registry">Status Code Registry</a></li>
     525            </ul>
     526         </li>
    523527         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a></li>
    524528         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#entity">Entity</a></li>
     
    809813         which will explain the unusual status.
    810814      </p>
     815      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2>
     816      <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response.</p>
     817      <p id="rfc.section.5.1.p.2">Values to be added to this name space are subject to IETF review (<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>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this
     818         document.
     819      </p>
     820      <p id="rfc.section.5.1.p.3">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
     821      </p>
    811822      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response.header.fields" href="#response.header.fields">Response Header Fields</a></h1>
    812823      <p id="rfc.section.6.p.1">The response-header fields allow the server to pass additional information about the response which cannot be placed in the
     
    15791590</pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    15801591      <h2 id="rfc.section.11.1"><a href="#rfc.section.11.1">11.1</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registry</a></h2>
    1581       <p id="rfc.section.11.1.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below (see <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>, <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a>).
     1592      <p id="rfc.section.11.1.p.1">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> -- is now defined by <a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a> of this document.
     1593      </p>
     1594      <p id="rfc.section.11.1.p.2">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
    15821595      </p>
    15831596      <div id="rfc.table.u.1">
     
    20122025      <h2 id="rfc.references.2"><a href="#rfc.section.14.2" id="rfc.section.14.2">14.2</a> Informative References
    20132026      </h2>
    2014       <table summary="Informative References">             
     2027      <table summary="Informative References">               
    20152028         <tr>
    20162029            <td class="reference"><b id="Luo1998">[Luo1998]</b></td>
     
    20462059            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
    20472060            <td class="top"><a title="Nine by Nine">Klyne, G.</a>, <a title="BEA Systems">Nottingham, M.</a>, and <a title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     2061            </td>
     2062         </tr>
     2063         <tr>
     2064            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
     2065            <td class="top"><a title="IBM">Narten, T.</a> and <a title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    20482066            </td>
    20492067         </tr>
     
    20942112      </p>
    20952113      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2096       <p id="rfc.section.A.2.p.1">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;8.5</a>)
    2097       </p>
    2098       <p id="rfc.section.A.2.p.2">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     2114      <p id="rfc.section.A.2.p.1">This document takes over the Status Code Registry, 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.2"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;5.1</a>)
     2115      </p>
     2116      <p id="rfc.section.A.2.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.2" title="POST">Section&nbsp;8.5</a>)
     2117      </p>
     2118      <p id="rfc.section.A.2.p.3">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    20992119         user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.3" title="307 Temporary Redirect">9.3.8</a>)
    21002120      </p>
    2101       <p id="rfc.section.A.2.p.3">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
     2121      <p id="rfc.section.A.2.p.4">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource
    21022122         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    21032123         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;9.3.6</a>)
    21042124      </p>
    2105       <p id="rfc.section.A.2.p.4">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
     2125      <p id="rfc.section.A.2.p.5">Reclassify Allow header as response header, removing the option to specify it in a PUT request. Relax the server requirement
    21062126         on the contents of the Allow header and remove requirement on clients to always trust the header value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;10.1</a>)
    21072127      </p>
    2108       <p id="rfc.section.A.2.p.5">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
     2128      <p id="rfc.section.A.2.p.6">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications
    21092129         as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;10.4</a>)
    21102130      </p>
    2111       <p id="rfc.section.A.2.p.6">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
     2131      <p id="rfc.section.A.2.p.7">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly
    21122132         in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;10.8</a>)
    21132133      </p>
     
    21642184         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/24</a>&gt;: "Requiring Allow in 405 responses"
    21652185         </li>
     2186         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59</a>&gt;: "Status Code Registry"
     2187         </li>
    21662188         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61</a>&gt;: "Redirection vs. Location"
    21672189         </li>
     
    21802202         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
    21812203      </ul>
    2182       <p id="rfc.section.B.4.p.3">Ongoing work on IANA HTTP Status Code Registration (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59</a>&gt;):
    2183       </p>
    2184       <ul>
    2185          <li>Reference RFC 2817, and update the HTTP status code registrations.</li>
    2186       </ul>
    2187       <p id="rfc.section.B.4.p.4">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
     2204      <p id="rfc.section.B.4.p.3">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
    21882205      </p>
    21892206      <ul>
     
    24312448                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li>
    24322449                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
    2433                   <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a><ul class="ind">
    2434                         <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.1</a></li>
     2450                  <li class="indline1"><em>RFC2817</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#RFC2817"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a><ul class="ind">
     2451                        <li class="indline1"><em>Section 7.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2817.1">11.1</a>, <a class="iref" href="#rfc.xref.RFC2817.2">A.2</a></li>
    24352452                     </ul>
    24362453                  </li>
     
    24402457                  </li>
    24412458                  <li class="indline1"><em>RFC3864</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC3864.1">11.2</a>, <a class="iref" href="#RFC3864"><b>14.2</b></a></li>
     2459                  <li class="indline1"><em>RFC5226</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">5.1</a>, <a class="iref" href="#RFC5226"><b>14.2</b></a><ul class="ind">
     2460                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">5.1</a></li>
     2461                     </ul>
     2462                  </li>
    24422463               </ul>
    24432464            </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r261 r262  
    7373<?rfc-ext allow-markup-in-artwork="yes" ?>
    7474<?rfc-ext include-references-in-index="yes" ?>
    75 <rfc obsoletes="2616" category="std"
     75<rfc obsoletes="2616" updates="2817" category="std"
    7676     ipr="full3978" docName="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"
    7777     xmlns:x='http://purl.org/net/xml2rfc/ext'>
     
    539539   information which will explain the unusual status.
    540540</t>
     541
     542<section title="Status Code Registry" anchor="status.code.registry">
     543<t>
     544  The HTTP Status Code Registry defines the name space for the Status-Code
     545  token in the Status line of an HTTP response.
     546</t>
     547<t>
     548  Values to be added to this name space are subject to IETF review
     549  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering
     550  new status codes should be traceable through statuses of either 'Obsoletes'
     551  or 'Updates' to this document.
     552</t>
     553<t>
     554  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>.
     555</t>
     556</section>
     557
    541558</section>
    542559
     
    20742091<section title="IANA Considerations" anchor="IANA.considerations">
    20752092<section title="Status Code Registry" anchor="status.code.registration">
     2093<t>
     2094  The registration procedure for HTTP Status Codes -- previously defined
     2095  in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/> -- is now defined
     2096  by <xref target="status.code.registry"/> of this document.
     2097</t>
    20762098<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
    20772099<!--(START)-->
    20782100<t xmlns:x="http://purl.org/net/xml2rfc/ext">
    20792101    The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
    2080     should be updated with the registrations below (see <xref target="RFC2817" x:sec="7.1" x:fmt=","/>).
     2102    should be updated with the registrations below:
    20812103  </t>
    20822104<texttable xmlns:x="http://purl.org/net/xml2rfc/ext">
     
    23312353   </c>
    23322354</texttable>
    2333 <t xmlns:x="http://purl.org/net/xml2rfc/ext"/>
    23342355<!--(END)-->
    23352356</section>
     
    29532974</reference>
    29542975
     2976<reference anchor='RFC5226'>
     2977  <front>
     2978    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
     2979    <author initials='T.' surname='Narten' fullname='T. Narten'>
     2980      <organization>IBM</organization>
     2981      <address><email>narten@us.ibm.com</email></address>
     2982    </author>
     2983    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
     2984      <organization>Google</organization>
     2985      <address><email>Harald@Alvestrand.no</email></address>
     2986    </author>
     2987    <date year='2008' month='May' />
     2988  </front>
     2989  <seriesInfo name='BCP' value='26' />
     2990  <seriesInfo name='RFC' value='5226' />
     2991</reference>
     2992
    29552993</references>
    29562994
     
    30093047
    30103048<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
     3049<t>
     3050  This document takes over the Status Code Registry, previously defined
     3051  in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>.
     3052  (<xref target="status.code.registry"/>)
     3053</t>
    30113054<t>
    30123055  Clarify definition of POST.
     
    31523195    </t>
    31533196    <t>
     3197      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59"/>:
     3198      "Status Code Registry"
     3199    </t>
     3200    <t>
    31543201      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61"/>:
    31553202      "Redirection vs. Location"
     
    31833230</t>
    31843231<t>
    3185   Ongoing work on IANA HTTP Status Code Registration (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59"/>):
    3186   <list style="symbols">
    3187     <t>
    3188       Reference RFC 2817, and update the HTTP status code registrations.
    3189     </t>
    3190   </list>
    3191 </t>
    3192 <t>
    31933232  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
    31943233  <list style="symbols">
Note: See TracChangeset for help on using the changeset viewer.