Ignore:
Timestamp:
Jul 24, 2010, 7:39:54 AM (9 years ago)
Author:
julian.reschke@…
Message:

add IANA registry for range specifiers (see #85)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p5-range.xml

    r926 r930  
    329329  HTTP/1.1 has been designed to allow implementations of applications
    330330  that do not depend on knowledge of ranges. The only range unit defined
    331   by HTTP/1.1 is "bytes".
     331  by HTTP/1.1 is "bytes". Additional specifiers can be defined as described
     332  in <xref target="range.specifier.registry"/>.
    332333</t>
    333334<t>
     
    337338  &SHOULD; pass the response to the client; a client &MUST; fail.
    338339</t>
     340
     341<section title="Range Specifier Registry" anchor="range.specifier.registry">
     342<t>
     343   The HTTP Ranger Specifier Registry defines the name space for the range
     344   specifier names.
     345</t>
     346<t>
     347   Registrations &MUST; include the following fields:
     348   <list style="symbols">
     349     <t>Name</t>
     350     <t>Description</t>
     351     <t>Pointer to specification text</t>
     352   </list>
     353</t>
     354<t>
     355  Values to be added to this name space are subject to IETF review
     356  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     357</t>
     358<t>
     359   The registry itself is maintained at
     360   <eref target="http://www.iana.org/assignments/http-range-specifiers"/>.
     361</t>
     362</section>
     363
    339364</section>
    340365
     
    926951</t>
    927952</section>
     953
     954<section title="Range Specifier Registration" anchor="range.specifier.registration">
     955<t>
     956  The registration procedure for HTTP Range Specifiers is defined by
     957  <xref target="range.specifier.registry"/> of this document.
     958</t>
     959<t>
     960   The HTTP Range Specifier Registry should be created at <eref target="http://www.iana.org/assignments/http-range-specifiers"/>
     961   and be populated with the registrations below:
     962</t>
     963<texttable align="left" suppress-title="true" anchor="iana.range.specifiers.table">
     964   <ttcol>Range Specifier Name</ttcol>
     965   <ttcol>Description</ttcol>
     966   <ttcol>Reference</ttcol>
     967
     968   <c>bytes</c>
     969   <c>a range of octets</c>
     970   <c>(this specification)</c>
     971</texttable>
     972<t>
     973   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
     974</t>
     975</section>
    928976</section>
    929977
     
    11681216  <seriesInfo name="BCP" value="13"/>
    11691217  <seriesInfo name="RFC" value="4288"/>
     1218</reference>
     1219
     1220<reference anchor='RFC5226'>
     1221  <front>
     1222    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
     1223    <author initials='T.' surname='Narten' fullname='T. Narten'>
     1224      <organization>IBM</organization>
     1225      <address><email>narten@us.ibm.com</email></address>
     1226    </author>
     1227    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
     1228      <organization>Google</organization>
     1229      <address><email>Harald@Alvestrand.no</email></address>
     1230    </author>
     1231    <date year='2008' month='May' />
     1232  </front>
     1233  <seriesInfo name='BCP' value='26' />
     1234  <seriesInfo name='RFC' value='5226' />
    11701235</reference>
    11711236
     
    15721637  </list>
    15731638</t>
     1639<t>
     1640  Ongoing work on Custom Ranges (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/85"/>):
     1641  <list style="symbols">
     1642    <t>
     1643      Add IANA registry.
     1644    </t>
     1645  </list>
     1646</t>
    15741647</section>
    15751648
Note: See TracChangeset for help on using the changeset viewer.