Ignore:
Timestamp:
20/01/13 14:09:33 (10 years ago)
Author:
fielding@…
Message:

(editorial) move range unit registry to IANA considerations like we did for p2 registries

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p5-range.html

    r2138 r2139  
    576576            </ul>
    577577         </li>
    578          <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a><ul>
    579                <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry">Range Unit Registry</a></li>
    580             </ul>
    581          </li>
     578         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#range.units">Range Units</a></li>
    582579         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
    583580               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.206">206 Partial Content</a></li>
    … …  
    602599         </li>
    603600         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
    604                <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
    605                <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    606                <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#range.specifier.registration">Range Specifier Registration</a></li>
     601               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry">Range Unit Registry</a><ul>
     602                     <li><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registry.procedure">Procedure</a></li>
     603                     <li><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#range.unit.registration">Registrations</a></li>
     604                  </ul>
     605               </li>
     606               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
     607               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
    607608            </ul>
    608609         </li>
    … …  
    661662  <a href="#range.units" class="smpl">bytes-unit</a>       = "bytes"
    662663  <a href="#range.units" class="smpl">other-range-unit</a> = <a href="#imported.abnf" class="smpl">token</a>
    663 </pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes" (<a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>). Additional units can be defined as described in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;2.1</a>.
    664       </p>
    665       <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2>
    666       <p id="rfc.section.2.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.</p>
    667       <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
    668       </p>
    669       <ul>
    670          <li>Name</li>
    671          <li>Description</li>
    672          <li>Pointer to specification text</li>
    673       </ul>
    674       <p id="rfc.section.2.1.p.3">Values to be added to this name space require IETF Review (see <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>).
    675       </p>
    676       <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
     664</pre><p id="rfc.section.2.p.3">The only range unit defined by HTTP/1.1 is "bytes" (<a href="#byte.ranges" title="Byte Ranges">Section&nbsp;5.4.1</a>). Additional units can be defined as described in <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;6.1</a>.
    677665      </p>
    678666      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1>
    … …  
    929917      </p>
    930918      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    931       <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
    932       <p id="rfc.section.6.1.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
    933       </p>
     919      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="range.unit.registry" href="#range.unit.registry">Range Unit Registry</a></h2>
     920      <p id="rfc.section.6.1.p.1">The HTTP Range Unit Registry defines the name space for the range unit names and refers to their corresponding specifications.
     921         The registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt;.
     922      </p>
     923      <h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="range.unit.registry.procedure" href="#range.unit.registry.procedure">Procedure</a></h3>
     924      <p id="rfc.section.6.1.1.p.1">Registration of an HTTP Range Unit <em class="bcp14">MUST</em> include the following fields:
     925      </p>
     926      <ul>
     927         <li>Name</li>
     928         <li>Description</li>
     929         <li>Pointer to specification text</li>
     930      </ul>
     931      <p id="rfc.section.6.1.1.p.2">Values to be added to this name space require IETF Review (see <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>).
     932      </p>
     933      <h3 id="rfc.section.6.1.2"><a href="#rfc.section.6.1.2">6.1.2</a>&nbsp;<a id="range.unit.registration" href="#range.unit.registration">Registrations</a></h3>
     934      <p id="rfc.section.6.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p>
    934935      <div id="rfc.table.1">
     936         <div id="iana.range.units.table"></div>
     937         <table class="tt full left" cellpadding="3" cellspacing="0">
     938            <thead>
     939               <tr>
     940                  <th>Range Specifier Name</th>
     941                  <th>Description</th>
     942                  <th>Reference</th>
     943               </tr>
     944            </thead>
     945            <tbody>
     946               <tr>
     947                  <td class="left">bytes</td>
     948                  <td class="left">a range of octets</td>
     949                  <td class="left"><a href="#range.units" title="Range Units">Section&nbsp;2</a></td>
     950               </tr>
     951               <tr>
     952                  <td class="left">none</td>
     953                  <td class="left">reserved as keyword, indicating no ranges are supported</td>
     954                  <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a></td>
     955               </tr>
     956            </tbody>
     957         </table>
     958      </div>
     959      <p id="rfc.section.6.1.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     960      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
     961      <p id="rfc.section.6.2.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
     962      </p>
     963      <div id="rfc.table.2">
    935964         <div id="iana.status.code.registration.table"></div>
    936965         <table class="tt full left" cellpadding="3" cellspacing="0">
    … …  
    958987         </table>
    959988      </div>
    960       <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
    961       <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
    962       </p>
    963       <div id="rfc.table.2">
     989      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
     990      <p id="rfc.section.6.3.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; shall be updated with the permanent registrations below (see <a href="#BCP90" id="rfc.xref.BCP90.1"><cite title="Registration Procedures for Message Header Fields">[BCP90]</cite></a>):
     991      </p>
     992      <div id="rfc.table.3">
    964993         <div id="iana.header.registration.table"></div>
    965994         <table class="tt full left" cellpadding="3" cellspacing="0">
    … …  
    9771006                  <td class="left">http</td>
    9781007                  <td class="left">standard</td>
    979                   <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.1" title="Accept-Ranges">Section&nbsp;5.1</a>
     1008                  <td class="left"> <a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;5.1</a>
    9801009                  </td>
    9811010               </tr>
    … …  
    10041033         </table>
    10051034      </div>
    1006       <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    1007       <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="range.specifier.registration" href="#range.specifier.registration">Range Specifier Registration</a></h2>
    1008       <p id="rfc.section.6.3.p.1">The registration procedure for HTTP Range Specifiers is defined by <a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;2.1</a> of this document.
    1009       </p>
    1010       <p id="rfc.section.6.3.p.2">The HTTP Range Specifier Registry shall be created at &lt;<a href="http://www.iana.org/assignments/http-range-specifiers">http://www.iana.org/assignments/http-range-specifiers</a>&gt; and be populated with the registrations below:
    1011       </p>
    1012       <div id="rfc.table.3">
    1013          <div id="iana.range.specifiers.table"></div>
    1014          <table class="tt full left" cellpadding="3" cellspacing="0">
    1015             <thead>
    1016                <tr>
    1017                   <th>Range Specifier Name</th>
    1018                   <th>Description</th>
    1019                   <th>Reference</th>
    1020                </tr>
    1021             </thead>
    1022             <tbody>
    1023                <tr>
    1024                   <td class="left">bytes</td>
    1025                   <td class="left">a range of octets</td>
    1026                   <td class="left"><a href="#range.units" title="Range Units">Section&nbsp;2</a></td>
    1027                </tr>
    1028                <tr>
    1029                   <td class="left">none</td>
    1030                   <td class="left">reserved as keyword, indicating no ranges are supported</td>
    1031                   <td class="left"><a href="#header.accept-ranges" id="rfc.xref.header.accept-ranges.2" title="Accept-Ranges">Section&nbsp;5.1</a></td>
    1032                </tr>
    1033             </tbody>
    1034          </table>
    1035       </div>
    1036       <p id="rfc.section.6.3.p.3">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
     1035      <p id="rfc.section.6.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    10371036      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    10381037      <p id="rfc.section.7.p.1">This section is meant to inform developers, information providers, and users of known security concerns specific to the HTTP/1.1
    … …  
    12311230      <p id="rfc.section.B.p.4">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
    12321231      </p>
    1233       <p id="rfc.section.B.p.5">This specification introduces a Range Specifier Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;2.1</a>)
     1232      <p id="rfc.section.B.p.5">This specification introduces a Range Specifier Registry. (<a href="#range.unit.registry" title="Range Unit Registry">Section&nbsp;6.1</a>)
    12341233      </p>
    12351234      <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="imported.abnf" href="#imported.abnf">Imported ABNF</a></h1>
    … …  
    13261325         <ul class="ind">
    13271326            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    1328                   <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.1</a>, <a href="#rfc.xref.status.206.2">B</a></li>
     1327                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.1</b></a>, <a href="#rfc.xref.status.206.1">6.2</a>, <a href="#rfc.xref.status.206.2">B</a></li>
    13291328               </ul>
    13301329            </li>
    13311330            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    1332                   <li>416 Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.1</a></li>
     1331                  <li>416 Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>3.2</b></a>, <a href="#rfc.xref.status.416.1">6.2</a></li>
    13331332               </ul>
    13341333            </li>
    13351334            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
    1336                   <li>Accept-Ranges header field&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.2</a>, <a href="#rfc.xref.header.accept-ranges.2">6.3</a></li>
     1335                  <li>Accept-Ranges header field&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>5.1</b></a>, <a href="#rfc.xref.header.accept-ranges.1">6.1.2</a>, <a href="#rfc.xref.header.accept-ranges.2">6.3</a></li>
    13371336               </ul>
    13381337            </li>
    13391338            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
    13401339                  <li><em>BCP13</em>&nbsp;&nbsp;<a href="#BCP13"><b>9.2</b></a>, <a href="#rfc.xref.BCP13.1">A</a></li>
    1341                   <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">6.2</a>, <a href="#BCP90"><b>9.2</b></a></li>
     1340                  <li><em>BCP90</em>&nbsp;&nbsp;<a href="#rfc.xref.BCP90.1">6.3</a>, <a href="#BCP90"><b>9.2</b></a></li>
    13421341               </ul>
    13431342            </li>
    13441343            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
    1345                   <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.2</a>, <a href="#rfc.xref.header.content-range.5">B</a></li>
     1344                  <li>Content-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.content-range.1">2</a>, <a href="#rfc.xref.header.content-range.2">3.1</a>, <a href="#rfc.xref.header.content-range.3">3.2</a>, <a href="#rfc.iref.c.1"><b>5.2</b></a>, <a href="#rfc.xref.header.content-range.4">6.3</a>, <a href="#rfc.xref.header.content-range.5">B</a></li>
    13461345               </ul>
    13471346            </li>
    … …  
    13771376            </li>
    13781377            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
    1379                   <li>If-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.2</a></li>
     1378                  <li>If-Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.if-range.1">3.1</a>, <a href="#rfc.xref.header.if-range.2">3.2</a>, <a href="#rfc.iref.i.1"><b>5.3</b></a>, <a href="#rfc.xref.header.if-range.3">5.4.2</a>, <a href="#rfc.xref.header.if-range.4">6.3</a></li>
    13801379               </ul>
    13811380            </li>
    … …  
    14161415            </li>
    14171416            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
    1418                   <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">3.1</a>, <a href="#rfc.xref.header.range.3">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.4">6.2</a></li>
     1417                  <li>Range header field&nbsp;&nbsp;<a href="#rfc.xref.header.range.1">2</a>, <a href="#rfc.xref.header.range.2">3.1</a>, <a href="#rfc.xref.header.range.3">3.2</a>, <a href="#rfc.iref.r.1"><b>5.4</b></a>, <a href="#rfc.xref.header.range.4">6.3</a></li>
    14191418                  <li><em>RFC2046</em>&nbsp;&nbsp;<a href="#RFC2046"><b>9.1</b></a>, <a href="#rfc.xref.RFC2046.1">A</a>, <a href="#rfc.xref.RFC2046.2">A</a><ul>
    14201419                        <li><em>Section 5.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2046.1">A</a></li>
    … …  
    14231422                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li>
    14241423                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#RFC2616"><b>9.2</b></a></li>
    1425                   <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
    1426                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
     1424                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">6.1.1</a>, <a href="#RFC5226"><b>9.2</b></a><ul>
     1425                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">6.1.1</a></li>
    14271426                     </ul>
    14281427                  </li>

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

    r2138 r2139  
    205205</t>
    206206
    207 <section title="Range Unit Registry" anchor="range.unit.registry">
    208 <t>
    209    The HTTP Range Unit Registry defines the name space for the range
    210    unit names and refers to their corresponding specifications.
    211 </t>
    212 <t>
    213    Registrations &MUST; include the following fields:
    214    <list style="symbols">
    215      <t>Name</t>
    216      <t>Description</t>
    217      <t>Pointer to specification text</t>
    218    </list>
    219 </t>
    220 <t>
    221   Values to be added to this name space require IETF Review
    222   (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
    223 </t>
    224 <t>
    225    The registry itself is maintained at
    226    <eref target="http://www.iana.org/assignments/http-range-specifiers"/>.
    227 </t>
    228 </section>
    229 
    230207</section>
    231208
    … …  
    820797
    821798<section title="IANA Considerations" anchor="IANA.considerations">
     799
     800<section title="Range Unit Registry" anchor="range.unit.registry">
     801<t>
     802   The HTTP Range Unit Registry defines the name space for the range
     803   unit names and refers to their corresponding specifications.
     804   The registry is maintained at
     805   <eref target="http://www.iana.org/assignments/http-range-specifiers"/>.
     806</t>
     807
     808<section title="Procedure" anchor="range.unit.registry.procedure">
     809<t>
     810   Registration of an HTTP Range Unit &MUST; include the following fields:
     811   <list style="symbols">
     812     <t>Name</t>
     813     <t>Description</t>
     814     <t>Pointer to specification text</t>
     815   </list>
     816</t>
     817<t>
     818  Values to be added to this name space require IETF Review
     819  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
     820</t>
     821</section>
     822
     823<section title="Registrations" anchor="range.unit.registration">
     824<t>
     825   The initial HTTP Range Unit Registry shall contain the registrations
     826   below:
     827</t>
     828<texttable align="left" suppress-title="true" anchor="iana.range.units.table">
     829   <ttcol>Range Specifier Name</ttcol>
     830   <ttcol>Description</ttcol>
     831   <ttcol>Reference</ttcol>
     832
     833   <c>bytes</c>
     834   <c>a range of octets</c>
     835   <c><xref target="range.units"/></c>
     836
     837   <c>none</c>
     838   <c>reserved as keyword, indicating no ranges are supported</c>
     839   <c><xref target="header.accept-ranges"/></c>
     840</texttable>
     841<t>
     842   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
     843</t>
     844</section>
     845</section>
    822846
    823847<section title="Status Code Registration" anchor="status.code.registration">
    … …  
    892916</section>
    893917
    894 <section title="Range Specifier Registration" anchor="range.specifier.registration">
    895 <t>
    896   The registration procedure for HTTP Range Specifiers is defined by
    897   <xref target="range.unit.registry"/> of this document.
    898 </t>
    899 <t>
    900    The HTTP Range Specifier Registry shall be created at <eref target="http://www.iana.org/assignments/http-range-specifiers"/>
    901    and be populated with the registrations below:
    902 </t>
    903 <texttable align="left" suppress-title="true" anchor="iana.range.specifiers.table">
    904    <ttcol>Range Specifier Name</ttcol>
    905    <ttcol>Description</ttcol>
    906    <ttcol>Reference</ttcol>
    907 
    908    <c>bytes</c>
    909    <c>a range of octets</c>
    910    <c><xref target="range.units"/></c>
    911 
    912    <c>none</c>
    913    <c>reserved as keyword, indicating no ranges are supported</c>
    914    <c><xref target="header.accept-ranges"/></c>
    915 </texttable>
    916 <t>
    917    The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
    918 </t>
    919 </section>
    920918</section>
    921919
Note: See TracChangeset for help on using the changeset viewer.