Ignore:
Timestamp:
Jul 9, 2012, 11:04:50 AM (7 years ago)
Author:
julian.reschke@…
Message:

Minor fine-tuning of multipart/byteranges IANA registration template.

File:
1 edited

Legend:

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

    r1748 r1749  
    12641264   "multipart/byteranges".  The following is to be registered with IANA <xref target="RFC4288"/>.
    12651265</t>
    1266 <x:note>
    1267   <t>
    1268     &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
    1269   </t>
    1270 </x:note>
    12711266<t>
    12721267   The multipart/byteranges media type includes one or more parts, each
     
    13021297    </t>
    13031298    <t hangText="Applications that use this media type:">
     1299      HTTP components supporting multiple ranges in a single request.
    13041300    </t>
    13051301    <t hangText="Additional information:">
     
    13241320  </list>
    13251321</t>
     1322<x:note>
     1323  <t>
     1324    &Note; Despite the name "multipart/byteranges" is not limited to the byte ranges only.
     1325  </t>
     1326</x:note>
    13261327<figure><preamble>
    13271328   For example:
     
    13451346</artwork></figure>
    13461347<figure><preamble>
    1347    Other example:
     1348   Another example, using the "exampleunit" range unit:
    13481349</preamble>
    13491350<artwork type="example">
     
    13671368</figure>
    13681369<t>
    1369       Notes:
     1370  Notes:
    13701371  <list style="numbers">
    13711372      <t>Additional CRLFs &MAY; precede the first boundary string in the body.</t>
Note: See TracChangeset for help on using the changeset viewer.