Changeset 591 for draft-ietf-httpbis
- Timestamp:
- Jun 4, 2009, 11:56:35 PM (11 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r588 r591 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">June 1, 2009</td>473 <td class="header right">June 4, 2009</td> 474 474 </tr> 475 475 </table> … … 759 759 <li>Pointer to specification text</li> 760 760 </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>). 763 762 </p> 764 763 <p id="rfc.section.2.1.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>>. … … 853 852 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="status.code.registry" href="#status.code.registry">Status Code Registry</a></h2> 854 853 <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>). 857 855 </p> 858 856 <p id="rfc.section.4.1.p.3">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>>. … … 2484 2482 <ul> 2485 2483 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/164">http://tools.ietf.org/wg/httpbis/trac/ticket/164</a>>: "status codes vs methods" 2484 </li> 2485 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/170">http://tools.ietf.org/wg/httpbis/trac/ticket/170</a>>: "Do not require "updates" relation for specs that register status codes or method names" 2486 2486 </li> 2487 2487 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r588 r591 459 459 <t> 460 460 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"/>). 464 462 </t> 465 463 <t> … … 599 597 <t> 600 598 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"/>). 604 600 </t> 605 601 <t> … … 3578 3574 "status codes vs methods" 3579 3575 </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> 3580 3580 </list> 3581 3581 </t>
Note: See TracChangeset
for help on using the changeset viewer.