Changeset 930

Timestamp:

Jul 24, 2010, 7:39:54 AM (9 years ago)

Author:

julian.reschke@…

Message:

add IANA registry for range specifiers (see #85)

File:

• draft-ietf-httpbis/latest/p5-range.xml (modified) (5 diffs)

draft-ietf-httpbis/latest/p5-range.xml

@@ -329 +329 @@
   HTTP/1.1 has been designed to allow implementations of applications
   that do not depend on knowledge of ranges. The only range unit defined
-  by HTTP/1.1 is "bytes".
+  by HTTP/1.1 is "bytes". Additional specifiers can be defined as described
+  in <xref target="range.specifier.registry"/>.
 </t>
 <t>
@@ -337 +338 @@
   &SHOULD; pass the response to the client; a client &MUST; fail.
 </t>
+
+<section title="Range Specifier Registry" anchor="range.specifier.registry">
+<t>
+   The HTTP Ranger Specifier Registry defines the name space for the range
+   specifier 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 are subject to IETF review
+  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
+</t>
+<t>
+   The registry itself is maintained at
+   <eref target="http://www.iana.org/assignments/http-range-specifiers"/>.
+</t>
+</section>
+
 </section>
 
@@ -926 +951 @@
 </t>
 </section>
+
+<section title="Range Specifier Registration" anchor="range.specifier.registration">
+<t>
+  The registration procedure for HTTP Range Specifiers is defined by 
+  <xref target="range.specifier.registry"/> of this document.
+</t>
+<t>
+   The HTTP Range Specifier Registry should be created at <eref target="http://www.iana.org/assignments/http-range-specifiers"/>
+   and be populated with the registrations below:
+</t>
+<texttable align="left" suppress-title="true" anchor="iana.range.specifiers.table">
+   <ttcol>Range Specifier Name</ttcol>
+   <ttcol>Description</ttcol>
+   <ttcol>Reference</ttcol>
+
+   <c>bytes</c>
+   <c>a range of octets</c>
+   <c>(this specification)</c>
+</texttable>
+<t>
+   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
+</t>
+</section>
 </section>
 
@@ -1168 +1216 @@
   <seriesInfo name="BCP" value="13"/>
   <seriesInfo name="RFC" value="4288"/>
+</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>
 
@@ -1572 +1637 @@
   </list>
 </t>
+<t>
+  Ongoing work on Custom Ranges (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/85"/>):
+  <list style="symbols"> 
+    <t>
+      Add IANA registry.
+    </t>
+  </list>
+</t>
 </section>