Changeset 591 for draft-ietf-httpbis

Timestamp:

05/06/09 06:56:35 (13 years ago)

Author:

julian.reschke@…

Message:

Do not require "updates" relation for specs that define new status codes or method name (related to #170)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (4 diffs)
• p2-semantics.xml (modified) (3 diffs)

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

@@ -471 +471 @@
          <tr>
             <td class="header left"></td>
-            <td class="header right">June 1, 2009</td>
+            <td class="header right">June 4, 2009</td>
          </tr>
       </table>
@@ -759 +759 @@
          <li>Pointer to specification text</li>
       </ul>
-      <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
-         document.
+      <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>).
       </p>
       <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;.
@@ -853 +852 @@
       <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>
       <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>
-      <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
-         document.
+      <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>).
       </p>
       <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;.
@@ -2484 +2482 @@
       <ul>
          <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"
+         </li>
+         <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"
          </li>
       </ul>

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

@@ -459 +459 @@
 <t>
   Values to be added to this name space are subject to IETF review
-  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering
-  new method names should be traceable through statuses of either 'Obsoletes'
-  or 'Updates' to this document.
+  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
 </t>
 <t>
@@ -599 +597 @@
 <t>
   Values to be added to this name space are subject to IETF review
-  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).  Any document registering
-  new status codes should be traceable through statuses of either 'Obsoletes'
-  or 'Updates' to this document.
+  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
 </t>
 <t>
@@ -3578 +3574 @@
       "status codes vs methods"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/170"/>:
+      "Do not require "updates" relation for specs that register status codes or method names"
+    </t>
   </list>
 </t>