* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #59: i59.diff

File i59.diff, 18.1 KB (added by julian.reschke@gmx.de, 7 years ago)

proposed change for part 2.

  • p2-semantics.xml

     
    7272<?rfc inline="yes"?> 
    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'> 
    7878<front> 
     
    538538   with the response, since that entity is likely to include human-readable 
    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 &SHOULD; be subject to review in 
     549  the form of a standards track document within the IETF Applications 
     550  Area.  Any such document &SHOULD; be traceable through statuses of 
     551  either 'Obsoletes' 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> 
    541556</section> 
    542557 
     558</section> 
     559 
    543560<section title="Response Header Fields" anchor="response.header.fields"> 
    544561  <x:anchor-alias value="response-header"/> 
    545562<t> 
     
    20732090 
    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"> 
    20832105   <ttcol>Value</ttcol> 
     
    23302352      <xref target="status.505"/> 
    23312353   </c> 
    23322354</texttable> 
    2333 <t xmlns:x="http://purl.org/net/xml2rfc/ext"/> 
    23342355<!--(END)--> 
    23352356</section> 
    23362357<section title="Message Header Registration" anchor="message.header.registration"> 
     
    30093030 
    30103031<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616"> 
    30113032<t> 
     3033  This document takes over the Status Code Registry, previously defined 
     3034  in <xref target="RFC2817" x:fmt="of" x:sec="7.1"/>. 
     3035  (<xref target="status.code.registry"/>) 
     3036</t> 
     3037<t> 
    30123038  Clarify definition of POST. 
    30133039  (<xref target="POST"/>) 
    30143040</t> 
     
    31513177      "Requiring Allow in 405 responses" 
    31523178    </t> 
    31533179    <t> 
     3180      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/59"/>: 
     3181      "Status Code Registry" 
     3182    </t> 
     3183    <t> 
    31543184      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/61"/>: 
    31553185      "Redirection vs. Location" 
    31563186    </t> 
     
    31823212  </list> 
    31833213</t> 
    31843214<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> 
    31933215  Ongoing work on ABNF conversion (<eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36"/>): 
    31943216  <list style="symbols">  
    31953217    <t> 
  • p2-semantics.html

     
    418418            <td class="header right">One Laptop per Child</td> 
    419419         </tr> 
    420420         <tr> 
    421             <td class="header left">Intended status: Standards Track</td> 
     421            <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved) 
     422            </td> 
    422423            <td class="header right">J. Mogul</td> 
    423424         </tr> 
    424425         <tr> 
    425             <td class="header left">Expires: December 2008</td> 
     426            <td class="header left">Intended status: Standards Track</td> 
    426427            <td class="header right">HP</td> 
    427428         </tr> 
    428429         <tr> 
    429             <td class="header left"></td> 
     430            <td class="header left">Expires: December 2008</td> 
    430431            <td class="header right">H. Frystyk</td> 
    431432         </tr> 
    432433         <tr> 
     
    475476         </tr> 
    476477         <tr> 
    477478            <td class="header left"></td> 
    478             <td class="header right">June 6, 2008</td> 
     479            <td class="header right">June 9, 2008</td> 
    479480         </tr> 
    480481      </table> 
    481482      <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p> 
     
    519520         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li> 
    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> 
    525529         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#method.definitions">Method Definitions</a><ul class="toc"> 
     
    808812         something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents <em class="bcp14">SHOULD</em> present to the user the entity returned with the response, since that entity is likely to include human-readable information 
    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 <em class="bcp14">SHOULD</em> be subject to review in the form of a standards track document within the IETF Applications Area. Any such document <em class="bcp14">SHOULD</em> be traceable through statuses of either 'Obsoletes' or 'Updates' to this document. 
     818      </p> 
     819      <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;. 
     820      </p> 
    811821      <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> 
    812822      <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 
    813823         Status-Line. These header fields give information about the server and about further access to the resource identified by 
     
    15781588      <div id="rfc.figure.u.29"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3 
    15791589</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> 
    15801590      <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>). 
     1591      <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. 
    15821592      </p> 
     1593      <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: 
     1594      </p> 
    15831595      <div id="rfc.table.u.1"> 
    15841596         <table summary="" class="tt full" cellpadding="3" cellspacing="0"> 
    15851597            <thead> 
     
    20932105      <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 
    20942106      </p> 
    20952107      <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>) 
     2108      <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>) 
    20972109      </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 
     2110      <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>) 
     2111      </p> 
     2112      <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 
    20992113         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>) 
    21002114      </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 
     2115      <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 
    21022116         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 
    21032117         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>) 
    21042118      </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 
     2119      <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 
    21062120         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>) 
    21072121      </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 
     2122      <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 
    21092123         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>) 
    21102124      </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 
     2125      <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 
    21122126         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>) 
    21132127      </p> 
    21142128      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1> 
     
    21632177      <ul> 
    21642178         <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" 
    21652179         </li> 
     2180         <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" 
     2181         </li> 
    21662182         <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" 
    21672183         </li> 
    21682184         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/70</a>&gt;: "Cacheability of 303 response" 
     
    21792195      <ul> 
    21802196         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li> 
    21812197      </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;):  
     2198      <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;):  
    21832199      </p> 
    21842200      <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;):  
    2188       </p> 
    2189       <ul> 
    21902201         <li>Replace string literals when the string really is case-sensitive (method).</li> 
    21912202      </ul> 
    21922203      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1> 
     
    24302441                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li> 
    24312442                  <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> 
    24322443                  <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> 
     2444                  <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"> 
     2445                        <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> 
    24352446                     </ul> 
    24362447                  </li> 
    24372448                  <li class="indline1"><em>RFC2822</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2822.1">10.3</a>, <a class="iref" href="#rfc.xref.RFC2822.2">10.3</a>, <a class="iref" href="#RFC2822"><b>14.2</b></a><ul class="ind"> 
  • extract-status-code-defs.xslt

     
    1212  <xsl:text>&#10;</xsl:text> 
    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> 
    1818    <ttcol>Value</ttcol>