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

Ticket #170: 170.diff

File 170.diff, 5.5 KB (added by julian.reschke@gmx.de, 6 years ago)

proposed change for part 2

  • p2-semantics.xml

     
    458458</t> 
    459459<t> 
    460460  Values to be added to this name space are subject to IETF review 
    461   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering 
    462   new method names should be traceable through statuses of either 'Obsoletes' 
    463   or 'Updates' to this document. 
     461  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 
    464462</t> 
    465463<t> 
    466464  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-methods"/>. 
     
    598596</t> 
    599597<t> 
    600598  Values to be added to this name space are subject to IETF review 
    601   (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering 
    602   new status codes should be traceable through statuses of either 'Obsoletes' 
    603   or 'Updates' to this document. 
     599  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 
    604600</t> 
    605601<t> 
    606602  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-status-codes"/>. 
     
    35773573      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/164"/>: 
    35783574      "status codes vs methods" 
    35793575    </t> 
     3576    <t> 
     3577      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/170"/>: 
     3578      "Do not require "updates" relation for specs that register status codes or method names" 
     3579    </t> 
    35803580  </list> 
    35813581</t> 
    35823582</section> 
  • p2-semantics.html

     
    470470         </tr> 
    471471         <tr> 
    472472            <td class="header left"></td> 
    473             <td class="header right">June 1, 2009</td> 
     473            <td class="header right">June 4, 2009</td> 
    474474         </tr> 
    475475      </table> 
    476476      <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p> 
     
    758758         </li> 
    759759         <li>Pointer to specification text</li> 
    760760      </ul> 
    761       <p id="rfc.section.2.1.p.3">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 method names should be traceable through statuses of either 'Obsoletes' or 'Updates' to this 
    762          document. 
     761      <p id="rfc.section.2.1.p.3">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>). 
    763762      </p> 
    764763      <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;. 
    765764      </p> 
     
    852851      </p> 
    853852      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2> 
    854853      <p id="rfc.section.4.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> 
    855       <p id="rfc.section.4.1.p.2">Values to be added to this name space are subject to IETF review (<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>). Any document registering new status codes should be traceable through statuses of either 'Obsoletes' or 'Updates' to this 
    856          document. 
     854      <p id="rfc.section.4.1.p.2">Values to be added to this name space are subject to IETF review (<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>). 
    857855      </p> 
    858856      <p id="rfc.section.4.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;. 
    859857      </p> 
     
    24842482      <ul> 
    24852483         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/164">http://tools.ietf.org/wg/httpbis/trac/ticket/164</a>&gt;: "status codes vs methods" 
    24862484         </li> 
     2485         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/170">http://tools.ietf.org/wg/httpbis/trac/ticket/170</a>&gt;: "Do not require "updates" relation for specs that register status codes or method names" 
     2486         </li> 
    24872487      </ul> 
    24882488      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
    24892489      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a>