Changeset 670 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

07/08/09 14:18:03 (13 years ago)

Author:

julian.reschke@…

Message:

Rephrase registration procedures for Transfer/Content? Codings in terms of RFC5226, requiring Expert Review & Specification (see #188)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (6 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -1795 +1795 @@
 </t>
 <t>
-   The Internet Assigned Numbers Authority (IANA) acts as a registry for
-   transfer-coding value tokens. Initially, the registry contains the
-   following tokens: "chunked" (<xref target="chunked.transfer.encoding"/>),
-   "gzip", "compress", and "deflate" (&content-codings;).
-</t>
-<t>
-   New transfer-coding value tokens &SHOULD; be registered in the same way
-   as new content-coding value tokens (&content-codings;).
-</t>
-<t>
    A server which receives an entity-body with a transfer-coding it does
    not understand &SHOULD; return 501 (Not Implemented), and close the
@@ -1907 +1897 @@
    "chunked" transfer-coding, and &MUST; ignore chunk-ext extensions
    they do not understand.
+</t>
+</section>
+
+<section title="Transfer Coding Registry" anchor="transfer.coding.registry">
+<t>
+   The HTTP Transfer Coding Registry defines the name space for the transfer
+   coding names.
+</t>
+<t>
+   Registrations &MUST; include the following fields:
+   <list style="symbols">
+     <t>Name</t>
+     <t>Description</t>
+     <t>Pointer to specification text</t>
+   </list>
+</t>
+<t>
+   Values to be added to this name space require expert review and a specification
+   (see "Expert Review" and "Specification Required" in
+   <xref target="RFC5226" x:fmt="of" x:sec="4.1"/>), and &MUST;
+   conform to the purpose of transfer coding defined in this section.
+</t>
+<t>
+   The registry itself is maintained at
+   <eref target="http://www.iana.org/assignments/http-parameters"/>.
 </t>
 </section>
@@ -3200 +3215 @@
 <t>
    The registration procedure for HTTP Transfer Codings is now defined
-   by <xref target="transfer.codings"/> of this document.
+   by <xref target="transfer.coding.registry"/> of this document.
 </t>
 <t>
@@ -3207 +3222 @@
 </t>
 <texttable align="left" suppress-title="true" anchor="iana.transfer.coding.registration.table">
-   <ttcol>Registry Name</ttcol>
+   <ttcol>Name</ttcol>
    <ttcol>Description</ttcol>
    <ttcol>Reference</ttcol>
@@ -4039 +4054 @@
 </reference>
 
+<reference anchor='RFC5226'>
+  <front>
+    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
+    <author initials='T.' surname='Narten' fullname='T. Narten'>
+      <organization>IBM</organization>
+      <address><email>narten@us.ibm.com</email></address>
+    </author>
+    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
+      <organization>Google</organization>
+      <address><email>Harald@Alvestrand.no</email></address>
+    </author>
+    <date year='2008' month='May' />
+  </front>
+  <seriesInfo name='BCP' value='26' />
+  <seriesInfo name='RFC' value='5226' />
+</reference>
+
 <reference anchor="RFC5322">
   <front>
@@ -4966 +4998 @@
       "IP addresses in URLs"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/188"/>:
+      "pick IANA policy (RFC5226) for Transfer Coding / Content Coding"
+    </t>
   </list>
 </t>