Changeset 2687 for draft-ietf-httpbis


Ignore:
Timestamp:
20/05/14 16:09:54 (6 years ago)
Author:
julian.reschke@…
Message:

editorial fixes (#553)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/auth48/p5-range.unpg.txt

    r2676 r2687  
    66Obsoletes: 2616 (if approved)                              Y. Lafon, Ed.
    77Intended status: Standards Track                                     W3C
    8 Expires: November 16, 2014                               J. Reschke, Ed.
     8Expires: November 21, 2014                               J. Reschke, Ed.
    99                                                              greenbytes
    10                                                             May 15, 2014
     10                                                            May 20, 2014
    1111
    1212
     
    5353
    5454
    55 Fielding, et al.        Expires November 16, 2014               [Page 1]
    56 
    57 
    58 Internet-Draft           HTTP/1.1 Range Requests                May 2014
    59 
    60 
    61    This Internet-Draft will expire on November 16, 2014.
     55Fielding, et al.        Expires November 21, 2014               [Page 1]
     56
     57
     58Internet-Draft           HTTP/1.1 Range Requests                May 2014
     59
     60
     61   This Internet-Draft will expire on November 21, 2014.
    6262
    6363Copyright Notice
     
    110110
    111111
    112 Fielding, et al.        Expires November 16, 2014               [Page 2]
     112Fielding, et al.        Expires November 21, 2014               [Page 2]
    113113
    114114
     
    167167
    168168
    169 Fielding, et al.        Expires November 16, 2014               [Page 3]
     169Fielding, et al.        Expires November 21, 2014               [Page 3]
    170170
    171171
     
    224224
    225225
    226 Fielding, et al.        Expires November 16, 2014               [Page 4]
     226Fielding, et al.        Expires November 21, 2014               [Page 4]
    227227
    228228
     
    249249     bytes-unit       = "bytes"
    250250
    251    A byte range request can specify a single range of bytes, or a set of
     251   A byte-range request can specify a single range of bytes or a set of
    252252   ranges within a single representation.
    253253
     
    281281
    282282
    283 Fielding, et al.        Expires November 16, 2014               [Page 5]
     283Fielding, et al.        Expires November 21, 2014               [Page 5]
    284284
    285285
     
    328328   Otherwise, the byte-range-set is unsatisfiable.
    329329
    330    In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-
     330   In the byte-range syntax, first-byte-pos, last-byte-pos, and suffix-
    331331   length are expressed as decimal number of octets.  Since there is no
    332332   predefined limit to the length of a payload, recipients MUST
     
    338338
    339339
    340 Fielding, et al.        Expires November 16, 2014               [Page 6]
     340Fielding, et al.        Expires November 21, 2014               [Page 6]
    341341
    342342
     
    395395
    396396
    397 Fielding, et al.        Expires November 16, 2014               [Page 7]
     397Fielding, et al.        Expires November 21, 2014               [Page 7]
    398398
    399399
     
    452452
    453453
    454 Fielding, et al.        Expires November 16, 2014               [Page 8]
     454Fielding, et al.        Expires November 21, 2014               [Page 8]
    455455
    456456
     
    469469
    470470   The "If-Range" header field allows a client to "short-circuit" the
    471    second request.  Informally, its meaning is: if the representation is
    472    unchanged, send me the part(s) that I am requesting in Range;
    473    otherwise, send me the entire representation.
     471   second request.  Informally, its meaning is as follows: if the
     472   representation is unchanged, send me the part(s) that I am requesting
     473   in Range; otherwise, send me the entire representation.
    474474
    475475     If-Range = entity-tag / HTTP-date
     
    509509
    510510
    511 Fielding, et al.        Expires November 16, 2014               [Page 9]
     511Fielding, et al.        Expires November 21, 2014               [Page 9]
    512512
    513513
     
    543543   defined in Appendix A, and a Content-Type header field containing the
    544544   multipart/byteranges media type and its required boundary parameter.
    545    To avoid confusion with single part responses, a server MUST NOT
     545   To avoid confusion with single-part responses, a server MUST NOT
    546546   generate a Content-Range header field in the HTTP header section of a
    547547   multiple part response (this field will be sent in each part
     
    566566
    567567
    568 Fielding, et al.        Expires November 16, 2014              [Page 10]
     568Fielding, et al.        Expires November 21, 2014              [Page 10]
    569569
    570570
     
    623623
    624624
    625 Fielding, et al.        Expires November 16, 2014              [Page 11]
     625Fielding, et al.        Expires November 21, 2014              [Page 11]
    626626
    627627
     
    680680
    681681
    682 Fielding, et al.        Expires November 16, 2014              [Page 12]
     682Fielding, et al.        Expires November 21, 2014              [Page 12]
    683683
    684684
     
    710710   representation.
    711711
    712    A server generating a 416 (Range Not Satisfiable) response to a byte
     712   A server generating a 416 (Range Not Satisfiable) response to a byte-
    713713   range request SHOULD send a Content-Range header field with an
    714714   unsatisfied-range value, as in the following example:
     
    737737
    738738
    739 Fielding, et al.        Expires November 16, 2014              [Page 13]
     739Fielding, et al.        Expires November 21, 2014              [Page 13]
    740740
    741741
     
    794794
    795795
    796 Fielding, et al.        Expires November 16, 2014              [Page 14]
     796Fielding, et al.        Expires November 21, 2014              [Page 14]
    797797
    798798
     
    811811   first-byte-pos of all of the byte-range-spec values were greater than
    812812   the current length of the selected representation.  When this status
    813    code is generated in response to a byte range request, the sender
     813   code is generated in response to a byte-range request, the sender
    814814   SHOULD generate a Content-Range header field specifying the current
    815815   length of the selected representation (Section 4.2).
     
    8358355.1.  Range Unit Registry
    836836
    837    The HTTP Range Unit Registry defines the namespace for the range unit
    838    names and refers to their corresponding specifications.  The registry
    839    will be created and maintained at (the suggested URI)
     837   The "HTTP Range Unit Registry" defines the namespace for the range
     838   unit names and refers to their corresponding specifications.  The
     839   registry will be created and maintained at (the suggested URI)
    840840   <http://www.iana.org/assignments/http-parameters>.
    841841
     
    851851
    852852
    853 Fielding, et al.        Expires November 16, 2014              [Page 15]
     853Fielding, et al.        Expires November 21, 2014              [Page 15]
    854854
    855855
     
    8648645.1.2.  Registrations
    865865
    866    The initial HTTP Range Unit Registry shall contain the registrations
    867    below:
     866   The initial range unit registry contains the registrations below:
    868867
    869868   +-------------+---------------------------------------+-------------+
     
    883882   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located
    884883   at <http://www.iana.org/assignments/http-status-codes> has been
    885    updated with the registrations below:
     884   updated to include the registrations below:
    886885
    887886   +-------+-----------------------+-------------+
     
    896895   HTTP header fields are registered within the "Message Headers"
    897896   registry maintained at
    898    <http://www.iana.org/assignments/message-headers/>.
     897   <http://www.iana.org/assignments/message-headers>.
    899898
    900899   This document defines the following HTTP header fields, so the
     
    908907
    909908
    910 Fielding, et al.        Expires November 16, 2014              [Page 16]
     909
     910Fielding, et al.        Expires November 21, 2014              [Page 16]
    911911
    912912
     
    932932
    933933   This document serves as the specification for the Internet media type
    934    "multipart/byteranges".  The following is to be registered with IANA.
     934   "multipart/byteranges".  The following has been registered with IANA.
    935935
    9369365.4.1.  Internet Media Type multipart/byteranges
     
    965965
    966966
    967 Fielding, et al.        Expires November 16, 2014              [Page 17]
     967Fielding, et al.        Expires November 21, 2014              [Page 17]
    968968
    969969
     
    10221022
    10231023
    1024 Fielding, et al.        Expires November 16, 2014              [Page 18]
     1024Fielding, et al.        Expires November 21, 2014              [Page 18]
    10251025
    10261026
     
    10791079
    10801080
    1081 Fielding, et al.        Expires November 16, 2014              [Page 19]
     1081Fielding, et al.        Expires November 21, 2014              [Page 19]
    10821082
    10831083
     
    11361136
    11371137
    1138 Fielding, et al.        Expires November 16, 2014              [Page 20]
     1138Fielding, et al.        Expires November 21, 2014              [Page 20]
    11391139
    11401140
     
    11931193
    11941194
    1195 Fielding, et al.        Expires November 16, 2014              [Page 21]
     1195Fielding, et al.        Expires November 21, 2014              [Page 21]
    11961196
    11971197
     
    12501250
    12511251
    1252 Fielding, et al.        Expires November 16, 2014              [Page 22]
     1252Fielding, et al.        Expires November 21, 2014              [Page 22]
    12531253
    12541254
     
    13071307
    13081308
    1309 Fielding, et al.        Expires November 16, 2014              [Page 23]
     1309Fielding, et al.        Expires November 21, 2014              [Page 23]
    13101310
    13111311
     
    13641364
    13651365
    1366 Fielding, et al.        Expires November 16, 2014              [Page 24]
    1367 
    1368 
     1366Fielding, et al.        Expires November 21, 2014              [Page 24]
     1367
     1368
  • draft-ietf-httpbis/latest/auth48/rfc7233.abdiff.txt

    r2676 r2687  
    77 Obsoletes: 2616 (if approved)                              Y. Lafon, Ed.
    88 Intended status: Standards Track                                     W3C
    9  Expires: November 16, 2014                               J. Reschke, Ed.
     9 Expires: November 21, 2014                               J. Reschke, Ed.
    1010                                                               greenbytes
    11                                                              May 15, 2014
     11                                                             May 20, 2014
    1212
    1313NEW:
     
    9292    time.  It is inappropriate to use Internet-Drafts as reference
    9393    material or to cite them other than as "work in progress."
    94     This Internet-Draft will expire on November 16, 2014.
     94    This Internet-Draft will expire on November 21, 2014.
    9595
    9696NEW:
     
    201201
    202202
    203 Section 2.1., paragraph 3:
    204 OLD:
    205 
    206     A byte range request can specify a single range of bytes, or a set of
    207     ranges within a single representation.
    208 
    209 NEW:
    210 
    211     A byte-range request can specify a single range of bytes or a set of
    212     ranges within a single representation.
    213 
    214 
    215 Section 2.1., paragraph 26:
    216 OLD:
    217 
    218     In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-
    219     length are expressed as decimal number of octets.  Since there is no
    220     predefined limit to the length of a payload, recipients MUST
    221     anticipate potentially large decimal numerals and prevent parsing
    222     errors due to integer conversion overflows.
    223 
    224 NEW:
    225 
    226     In the byte-range syntax, first-byte-pos, last-byte-pos, and suffix-
    227     length are expressed as decimal number of octets.  Since there is no
    228     predefined limit to the length of a payload, recipients MUST
    229     anticipate potentially large decimal numerals and prevent parsing
    230     errors due to integer conversion overflows.
    231 
    232 
    233 Section 3.2., paragraph 2:
    234 OLD:
    235 
    236     The "If-Range" header field allows a client to "short-circuit" the
    237     second request.  Informally, its meaning is: if the representation is
    238     unchanged, send me the part(s) that I am requesting in Range;
    239     otherwise, send me the entire representation.
    240 
    241 NEW:
    242 
    243     The "If-Range" header field allows a client to "short-circuit" the
    244     second request.  Informally, its meaning is as follows: if the
    245     representation is unchanged, send me the part(s) that I am requesting
    246     in Range; otherwise, send me the entire representation.
    247 
    248 
    249203Section 3.2., paragraph 4:
    250204OLD:
     
    291245
    292246
    293 Section 206, paragraph 0:
    294 OLD:
    295 
    296     If multiple parts are being transferred, the server generating the
    297     206 response MUST generate a "multipart/byteranges" payload, as
    298     defined in Appendix A, and a Content-Type header field containing the
    299     multipart/byteranges media type and its required boundary parameter.
    300     To avoid confusion with single part responses, a server MUST NOT
    301     generate a Content-Range header field in the HTTP header section of a
    302     multiple part response (this field will be sent in each part
    303     instead).
    304 
    305 NEW:
    306 
    307     If multiple parts are being transferred, the server generating the
    308     206 response MUST generate a "multipart/byteranges" payload, as
    309     defined in Appendix A, and a Content-Type header field containing the
    310     multipart/byteranges media type and its required boundary parameter.
    311     To avoid confusion with single-part responses, a server MUST NOT
    312     generate a Content-Range header field in the HTTP header section of a
    313     multiple part response (this field will be sent in each part
    314     instead).
    315 
    316 
    317 Section 4.2., paragraph 14:
    318 OLD:
    319 
    320     A server generating a 416 (Range Not Satisfiable) response to a byte
    321     range request SHOULD send a Content-Range header field with an
    322     unsatisfied-range value, as in the following example:
    323 
    324 NEW:
    325 
    326     A server generating a 416 (Range Not Satisfiable) response to a byte-
    327     range request SHOULD send a Content-Range header field with an
    328     unsatisfied-range value, as in the following example:
    329 
    330 
    331247Section 4.2., paragraph 17:
    332248OLD:
     
    359275
    360276
    361 Section 4.4., paragraph 2:
    362 OLD:
    363 
    364     For byte ranges, failing to overlap the current extent means that the
    365     first-byte-pos of all of the byte-range-spec values were greater than
    366     the current length of the selected representation.  When this status
    367     code is generated in response to a byte range request, the sender
    368     SHOULD generate a Content-Range header field specifying the current
    369     length of the selected representation (Section 4.2).
    370 
    371 NEW:
    372 
    373     For byte ranges, failing to overlap the current extent means that the
    374     first-byte-pos of all of the byte-range-spec values were greater than
    375     the current length of the selected representation.  When this status
    376     code is generated in response to a byte-range request, the sender
    377     SHOULD generate a Content-Range header field specifying the current
    378     length of the selected representation (Section 4.2).
    379 
    380 
    381277Section 5.1., paragraph 1:
    382278OLD:
    383279
    384     The HTTP Range Unit Registry defines the namespace for the range unit
    385     names and refers to their corresponding specifications.  The registry
    386     will be created and maintained at (the suggested URI)
     280    The "HTTP Range Unit Registry" defines the namespace for the range
     281    unit names and refers to their corresponding specifications.  The
     282    registry will be created and maintained at (the suggested URI)
    387283    <http://www.iana.org/assignments/http-parameters>.
    388284
     
    398294OLD:
    399295
    400     The initial HTTP Range Unit Registry shall contain the registrations
    401     below:
     296    The initial range unit registry contains the registrations below:
    402297
    403298NEW:
     
    405300    The initial "HTTP Range Unit Registry" contains the registrations
    406301    below:
    407 
    408 
    409 Section 5.2., paragraph 1:
    410 OLD:
    411 
    412     The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located
    413     at <http://www.iana.org/assignments/http-status-codes> has been
    414     updated with the registrations below:
    415 
    416 NEW:
    417 
    418     The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located
    419     at <http://www.iana.org/assignments/http-status-codes> has been
    420     updated to include the registrations below:
    421 
    422 
    423 Section 5.3., paragraph 1:
    424 OLD:
    425 
    426     HTTP header fields are registered within the "Message Headers"
    427     registry maintained at
    428     <http://www.iana.org/assignments/message-headers/>.
    429 
    430 NEW:
    431 
    432     HTTP header fields are registered within the "Message Headers"
    433     registry maintained at
    434     <http://www.iana.org/assignments/message-headers>.
    435302
    436303
     
    447314    associated registry entries have been updated according to the
    448315    permanent registrations below (see [BCP90]):
    449 
    450 
    451 Section 5.4., paragraph 2:
    452 OLD:
    453 
    454     This document serves as the specification for the Internet media type
    455     "multipart/byteranges".  The following is to be registered with IANA.
    456 
    457 NEW:
    458 
    459     This document serves as the specification for the Internet media type
    460     "multipart/byteranges".  The following has been registered with IANA.
    461316
    462317
  • draft-ietf-httpbis/latest/auth48/rfc7233.diff.html

    r2678 r2687  
    4343      <tr><td class="lineno" valign="top"></td><td class="lblock">Obsoletes: 2616 <span class="delete">(if approved)</span>                              Y. Lafon, Ed.</td><td> </td><td class="rblock">Obsoletes: 2616                                            Y. Lafon, Ed.</td><td class="lineno" valign="top"></td></tr>
    4444      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Intended status:</span> Standards Track                                     W3C</td><td> </td><td class="rblock"><span class="insert">Category:</span> Standards Track                                            W3C</td><td class="lineno" valign="top"></td></tr>
    45       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 16, 2014</span>                               J. Reschke, Ed.</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span>                                          J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
     45      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">Expires: November 21, 2014</span>                               J. Reschke, Ed.</td><td> </td><td class="rblock"><span class="insert">ISSN: 2070-1721</span>                                          J. Reschke, Ed.</td><td class="lineno" valign="top"></td></tr>
    4646      <tr><td class="lineno" valign="top"></td><td class="left">                                                              greenbytes</td><td> </td><td class="right">                                                              greenbytes</td><td class="lineno" valign="top"></td></tr>
    4747      <tr><td><a name="diff0002" /></td></tr>
    48       <tr><td class="lineno" valign="top"></td><td class="lblock">                                                            <span class="delete">May 15,</span> 2014</td><td> </td><td class="rblock">                                                            <span class="insert">    May</span> 2014</td><td class="lineno" valign="top"></td></tr>
     48      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                            <span class="delete">May 20,</span> 2014</td><td> </td><td class="rblock">                                                            <span class="insert">    May</span> 2014</td><td class="lineno" valign="top"></td></tr>
    4949      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    5050      <tr><td class="lineno" valign="top"></td><td class="left">         Hypertext Transfer Protocol (HTTP/1.1): Range Requests</td><td> </td><td class="right">         Hypertext Transfer Protocol (HTTP/1.1): Range Requests</td><td class="lineno" valign="top"></td></tr>
     
    9292      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   time.  It is inappropriate to use Internet-Drafts as reference</span></td><td> </td><td class="rblock">   <span class="insert">http://www.rfc-editor.org/info/rfc7233.</span></td><td class="lineno" valign="top"></td></tr>
    9393      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   material or to cite them other than as "work in progress."</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    94       <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This Internet-Draft will expire on November 16, 2014.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     94      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   This Internet-Draft will expire on November 21, 2014.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    9595      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    9696      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
     
    181181      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
    182182      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    183       <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 5, line 23</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 4, line 23</em></th><td></td></tr>
    184       <tr><td class="lineno" valign="top"></td><td class="left">2.1.  Byte Ranges</td><td> </td><td class="right">2.1.  Byte Ranges</td><td class="lineno" valign="top"></td></tr>
    185       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    186       <tr><td class="lineno" valign="top"></td><td class="left">   Since representation data is transferred in payloads as a sequence of</td><td> </td><td class="right">   Since representation data is transferred in payloads as a sequence of</td><td class="lineno" valign="top"></td></tr>
    187       <tr><td class="lineno" valign="top"></td><td class="left">   octets, a byte range is a meaningful substructure for any</td><td> </td><td class="right">   octets, a byte range is a meaningful substructure for any</td><td class="lineno" valign="top"></td></tr>
    188       <tr><td class="lineno" valign="top"></td><td class="left">   representation transferable over HTTP (Section 3 of [RFC7231]).  The</td><td> </td><td class="right">   representation transferable over HTTP (Section 3 of [RFC7231]).  The</td><td class="lineno" valign="top"></td></tr>
    189       <tr><td class="lineno" valign="top"></td><td class="left">   "bytes" range unit is defined for expressing subranges of the data's</td><td> </td><td class="right">   "bytes" range unit is defined for expressing subranges of the data's</td><td class="lineno" valign="top"></td></tr>
    190       <tr><td class="lineno" valign="top"></td><td class="left">   octet sequence.</td><td> </td><td class="right">   octet sequence.</td><td class="lineno" valign="top"></td></tr>
    191       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    192       <tr><td class="lineno" valign="top"></td><td class="left">     bytes-unit       = "bytes"</td><td> </td><td class="right">     bytes-unit       = "bytes"</td><td class="lineno" valign="top"></td></tr>
    193       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     183      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 9, line 23</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 8, line 23</em></th><td></td></tr>
     184      <tr><td class="lineno" valign="top"></td><td class="left">   representation.</td><td> </td><td class="right">   representation.</td><td class="lineno" valign="top"></td></tr>
     185      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     186      <tr><td class="lineno" valign="top"></td><td class="left">   The "If-Range" header field allows a client to "short-circuit" the</td><td> </td><td class="right">   The "If-Range" header field allows a client to "short-circuit" the</td><td class="lineno" valign="top"></td></tr>
     187      <tr><td class="lineno" valign="top"></td><td class="left">   second request.  Informally, its meaning is as follows: if the</td><td> </td><td class="right">   second request.  Informally, its meaning is as follows: if the</td><td class="lineno" valign="top"></td></tr>
     188      <tr><td class="lineno" valign="top"></td><td class="left">   representation is unchanged, send me the part(s) that I am requesting</td><td> </td><td class="right">   representation is unchanged, send me the part(s) that I am requesting</td><td class="lineno" valign="top"></td></tr>
     189      <tr><td class="lineno" valign="top"></td><td class="left">   in Range; otherwise, send me the entire representation.</td><td> </td><td class="right">   in Range; otherwise, send me the entire representation.</td><td class="lineno" valign="top"></td></tr>
     190      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     191      <tr><td class="lineno" valign="top"></td><td class="left">     If-Range = entity-tag / HTTP-date</td><td> </td><td class="right">     If-Range = entity-tag / HTTP-date</td><td class="lineno" valign="top"></td></tr>
     192      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     193      <tr><td class="lineno" valign="top"></td><td class="left">   A client MUST NOT generate an If-Range header field in a request that</td><td> </td><td class="right">   A client MUST NOT generate an If-Range header field in a request that</td><td class="lineno" valign="top"></td></tr>
    194194      <tr><td><a name="diff0010" /></td></tr>
    195       <tr><td class="lineno" valign="top"></td><td class="lblock">   A byte<span class="delete"> range request can specify a single range of bytes,</span> or a set of</td><td> </td><td class="rblock">   A byte<span class="insert">-range request can specify a single range of bytes</span> or a set of</td><td class="lineno" valign="top"></td></tr>
    196       <tr><td class="lineno" valign="top"></td><td class="left">   ranges within a single representation.</td><td> </td><td class="right">   ranges within a single representation.</td><td class="lineno" valign="top"></td></tr>
    197       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    198       <tr><td class="lineno" valign="top"></td><td class="left">     byte-ranges-specifier = bytes-unit "=" byte-range-set</td><td> </td><td class="right">     byte-ranges-specifier = bytes-unit "=" byte-range-set</td><td class="lineno" valign="top"></td></tr>
    199       <tr><td class="lineno" valign="top"></td><td class="left">     byte-range-set  = 1#( byte-range-spec / suffix-byte-range-spec )</td><td> </td><td class="right">     byte-range-set  = 1#( byte-range-spec / suffix-byte-range-spec )</td><td class="lineno" valign="top"></td></tr>
    200       <tr><td class="lineno" valign="top"></td><td class="left">     byte-range-spec = first-byte-pos "-" [ last-byte-pos ]</td><td> </td><td class="right">     byte-range-spec = first-byte-pos "-" [ last-byte-pos ]</td><td class="lineno" valign="top"></td></tr>
    201       <tr><td class="lineno" valign="top"></td><td class="left">     first-byte-pos  = 1*DIGIT</td><td> </td><td class="right">     first-byte-pos  = 1*DIGIT</td><td class="lineno" valign="top"></td></tr>
    202       <tr><td class="lineno" valign="top"></td><td class="left">     last-byte-pos   = 1*DIGIT</td><td> </td><td class="right">     last-byte-pos   = 1*DIGIT</td><td class="lineno" valign="top"></td></tr>
    203       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    204       <tr><td class="lineno" valign="top"></td><td class="left">   The first-byte-pos value in a byte-range-spec gives the byte-offset</td><td> </td><td class="right">   The first-byte-pos value in a byte-range-spec gives the byte-offset</td><td class="lineno" valign="top"></td></tr>
    205       <tr><td class="lineno" valign="top"></td><td class="left">   of the first byte in a range.  The last-byte-pos value gives the</td><td> </td><td class="right">   of the first byte in a range.  The last-byte-pos value gives the</td><td class="lineno" valign="top"></td></tr>
    206       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    207       <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 6, line 45</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 5, line 45</em></th><td></td></tr>
    208       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    209       <tr><td class="lineno" valign="top"></td><td class="left">        bytes=500-600,601-999</td><td> </td><td class="right">        bytes=500-600,601-999</td><td class="lineno" valign="top"></td></tr>
    210       <tr><td class="lineno" valign="top"></td><td class="left">        bytes=500-700,601-999</td><td> </td><td class="right">        bytes=500-700,601-999</td><td class="lineno" valign="top"></td></tr>
    211       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    212       <tr><td class="lineno" valign="top"></td><td class="left">   If a valid byte-range-set includes at least one byte-range-spec with</td><td> </td><td class="right">   If a valid byte-range-set includes at least one byte-range-spec with</td><td class="lineno" valign="top"></td></tr>
    213       <tr><td class="lineno" valign="top"></td><td class="left">   a first-byte-pos that is less than the current length of the</td><td> </td><td class="right">   a first-byte-pos that is less than the current length of the</td><td class="lineno" valign="top"></td></tr>
    214       <tr><td class="lineno" valign="top"></td><td class="left">   representation, or at least one suffix-byte-range-spec with a non-</td><td> </td><td class="right">   representation, or at least one suffix-byte-range-spec with a non-</td><td class="lineno" valign="top"></td></tr>
    215       <tr><td class="lineno" valign="top"></td><td class="left">   zero suffix-length, then the byte-range-set is satisfiable.</td><td> </td><td class="right">   zero suffix-length, then the byte-range-set is satisfiable.</td><td class="lineno" valign="top"></td></tr>
    216       <tr><td class="lineno" valign="top"></td><td class="left">   Otherwise, the byte-range-set is unsatisfiable.</td><td> </td><td class="right">   Otherwise, the byte-range-set is unsatisfiable.</td><td class="lineno" valign="top"></td></tr>
    217       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    218       <tr><td><a name="diff0011" /></td></tr>
    219       <tr><td class="lineno" valign="top"></td><td class="lblock">   In the byte<span class="delete"> </span>range syntax, first-byte-pos, last-byte-pos, and suffix-</td><td> </td><td class="rblock">   In the byte<span class="insert">-</span>range syntax, first-byte-pos, last-byte-pos, and suffix-</td><td class="lineno" valign="top"></td></tr>
    220       <tr><td class="lineno" valign="top"></td><td class="left">   length are expressed as decimal number of octets.  Since there is no</td><td> </td><td class="right">   length are expressed as decimal number of octets.  Since there is no</td><td class="lineno" valign="top"></td></tr>
    221       <tr><td class="lineno" valign="top"></td><td class="left">   predefined limit to the length of a payload, recipients MUST</td><td> </td><td class="right">   predefined limit to the length of a payload, recipients MUST</td><td class="lineno" valign="top"></td></tr>
    222       <tr><td class="lineno" valign="top"></td><td class="left">   anticipate potentially large decimal numerals and prevent parsing</td><td> </td><td class="right">   anticipate potentially large decimal numerals and prevent parsing</td><td class="lineno" valign="top"></td></tr>
    223       <tr><td class="lineno" valign="top"></td><td class="left">   errors due to integer conversion overflows.</td><td> </td><td class="right">   errors due to integer conversion overflows.</td><td class="lineno" valign="top"></td></tr>
    224       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    225       <tr><td class="lineno" valign="top"></td><td class="left">2.2.  Other Range Units</td><td> </td><td class="right">2.2.  Other Range Units</td><td class="lineno" valign="top"></td></tr>
    226       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    227       <tr><td class="lineno" valign="top"></td><td class="left">   Range units are intended to be extensible.  New range units ought to</td><td> </td><td class="right">   Range units are intended to be extensible.  New range units ought to</td><td class="lineno" valign="top"></td></tr>
    228       <tr><td class="lineno" valign="top"></td><td class="left">   be registered with IANA, as defined in Section 5.1.</td><td> </td><td class="right">   be registered with IANA, as defined in Section 5.1.</td><td class="lineno" valign="top"></td></tr>
    229       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    230       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    231       <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 9, line 16</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 8, line 16</em></th><td></td></tr>
    232       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    233       <tr><td class="lineno" valign="top"></td><td class="left">   If a client has a partial copy of a representation and wishes to have</td><td> </td><td class="right">   If a client has a partial copy of a representation and wishes to have</td><td class="lineno" valign="top"></td></tr>
    234       <tr><td class="lineno" valign="top"></td><td class="left">   an up-to-date copy of the entire representation, it could use the</td><td> </td><td class="right">   an up-to-date copy of the entire representation, it could use the</td><td class="lineno" valign="top"></td></tr>
    235       <tr><td class="lineno" valign="top"></td><td class="left">   Range header field with a conditional GET (using either or both of</td><td> </td><td class="right">   Range header field with a conditional GET (using either or both of</td><td class="lineno" valign="top"></td></tr>
    236       <tr><td class="lineno" valign="top"></td><td class="left">   If-Unmodified-Since and If-Match.)  However, if the precondition</td><td> </td><td class="right">   If-Unmodified-Since and If-Match.)  However, if the precondition</td><td class="lineno" valign="top"></td></tr>
    237       <tr><td class="lineno" valign="top"></td><td class="left">   fails because the representation has been modified, the client would</td><td> </td><td class="right">   fails because the representation has been modified, the client would</td><td class="lineno" valign="top"></td></tr>
    238       <tr><td class="lineno" valign="top"></td><td class="left">   then have to make a second request to obtain the entire current</td><td> </td><td class="right">   then have to make a second request to obtain the entire current</td><td class="lineno" valign="top"></td></tr>
    239       <tr><td class="lineno" valign="top"></td><td class="left">   representation.</td><td> </td><td class="right">   representation.</td><td class="lineno" valign="top"></td></tr>
    240       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    241       <tr><td class="lineno" valign="top"></td><td class="left">   The "If-Range" header field allows a client to "short-circuit" the</td><td> </td><td class="right">   The "If-Range" header field allows a client to "short-circuit" the</td><td class="lineno" valign="top"></td></tr>
    242       <tr><td><a name="diff0012" /></td></tr>
    243       <tr><td class="lineno" valign="top"></td><td class="lblock">   second request.  Informally, its meaning <span class="delete">is:</span> if the representation is</td><td> </td><td class="rblock">   second request.  Informally, its meaning <span class="insert">is as follows:</span> if the</td><td class="lineno" valign="top"></td></tr>
    244       <tr><td class="lineno" valign="top"></td><td class="lblock">   unchanged, send me the part(s) that I am requesting in Range;</td><td> </td><td class="rblock">   representation is unchanged, send me the part(s) that I am requesting</td><td class="lineno" valign="top"></td></tr>
    245       <tr><td class="lineno" valign="top"></td><td class="lblock">   otherwise, send me the entire representation.</td><td> </td><td class="rblock">   in Range; otherwise, send me the entire representation.</td><td class="lineno" valign="top"></td></tr>
    246       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    247       <tr><td class="lineno" valign="top"></td><td class="left">     If-Range = entity-tag / HTTP-date</td><td> </td><td class="right">     If-Range = entity-tag / HTTP-date</td><td class="lineno" valign="top"></td></tr>
    248       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    249       <tr><td class="lineno" valign="top"></td><td class="left">   A client MUST NOT generate an If-Range header field in a request that</td><td> </td><td class="right">   A client MUST NOT generate an If-Range header field in a request that</td><td class="lineno" valign="top"></td></tr>
    250       <tr><td><a name="diff0013" /></td></tr>
    251195      <tr><td class="lineno" valign="top"></td><td class="lblock">   does not contain a Range header field.  A server MUST ignore an <span class="delete">If-</span></td><td> </td><td class="rblock">   does not contain a Range header field.  A server MUST ignore an</td><td class="lineno" valign="top"></td></tr>
    252196      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Range</span> header field received in a request that does not contain a</td><td> </td><td class="rblock">   <span class="insert">If-Range</span> header field received in a request that does not contain a</td><td class="lineno" valign="top"></td></tr>
     
    262206      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    263207      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    264       <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 9, line 49</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 8, line 49</em></th><td></td></tr>
     208      <tr bgcolor="gray" ><td></td><th><a name="part-l4" /><small>skipping to change at</small><em> page 9, line 49</em></th><th> </th><th><a name="part-r4" /><small>skipping to change at</small><em> page 8, line 49</em></th><td></td></tr>
    265209      <tr><td class="lineno" valign="top"></td><td class="left">   defined by Section 2.2.2 of [RFC7232].  A valid entity-tag can be</td><td> </td><td class="right">   defined by Section 2.2.2 of [RFC7232].  A valid entity-tag can be</td><td class="lineno" valign="top"></td></tr>
    266210      <tr><td class="lineno" valign="top"></td><td class="left">   distinguished from a valid HTTP-date by examining the first two</td><td> </td><td class="right">   distinguished from a valid HTTP-date by examining the first two</td><td class="lineno" valign="top"></td></tr>
     
    273217      <tr><td class="lineno" valign="top"></td><td class="left">   the Range header field.  Note that this comparison by exact match,</td><td> </td><td class="right">   the Range header field.  Note that this comparison by exact match,</td><td class="lineno" valign="top"></td></tr>
    274218      <tr><td class="lineno" valign="top"></td><td class="left">   including when the validator is an HTTP-date, differs from the</td><td> </td><td class="right">   including when the validator is an HTTP-date, differs from the</td><td class="lineno" valign="top"></td></tr>
    275       <tr><td><a name="diff0014" /></td></tr>
     219      <tr><td><a name="diff0011" /></td></tr>
    276220      <tr><td class="lineno" valign="top"></td><td class="lblock">   "earlier than or equal to" comparison used when evaluating an <span class="delete">If-</span></td><td> </td><td class="rblock">   "earlier than or equal to" comparison used when evaluating an</td><td class="lineno" valign="top"></td></tr>
    277221      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   Unmodified-Since</span> conditional.</td><td> </td><td class="rblock">   <span class="insert">If-Unmodified-Since</span> conditional.</td><td class="lineno" valign="top"></td></tr>
     
    287231      <tr><td class="lineno" valign="top"></td><td class="left">   header field (Section 3.1).</td><td> </td><td class="right">   header field (Section 3.1).</td><td class="lineno" valign="top"></td></tr>
    288232      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    289       <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 10, line 33</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 9, line 33</em></th><td></td></tr>
    290       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Range: bytes 21010-47021/47022</td><td> </td><td class="right">     Content-Range: bytes 21010-47021/47022</td><td class="lineno" valign="top"></td></tr>
    291       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Length: 26012</td><td> </td><td class="right">     Content-Length: 26012</td><td class="lineno" valign="top"></td></tr>
    292       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Type: image/gif</td><td> </td><td class="right">     Content-Type: image/gif</td><td class="lineno" valign="top"></td></tr>
    293       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    294       <tr><td class="lineno" valign="top"></td><td class="left">     ... 26012 bytes of partial image data ...</td><td> </td><td class="right">     ... 26012 bytes of partial image data ...</td><td class="lineno" valign="top"></td></tr>
    295       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    296       <tr><td class="lineno" valign="top"></td><td class="left">   If multiple parts are being transferred, the server generating the</td><td> </td><td class="right">   If multiple parts are being transferred, the server generating the</td><td class="lineno" valign="top"></td></tr>
    297       <tr><td class="lineno" valign="top"></td><td class="left">   206 response MUST generate a "multipart/byteranges" payload, as</td><td> </td><td class="right">   206 response MUST generate a "multipart/byteranges" payload, as</td><td class="lineno" valign="top"></td></tr>
    298       <tr><td class="lineno" valign="top"></td><td class="left">   defined in Appendix A, and a Content-Type header field containing the</td><td> </td><td class="right">   defined in Appendix A, and a Content-Type header field containing the</td><td class="lineno" valign="top"></td></tr>
    299       <tr><td class="lineno" valign="top"></td><td class="left">   multipart/byteranges media type and its required boundary parameter.</td><td> </td><td class="right">   multipart/byteranges media type and its required boundary parameter.</td><td class="lineno" valign="top"></td></tr>
    300       <tr><td><a name="diff0015" /></td></tr>
    301       <tr><td class="lineno" valign="top"></td><td class="lblock">   To avoid confusion with single<span class="delete"> </span>part responses, a server MUST NOT</td><td> </td><td class="rblock">   To avoid confusion with single<span class="insert">-</span>part responses, a server MUST NOT</td><td class="lineno" valign="top"></td></tr>
    302       <tr><td class="lineno" valign="top"></td><td class="left">   generate a Content-Range header field in the HTTP header section of a</td><td> </td><td class="right">   generate a Content-Range header field in the HTTP header section of a</td><td class="lineno" valign="top"></td></tr>
    303       <tr><td class="lineno" valign="top"></td><td class="left">   multiple part response (this field will be sent in each part</td><td> </td><td class="right">   multiple part response (this field will be sent in each part</td><td class="lineno" valign="top"></td></tr>
    304       <tr><td class="lineno" valign="top"></td><td class="left">   instead).</td><td> </td><td class="right">   instead).</td><td class="lineno" valign="top"></td></tr>
    305       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    306       <tr><td class="lineno" valign="top"></td><td class="left">   Within the header area of each body part in the multipart payload,</td><td> </td><td class="right">   Within the header area of each body part in the multipart payload,</td><td class="lineno" valign="top"></td></tr>
    307       <tr><td class="lineno" valign="top"></td><td class="left">   the server MUST generate a Content-Range header field corresponding</td><td> </td><td class="right">   the server MUST generate a Content-Range header field corresponding</td><td class="lineno" valign="top"></td></tr>
    308       <tr><td class="lineno" valign="top"></td><td class="left">   to the range being enclosed in that body part.  If the selected</td><td> </td><td class="right">   to the range being enclosed in that body part.  If the selected</td><td class="lineno" valign="top"></td></tr>
    309       <tr><td class="lineno" valign="top"></td><td class="left">   representation would have had a Content-Type header field in a 200</td><td> </td><td class="right">   representation would have had a Content-Type header field in a 200</td><td class="lineno" valign="top"></td></tr>
    310       <tr><td class="lineno" valign="top"></td><td class="left">   (OK) response, the server SHOULD generate that same Content-Type</td><td> </td><td class="right">   (OK) response, the server SHOULD generate that same Content-Type</td><td class="lineno" valign="top"></td></tr>
    311       <tr><td class="lineno" valign="top"></td><td class="left">   field in the header area of each body part.  For example:</td><td> </td><td class="right">   field in the header area of each body part.  For example:</td><td class="lineno" valign="top"></td></tr>
    312       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    313       <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 13, line 29</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 12, line 29</em></th><td></td></tr>
    314       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    315       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Range: bytes 42-1233/*</td><td> </td><td class="right">     Content-Range: bytes 42-1233/*</td><td class="lineno" valign="top"></td></tr>
    316       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    317       <tr><td class="lineno" valign="top"></td><td class="left">   A Content-Range field value is invalid if it contains a byte-range-</td><td> </td><td class="right">   A Content-Range field value is invalid if it contains a byte-range-</td><td class="lineno" valign="top"></td></tr>
    318       <tr><td class="lineno" valign="top"></td><td class="left">   resp that has a last-byte-pos value less than its first-byte-pos</td><td> </td><td class="right">   resp that has a last-byte-pos value less than its first-byte-pos</td><td class="lineno" valign="top"></td></tr>
    319       <tr><td class="lineno" valign="top"></td><td class="left">   value, or a complete-length value less than or equal to its last-</td><td> </td><td class="right">   value, or a complete-length value less than or equal to its last-</td><td class="lineno" valign="top"></td></tr>
    320       <tr><td class="lineno" valign="top"></td><td class="left">   byte-pos value.  The recipient of an invalid Content-Range MUST NOT</td><td> </td><td class="right">   byte-pos value.  The recipient of an invalid Content-Range MUST NOT</td><td class="lineno" valign="top"></td></tr>
    321       <tr><td class="lineno" valign="top"></td><td class="left">   attempt to recombine the received content with a stored</td><td> </td><td class="right">   attempt to recombine the received content with a stored</td><td class="lineno" valign="top"></td></tr>
    322       <tr><td class="lineno" valign="top"></td><td class="left">   representation.</td><td> </td><td class="right">   representation.</td><td class="lineno" valign="top"></td></tr>
    323       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    324       <tr><td><a name="diff0016" /></td></tr>
    325       <tr><td class="lineno" valign="top"></td><td class="lblock">   A server generating a 416 (Range Not Satisfiable) response to a byte</td><td> </td><td class="rblock">   A server generating a 416 (Range Not Satisfiable) response to a byte<span class="insert">-</span></td><td class="lineno" valign="top"></td></tr>
     233      <tr bgcolor="gray" ><td></td><th><a name="part-l5" /><small>skipping to change at</small><em> page 13, line 38</em></th><th> </th><th><a name="part-r5" /><small>skipping to change at</small><em> page 12, line 38</em></th><td></td></tr>
     234      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     235      <tr><td class="lineno" valign="top"></td><td class="left">   A server generating a 416 (Range Not Satisfiable) response to a byte-</td><td> </td><td class="right">   A server generating a 416 (Range Not Satisfiable) response to a byte-</td><td class="lineno" valign="top"></td></tr>
    326236      <tr><td class="lineno" valign="top"></td><td class="left">   range request SHOULD send a Content-Range header field with an</td><td> </td><td class="right">   range request SHOULD send a Content-Range header field with an</td><td class="lineno" valign="top"></td></tr>
    327237      <tr><td class="lineno" valign="top"></td><td class="left">   unsatisfied-range value, as in the following example:</td><td> </td><td class="right">   unsatisfied-range value, as in the following example:</td><td class="lineno" valign="top"></td></tr>
     
    332242      <tr><td class="lineno" valign="top"></td><td class="left">   the selected representation.</td><td> </td><td class="right">   the selected representation.</td><td class="lineno" valign="top"></td></tr>
    333243      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    334       <tr><td><a name="diff0017" /></td></tr>
     244      <tr><td><a name="diff0012" /></td></tr>
    335245      <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">"Content-Range"</span> header field has no meaning for status codes that</td><td> </td><td class="rblock">   The <span class="insert">Content-Range</span> header field has no meaning for status codes that</td><td class="lineno" valign="top"></td></tr>
    336246      <tr><td class="lineno" valign="top"></td><td class="left">   do not explicitly describe its semantic.  For this specification,</td><td> </td><td class="right">   do not explicitly describe its semantic.  For this specification,</td><td class="lineno" valign="top"></td></tr>
     
    345255      <tr><td class="lineno" valign="top"></td><td class="left">        Content-Range: bytes 0-499/1234</td><td> </td><td class="right">        Content-Range: bytes 0-499/1234</td><td class="lineno" valign="top"></td></tr>
    346256      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    347       <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 14, line 28</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 13, line 28</em></th><td></td></tr>
     257      <tr bgcolor="gray" ><td></td><th><a name="part-l6" /><small>skipping to change at</small><em> page 14, line 28</em></th><th> </th><th><a name="part-r6" /><small>skipping to change at</small><em> page 13, line 28</em></th><td></td></tr>
    348258      <tr><td class="lineno" valign="top"></td><td class="left">   have received several ranges of the same representation.  These</td><td> </td><td class="right">   have received several ranges of the same representation.  These</td><td class="lineno" valign="top"></td></tr>
    349259      <tr><td class="lineno" valign="top"></td><td class="left">   ranges can only be safely combined if they all have in common the</td><td> </td><td class="right">   ranges can only be safely combined if they all have in common the</td><td class="lineno" valign="top"></td></tr>
     
    356266      <tr><td class="lineno" valign="top"></td><td class="left">   If the most recent response is an incomplete 200 (OK) response, then</td><td> </td><td class="right">   If the most recent response is an incomplete 200 (OK) response, then</td><td class="lineno" valign="top"></td></tr>
    357267      <tr><td class="lineno" valign="top"></td><td class="left">   the header fields of that response are used for any combined response</td><td> </td><td class="right">   the header fields of that response are used for any combined response</td><td class="lineno" valign="top"></td></tr>
    358       <tr><td><a name="diff0018" /></td></tr>
     268      <tr><td><a name="diff0013" /></td></tr>
    359269      <tr><td class="lineno" valign="top"></td><td class="lblock">   and replace those of the matching stored responses.</td><td> </td><td class="rblock">   and <span class="insert">they </span>replace those of the matching stored responses.</td><td class="lineno" valign="top"></td></tr>
    360270      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    369279      <tr><td class="lineno" valign="top"></td><td class="left">   all instances of the corresponding header fields in the stored</td><td> </td><td class="right">   all instances of the corresponding header fields in the stored</td><td class="lineno" valign="top"></td></tr>
    370280      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    371       <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 15, line 16</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 14, line 16</em></th><td></td></tr>
    372       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    373       <tr><td class="lineno" valign="top"></td><td class="left">   The 416 (Range Not Satisfiable) status code indicates that none of</td><td> </td><td class="right">   The 416 (Range Not Satisfiable) status code indicates that none of</td><td class="lineno" valign="top"></td></tr>
    374       <tr><td class="lineno" valign="top"></td><td class="left">   the ranges in the request's Range header field (Section 3.1) overlap</td><td> </td><td class="right">   the ranges in the request's Range header field (Section 3.1) overlap</td><td class="lineno" valign="top"></td></tr>
    375       <tr><td class="lineno" valign="top"></td><td class="left">   the current extent of the selected resource or that the set of ranges</td><td> </td><td class="right">   the current extent of the selected resource or that the set of ranges</td><td class="lineno" valign="top"></td></tr>
    376       <tr><td class="lineno" valign="top"></td><td class="left">   requested has been rejected due to invalid ranges or an excessive</td><td> </td><td class="right">   requested has been rejected due to invalid ranges or an excessive</td><td class="lineno" valign="top"></td></tr>
    377       <tr><td class="lineno" valign="top"></td><td class="left">   request of small or overlapping ranges.</td><td> </td><td class="right">   request of small or overlapping ranges.</td><td class="lineno" valign="top"></td></tr>
    378       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    379       <tr><td class="lineno" valign="top"></td><td class="left">   For byte ranges, failing to overlap the current extent means that the</td><td> </td><td class="right">   For byte ranges, failing to overlap the current extent means that the</td><td class="lineno" valign="top"></td></tr>
    380       <tr><td class="lineno" valign="top"></td><td class="left">   first-byte-pos of all of the byte-range-spec values were greater than</td><td> </td><td class="right">   first-byte-pos of all of the byte-range-spec values were greater than</td><td class="lineno" valign="top"></td></tr>
    381       <tr><td class="lineno" valign="top"></td><td class="left">   the current length of the selected representation.  When this status</td><td> </td><td class="right">   the current length of the selected representation.  When this status</td><td class="lineno" valign="top"></td></tr>
    382       <tr><td><a name="diff0019" /></td></tr>
    383       <tr><td class="lineno" valign="top"></td><td class="lblock">   code is generated in response to a byte<span class="delete"> </span>range request, the sender</td><td> </td><td class="rblock">   code is generated in response to a byte<span class="insert">-</span>range request, the sender</td><td class="lineno" valign="top"></td></tr>
    384       <tr><td class="lineno" valign="top"></td><td class="left">   SHOULD generate a Content-Range header field specifying the current</td><td> </td><td class="right">   SHOULD generate a Content-Range header field specifying the current</td><td class="lineno" valign="top"></td></tr>
    385       <tr><td class="lineno" valign="top"></td><td class="left">   length of the selected representation (Section 4.2).</td><td> </td><td class="right">   length of the selected representation (Section 4.2).</td><td class="lineno" valign="top"></td></tr>
    386       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    387       <tr><td class="lineno" valign="top"></td><td class="left">   For example:</td><td> </td><td class="right">   For example:</td><td class="lineno" valign="top"></td></tr>
    388       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    389       <tr><td class="lineno" valign="top"></td><td class="left">     HTTP/1.1 416 Range Not Satisfiable</td><td> </td><td class="right">     HTTP/1.1 416 Range Not Satisfiable</td><td class="lineno" valign="top"></td></tr>
    390       <tr><td class="lineno" valign="top"></td><td class="left">     Date: Fri, 20 Jan 2012 15:41:54 GMT</td><td> </td><td class="right">     Date: Fri, 20 Jan 2012 15:41:54 GMT</td><td class="lineno" valign="top"></td></tr>
    391       <tr><td class="lineno" valign="top"></td><td class="left">     Content-Range: bytes */47022</td><td> </td><td class="right">     Content-Range: bytes */47022</td><td class="lineno" valign="top"></td></tr>
    392       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    393       <tr><td class="lineno" valign="top"></td><td class="left">      Note: Because servers are free to ignore Range, many</td><td> </td><td class="right">      Note: Because servers are free to ignore Range, many</td><td class="lineno" valign="top"></td></tr>
    394       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    395       <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 15, line 40</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 14, line 40</em></th><td></td></tr>
    396       <tr><td class="lineno" valign="top"></td><td class="left">      task (albeit less efficiently) and partly because clients might</td><td> </td><td class="right">      task (albeit less efficiently) and partly because clients might</td><td class="lineno" valign="top"></td></tr>
    397       <tr><td class="lineno" valign="top"></td><td class="left">      not stop making an invalid partial request until they have</td><td> </td><td class="right">      not stop making an invalid partial request until they have</td><td class="lineno" valign="top"></td></tr>
     281      <tr bgcolor="gray" ><td></td><th><a name="part-l7" /><small>skipping to change at</small><em> page 15, line 42</em></th><th> </th><th><a name="part-r7" /><small>skipping to change at</small><em> page 14, line 42</em></th><td></td></tr>
    398282      <tr><td class="lineno" valign="top"></td><td class="left">      received a complete representation.  Thus, clients cannot depend</td><td> </td><td class="right">      received a complete representation.  Thus, clients cannot depend</td><td class="lineno" valign="top"></td></tr>
    399283      <tr><td class="lineno" valign="top"></td><td class="left">      on receiving a 416 (Range Not Satisfiable) response even when it</td><td> </td><td class="right">      on receiving a 416 (Range Not Satisfiable) response even when it</td><td class="lineno" valign="top"></td></tr>
     
    404288      <tr><td class="lineno" valign="top"></td><td class="left">5.1.  Range Unit Registry</td><td> </td><td class="right">5.1.  Range Unit Registry</td><td class="lineno" valign="top"></td></tr>
    405289      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    406       <tr><td><a name="diff0020" /></td></tr>
    407       <tr><td class="lineno" valign="top"></td><td class="lblock">   The <span class="delete">HTTP</span> Range Unit <span class="delete">Registry</span> defines the namespace for the range unit</td><td> </td><td class="rblock">   The <span class="insert">"HTTP</span> Range Unit <span class="insert">Registry"</span> defines the namespace for the range</td><td class="lineno" valign="top"></td></tr>
    408       <tr><td class="lineno" valign="top"></td><td class="lblock">   names and refers to their corresponding specifications.  The registry</td><td> </td><td class="rblock">   unit names and refers to their corresponding specifications.  The</td><td class="lineno" valign="top"></td></tr>
    409       <tr><td class="lineno" valign="top"></td><td class="lblock">   will be created and maintained at <span class="delete">(the suggested URI)</span></td><td> </td><td class="rblock">   registry will be created and maintained at</td><td class="lineno" valign="top"></td></tr>
     290      <tr><td class="lineno" valign="top"></td><td class="left">   The "HTTP Range Unit Registry" defines the namespace for the range</td><td> </td><td class="right">   The "HTTP Range Unit Registry" defines the namespace for the range</td><td class="lineno" valign="top"></td></tr>
     291      <tr><td class="lineno" valign="top"></td><td class="left">   unit names and refers to their corresponding specifications.  The</td><td> </td><td class="right">   unit names and refers to their corresponding specifications.  The</td><td class="lineno" valign="top"></td></tr>
     292      <tr><td><a name="diff0014" /></td></tr>
     293      <tr><td class="lineno" valign="top"></td><td class="lblock">   registry will be created and maintained at<span class="delete"> (the suggested URI)</span></td><td> </td><td class="rblock">   registry will be created and maintained at</td><td class="lineno" valign="top"></td></tr>
    410294      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/http-parameters&gt;.</td><td class="lineno" valign="top"></td></tr>
    411295      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    424308      <tr><td class="lineno" valign="top"></td><td class="left">5.1.2.  Registrations</td><td> </td><td class="right">5.1.2.  Registrations</td><td class="lineno" valign="top"></td></tr>
    425309      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    426       <tr><td><a name="diff0021" /></td></tr>
    427       <tr><td class="lineno" valign="top"></td><td class="lblock">   The initial <span class="delete">HTTP Range Unit Registry shall contain</span> the registrations</td><td> </td><td class="rblock">   The initial <span class="insert">"HTTP Range Unit Registry" contains</span> the registrations</td><td class="lineno" valign="top"></td></tr>
    428       <tr><td class="lineno" valign="top"></td><td class="left">   below:</td><td> </td><td class="right">   below:</td><td class="lineno" valign="top"></td></tr>
     310      <tr><td><a name="diff0015" /></td></tr>
     311      <tr><td class="lineno" valign="top"></td><td class="lblock">   The initial <span class="delete">range unit registry</span> contains the registrations below:</td><td> </td><td class="rblock">   The initial <span class="insert">"HTTP Range Unit Registry"</span> contains the registrations</td><td class="lineno" valign="top"></td></tr>
     312      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   below:</td><td class="lineno" valign="top"></td></tr>
    429313      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    430314      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------+---------------------------------------+-------------+</td><td> </td><td class="right">   +-------------+---------------------------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
     
    437321      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------+---------------------------------------+-------------+</td><td> </td><td class="right">   +-------------+---------------------------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
    438322      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    439       <tr><td class="lineno" valign="top"></td><td class="left">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td> </td><td class="right">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td class="lineno" valign="top"></td></tr>
    440       <tr><td class="lineno" valign="top"></td><td class="left">   Engineering Task Force".</td><td> </td><td class="right">   Engineering Task Force".</td><td class="lineno" valign="top"></td></tr>
    441       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    442       <tr><td class="lineno" valign="top"></td><td class="left">5.2.  Status Code Registration</td><td> </td><td class="right">5.2.  Status Code Registration</td><td class="lineno" valign="top"></td></tr>
    443       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    444       <tr><td class="lineno" valign="top"></td><td class="left">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located</td><td> </td><td class="right">   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located</td><td class="lineno" valign="top"></td></tr>
    445       <tr><td class="lineno" valign="top"></td><td class="left">   at &lt;http://www.iana.org/assignments/http-status-codes&gt; has been</td><td> </td><td class="right">   at &lt;http://www.iana.org/assignments/http-status-codes&gt; has been</td><td class="lineno" valign="top"></td></tr>
    446       <tr><td><a name="diff0022" /></td></tr>
    447       <tr><td class="lineno" valign="top"></td><td class="lblock">   updated <span class="delete">with</span> the registrations below:</td><td> </td><td class="rblock">   updated <span class="insert">to include</span> the registrations below:</td><td class="lineno" valign="top"></td></tr>
    448       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    449       <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-----------------------+-------------+</td><td> </td><td class="right">   +-------+-----------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
    450       <tr><td class="lineno" valign="top"></td><td class="left">   | Value | Description           | Reference   |</td><td> </td><td class="right">   | Value | Description           | Reference   |</td><td class="lineno" valign="top"></td></tr>
    451       <tr><td class="lineno" valign="top"></td><td class="left">   +-------+-----------------------+-------------+</td><td> </td><td class="right">   +-------+-----------------------+-------------+</td><td class="lineno" valign="top"></td></tr>
     323      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     324      <tr bgcolor="gray" ><td></td><th><a name="part-l8" /><small>skipping to change at</small><em> page 16, line 44</em></th><th> </th><th><a name="part-r8" /><small>skipping to change at</small><em> page 15, line 45</em></th><td></td></tr>
    452325      <tr><td class="lineno" valign="top"></td><td class="left">   | 206   | Partial Content       | Section 4.1 |</td><td> </td><td class="right">   | 206   | Partial Content       | Section 4.1 |</td><td class="lineno" valign="top"></td></tr>
    453326      <tr><td class="lineno" valign="top"></td><td class="left">   | 416   | Range Not Satisfiable | Section 4.4 |</td><td> </td><td class="right">   | 416   | Range Not Satisfiable | Section 4.4 |</td><td class="lineno" valign="top"></td></tr>
     
    458331      <tr><td class="lineno" valign="top"></td><td class="left">   HTTP header fields are registered within the "Message Headers"</td><td> </td><td class="right">   HTTP header fields are registered within the "Message Headers"</td><td class="lineno" valign="top"></td></tr>
    459332      <tr><td class="lineno" valign="top"></td><td class="left">   registry maintained at</td><td> </td><td class="right">   registry maintained at</td><td class="lineno" valign="top"></td></tr>
    460       <tr><td><a name="diff0023" /></td></tr>
    461       <tr><td class="lineno" valign="top"></td><td class="lblock">   &lt;http://www.iana.org/assignments/message-headers<span class="delete">/</span>&gt;.</td><td> </td><td class="rblock">   &lt;http://www.iana.org/assignments/message-headers&gt;.</td><td class="lineno" valign="top"></td></tr>
    462       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    463       <tr><td><a name="diff0024" /></td></tr>
     333      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/message-headers&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/message-headers&gt;.</td><td class="lineno" valign="top"></td></tr>
     334      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     335      <tr><td><a name="diff0016" /></td></tr>
    464336      <tr><td class="lineno" valign="top"></td><td class="lblock">   This document defines the following HTTP header <span class="delete">fields, so the</span></td><td> </td><td class="rblock">   This document defines the following HTTP header <span class="insert">fields; their</span></td><td class="lineno" valign="top"></td></tr>
    465337      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   "Permanent Message Header Field Names"</span> registry <span class="delete">has</span> been updated</td><td> </td><td class="rblock"><span class="insert">   associated</span> registry <span class="insert">entries have</span> been updated <span class="insert">according to the</span></td><td class="lineno" valign="top"></td></tr>
     
    475347      <tr><td class="lineno" valign="top"></td><td class="left">   +-------------------+----------+----------+-------------+</td><td> </td><td class="right">   +-------------------+----------+----------+-------------+</td><td class="lineno" valign="top"></td></tr>
    476348      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    477       <tr><td class="lineno" valign="top"></td><td class="left">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td> </td><td class="right">   The change controller is: "IETF (iesg@ietf.org) - Internet</td><td class="lineno" valign="top"></td></tr>
    478       <tr><td class="lineno" valign="top"></td><td class="left">   Engineering Task Force".</td><td> </td><td class="right">   Engineering Task Force".</td><td class="lineno" valign="top"></td></tr>
    479       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    480       <tr><td class="lineno" valign="top"></td><td class="left">5.4.  Internet Media Type Registration</td><td> </td><td class="right">5.4.  Internet Media Type Registration</td><td class="lineno" valign="top"></td></tr>
    481       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    482       <tr><td class="lineno" valign="top"></td><td class="left">   IANA maintains the registry of Internet media types [BCP13] at</td><td> </td><td class="right">   IANA maintains the registry of Internet media types [BCP13] at</td><td class="lineno" valign="top"></td></tr>
    483       <tr><td class="lineno" valign="top"></td><td class="left">   &lt;http://www.iana.org/assignments/media-types&gt;.</td><td> </td><td class="right">   &lt;http://www.iana.org/assignments/media-types&gt;.</td><td class="lineno" valign="top"></td></tr>
    484       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    485       <tr><td class="lineno" valign="top"></td><td class="left">   This document serves as the specification for the Internet media type</td><td> </td><td class="right">   This document serves as the specification for the Internet media type</td><td class="lineno" valign="top"></td></tr>
    486       <tr><td><a name="diff0025" /></td></tr>
    487       <tr><td class="lineno" valign="top"></td><td class="lblock">   "multipart/byteranges".  The following <span class="delete">is to be</span> registered with IANA.</td><td> </td><td class="rblock">   "multipart/byteranges".  The following <span class="insert">has been</span> registered with IANA.</td><td class="lineno" valign="top"></td></tr>
    488       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    489       <tr><td class="lineno" valign="top"></td><td class="left">5.4.1.  Internet Media Type multipart/byteranges</td><td> </td><td class="right">5.4.1.  Internet Media Type multipart/byteranges</td><td class="lineno" valign="top"></td></tr>
    490       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    491       <tr><td class="lineno" valign="top"></td><td class="left">   Type name:  multipart</td><td> </td><td class="right">   Type name:  multipart</td><td class="lineno" valign="top"></td></tr>
    492       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    493       <tr><td class="lineno" valign="top"></td><td class="left">   Subtype name:  byteranges</td><td> </td><td class="right">   Subtype name:  byteranges</td><td class="lineno" valign="top"></td></tr>
    494       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    495       <tr><td class="lineno" valign="top"></td><td class="left">   Required parameters:  boundary</td><td> </td><td class="right">   Required parameters:  boundary</td><td class="lineno" valign="top"></td></tr>
    496       <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    497       <tr><td class="lineno" valign="top"></td><td class="left">   Optional parameters:  N/A</td><td> </td><td class="right">   Optional parameters:  N/A</td><td class="lineno" valign="top"></td></tr>
    498       <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    499       <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 18, line 13</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 17, line 13</em></th><td></td></tr>
     349      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
     350      <tr bgcolor="gray" ><td></td><th><a name="part-l9" /><small>skipping to change at</small><em> page 18, line 13</em></th><th> </th><th><a name="part-r9" /><small>skipping to change at</small><em> page 17, line 13</em></th><td></td></tr>
    500351      <tr><td class="lineno" valign="top"></td><td class="left">   Additional information:</td><td> </td><td class="right">   Additional information:</td><td class="lineno" valign="top"></td></tr>
    501352      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    508359      <tr><td class="lineno" valign="top"></td><td class="left">      Macintosh file type code(s):  N/A</td><td> </td><td class="right">      Macintosh file type code(s):  N/A</td><td class="lineno" valign="top"></td></tr>
    509360      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    510       <tr><td><a name="diff0026" /></td></tr>
     361      <tr><td><a name="diff0017" /></td></tr>
    511362      <tr><td class="lineno" valign="top"></td><td class="lblock">   Person and email address to contact for further information:  See</td><td> </td><td class="rblock">   Person and email address to contact for further information:</td><td class="lineno" valign="top"></td></tr>
    512363      <tr><td class="lineno" valign="top"></td><td class="lblock">      Authors' Addresses <span class="delete">Section.</span></td><td> </td><td class="rblock">      See Authors' Addresses <span class="insert">section of RFC 7233.</span></td><td class="lineno" valign="top"></td></tr>
     
    516367      <tr><td class="lineno" valign="top"></td><td class="left">   Restrictions on usage:  N/A</td><td> </td><td class="right">   Restrictions on usage:  N/A</td><td class="lineno" valign="top"></td></tr>
    517368      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    518       <tr><td><a name="diff0027" /></td></tr>
     369      <tr><td><a name="diff0018" /></td></tr>
    519370      <tr><td class="lineno" valign="top"></td><td class="lblock">   Author:  See Authors<span class="delete">' Addresses</span> Section.</td><td> </td><td class="rblock">   Author:  See Authors Section.</td><td class="lineno" valign="top"></td></tr>
    520371      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    528379      <tr><td class="lineno" valign="top"></td><td class="left">   addressed in HTTP messaging [RFC7230] and semantics [RFC7231].</td><td> </td><td class="right">   addressed in HTTP messaging [RFC7230] and semantics [RFC7231].</td><td class="lineno" valign="top"></td></tr>
    529380      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    530       <tr><td><a name="diff0028" /></td></tr>
     381      <tr><td><a name="diff0019" /></td></tr>
    531382      <tr><td class="lineno" valign="top"></td><td class="lblock">6.1.  Denial<span class="delete"> of Service Attacks u</span>sing Range</td><td> </td><td class="rblock">6.1.  Denial<span class="insert">-of-Service Attacks U</span>sing Range</td><td class="lineno" valign="top"></td></tr>
    532383      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    541392      <tr><td class="lineno" valign="top"></td><td class="left">   apparent reason.  Multipart range requests are not designed to</td><td> </td><td class="right">   apparent reason.  Multipart range requests are not designed to</td><td class="lineno" valign="top"></td></tr>
    542393      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    543       <tr bgcolor="gray" ><td></td><th><a name="part-l13" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r13" /><small>skipping to change at</small><em> page 18, line 18</em></th><td></td></tr>
     394      <tr bgcolor="gray" ><td></td><th><a name="part-l10" /><small>skipping to change at</small><em> page 19, line 18</em></th><th> </th><th><a name="part-r10" /><small>skipping to change at</small><em> page 18, line 18</em></th><td></td></tr>
    544395      <tr><td class="lineno" valign="top"></td><td class="left">              November 1996.</td><td> </td><td class="right">              November 1996.</td><td class="lineno" valign="top"></td></tr>
    545396      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    552403      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    553404      <tr><td class="lineno" valign="top"></td><td class="left">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td> </td><td class="right">              Protocol (HTTP/1.1): Message Syntax and Routing",</td><td class="lineno" valign="top"></td></tr>
    554       <tr><td><a name="diff0029" /></td></tr>
     405      <tr><td><a name="diff0020" /></td></tr>
    555406      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p1-messaging-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7230,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    556407      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
    557408      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    558409      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    559       <tr><td><a name="diff0030" /></td></tr>
     410      <tr><td><a name="diff0021" /></td></tr>
    560411      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Semantics and Content",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Semantics and Content", <span class="insert">RFC 7231,</span></td><td class="lineno" valign="top"></td></tr>
    561412      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p2-semantics-latest (work in progress),</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    563414      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    564415      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td> </td><td class="right">   [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer</td><td class="lineno" valign="top"></td></tr>
    565       <tr><td><a name="diff0031" /></td></tr>
     416      <tr><td><a name="diff0022" /></td></tr>
    566417      <tr><td class="lineno" valign="top"></td><td class="lblock">              Protocol (HTTP/1.1): Conditional Requests",</td><td> </td><td class="rblock">              Protocol (HTTP/1.1): Conditional Requests", <span class="insert">RFC 7232,</span></td><td class="lineno" valign="top"></td></tr>
    567418      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p4-conditional-latest (work in</span></td><td> </td><td class="rblock">              May 2014.</td><td class="lineno" valign="top"></td></tr>
     
    570421      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td> </td><td class="right">   [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,</td><td class="lineno" valign="top"></td></tr>
    571422      <tr><td class="lineno" valign="top"></td><td class="left">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td> </td><td class="right">              Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",</td><td class="lineno" valign="top"></td></tr>
    572       <tr><td><a name="diff0032" /></td></tr>
     423      <tr><td><a name="diff0023" /></td></tr>
    573424      <tr><td class="lineno" valign="top"></td><td class="lblock">              <span class="delete">draft-ietf-httpbis-p6-cache-latest (work in progress),</span></td><td> </td><td class="rblock">              <span class="insert">RFC 7234,</span> May 2014.</td><td class="lineno" valign="top"></td></tr>
    574425      <tr><td class="lineno" valign="top"></td><td class="lblock">              May 2014.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
     
    584435      <tr><td class="lineno" valign="top"></td><td class="left">              September 2004.</td><td> </td><td class="right">              September 2004.</td><td class="lineno" valign="top"></td></tr>
    585436      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    586       <tr bgcolor="gray" ><td></td><th><a name="part-l14" /><small>skipping to change at</small><em> page 20, line 27</em></th><th> </th><th><a name="part-r14" /><small>skipping to change at</small><em> page 19, line 26</em></th><td></td></tr>
     437      <tr bgcolor="gray" ><td></td><th><a name="part-l11" /><small>skipping to change at</small><em> page 20, line 27</em></th><th> </th><th><a name="part-r11" /><small>skipping to change at</small><em> page 19, line 26</em></th><td></td></tr>
    587438      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    588439      <tr><td class="lineno" valign="top"></td><td class="left">   Implementation Notes:</td><td> </td><td class="right">   Implementation Notes:</td><td class="lineno" valign="top"></td></tr>
     
    595446      <tr><td class="lineno" valign="top"></td><td class="left">       incorrectly.</td><td> </td><td class="right">       incorrectly.</td><td class="lineno" valign="top"></td></tr>
    596447      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    597       <tr><td><a name="diff0033" /></td></tr>
     448      <tr><td><a name="diff0024" /></td></tr>
    598449      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  A number of clients and servers were coded to an early draft of</td><td> </td><td class="rblock">   3.  A number of clients and servers were coded to an early draft</td><td class="lineno" valign="top"></td></tr>
    599450      <tr><td class="lineno" valign="top"></td><td class="lblock">       the byteranges specification that used a media type of <span class="delete">multipart/</span></td><td> </td><td class="rblock">       <span class="insert">version</span> of the byteranges specification that used a media type of</td><td class="lineno" valign="top"></td></tr>
     
    611462      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES</td><td> </td><td class="right">     Content-Type: multipart/byteranges; boundary=THIS_STRING_SEPARATES</td><td class="lineno" valign="top"></td></tr>
    612463      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
    613       <tr bgcolor="gray" ><td></td><th><a name="part-l15" /><small>skipping to change at</small><em> page 21, line 9</em></th><th> </th><th><a name="part-r15" /><small>skipping to change at</small><em> page 20, line 8</em></th><td></td></tr>
     464      <tr bgcolor="gray" ><td></td><th><a name="part-l12" /><small>skipping to change at</small><em> page 21, line 9</em></th><th> </th><th><a name="part-r12" /><small>skipping to change at</small><em> page 20, line 8</em></th><td></td></tr>
    614465      <tr><td class="lineno" valign="top"></td><td class="left">     --THIS_STRING_SEPARATES</td><td> </td><td class="right">     --THIS_STRING_SEPARATES</td><td class="lineno" valign="top"></td></tr>
    615466      <tr><td class="lineno" valign="top"></td><td class="left">     Content-Type: video/example</td><td> </td><td class="right">     Content-Type: video/example</td><td class="lineno" valign="top"></td></tr>
     
    622473      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    623474      <tr><td class="lineno" valign="top"></td><td class="left">   Servers are given more leeway in how they respond to a range request,</td><td> </td><td class="right">   Servers are given more leeway in how they respond to a range request,</td><td class="lineno" valign="top"></td></tr>
    624       <tr><td><a name="diff0034" /></td></tr>
     475      <tr><td><a name="diff0025" /></td></tr>
    625476      <tr><td class="lineno" valign="top"></td><td class="lblock">   in order to mitigate abuse by malicious (or just greedy) <span class="delete">clients.</span></td><td> </td><td class="rblock">   in order to mitigate abuse by malicious (or just greedy) <span class="insert">clients</span></td><td class="lineno" valign="top"></td></tr>
    626477      <tr><td class="lineno" valign="top"></td><td class="lblock">   (Section <span class="delete">3.1)</span></td><td> </td><td class="rblock">   (Section <span class="insert">3.1).</span></td><td class="lineno" valign="top"></td></tr>
    627478      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    628       <tr><td><a name="diff0035" /></td></tr>
     479      <tr><td><a name="diff0026" /></td></tr>
    629480      <tr><td class="lineno" valign="top"></td><td class="lblock">   A weak validator cannot be used in a 206 response<span class="delete">.  (Section 4.1)</span></td><td> </td><td class="rblock">   A weak validator cannot be used in a 206 response<span class="insert"> (Section 4.1).</span></td><td class="lineno" valign="top"></td></tr>
    630481      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    631482      <tr><td class="lineno" valign="top"></td><td class="left">   The Content-Range header field only has meaning when the status code</td><td> </td><td class="right">   The Content-Range header field only has meaning when the status code</td><td class="lineno" valign="top"></td></tr>
    632       <tr><td><a name="diff0036" /></td></tr>
     483      <tr><td><a name="diff0027" /></td></tr>
    633484      <tr><td class="lineno" valign="top"></td><td class="lblock">   explicitly defines its use<span class="delete">.  (Section 4.2)</span></td><td> </td><td class="rblock">   explicitly defines its use<span class="insert"> (Section 4.2).</span></td><td class="lineno" valign="top"></td></tr>
    634485      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    635       <tr><td><a name="diff0037" /></td></tr>
     486      <tr><td><a name="diff0028" /></td></tr>
    636487      <tr><td class="lineno" valign="top"></td><td class="lblock">   This specification introduces a Range Unit <span class="delete">Registry.</span>  (Section <span class="delete">5.1)</span></td><td> </td><td class="rblock">   This specification introduces a <span class="insert">the "HTTP</span> Range Unit <span class="insert">Registry"</span></td><td class="lineno" valign="top"></td></tr>
    637488      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   (Section <span class="insert">5.1).</span></td><td class="lineno" valign="top"></td></tr>
    638489      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    639       <tr><td><a name="diff0038" /></td></tr>
     490      <tr><td><a name="diff0029" /></td></tr>
    640491      <tr><td class="lineno" valign="top"></td><td class="lblock">   multipart/byteranges can consist of a single part<span class="delete">.  (Appendix A)</span></td><td> </td><td class="rblock">   multipart/byteranges can consist of a single part<span class="insert"> (Appendix A).</span></td><td class="lineno" valign="top"></td></tr>
    641492      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    654505      <tr><td class="lineno" valign="top"></td><td class="left">   The rules below are defined in [RFC7230]:</td><td> </td><td class="right">   The rules below are defined in [RFC7230]:</td><td class="lineno" valign="top"></td></tr>
    655506      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    656       <tr><td><a name="diff0039" /></td></tr>
     507      <tr><td><a name="diff0030" /></td></tr>
    657508      <tr><td class="lineno" valign="top"></td><td class="lblock">     OWS        = &lt;OWS, <span class="delete">see</span> [RFC7230], Section 3.2.3&gt;</td><td> </td><td class="rblock">     OWS        = &lt;OWS, <span class="insert">defined in</span> [RFC7230], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
    658509      <tr><td class="lineno" valign="top"></td><td class="lblock">     token      = &lt;token, <span class="delete">see</span> [RFC7230], Section 3.2.6&gt;</td><td> </td><td class="rblock">     token      = &lt;token, <span class="insert">defined in</span> [RFC7230], Section 3.2.6&gt;</td><td class="lineno" valign="top"></td></tr>
     
    660511      <tr><td class="lineno" valign="top"></td><td class="left">   The rules below are defined in other parts:</td><td> </td><td class="right">   The rules below are defined in other parts:</td><td class="lineno" valign="top"></td></tr>
    661512      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    662       <tr><td><a name="diff0040" /></td></tr>
     513      <tr><td><a name="diff0031" /></td></tr>
    663514      <tr><td class="lineno" valign="top"></td><td class="lblock">     HTTP-date  = &lt;HTTP-date, <span class="delete">see</span> [RFC7231], Section 7.1.1.1&gt;</td><td> </td><td class="rblock">     HTTP-date  = &lt;HTTP-date, <span class="insert">defined in</span> [RFC7231], Section 7.1.1.1&gt;</td><td class="lineno" valign="top"></td></tr>
    664515      <tr><td class="lineno" valign="top"></td><td class="lblock">     entity-tag = &lt;entity-tag, <span class="delete">see</span> [RFC7232], Section 2.3&gt;</td><td> </td><td class="rblock">     entity-tag = &lt;entity-tag, <span class="insert">defined in</span> [RFC7232], Section 2.3&gt;</td><td class="lineno" valign="top"></td></tr>
     
    673524      <tr><td class="lineno" valign="top"></td><td class="left">   Content-Range = byte-content-range / other-content-range</td><td> </td><td class="right">   Content-Range = byte-content-range / other-content-range</td><td class="lineno" valign="top"></td></tr>
    674525      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    675       <tr><td><a name="diff0041" /></td></tr>
     526      <tr><td><a name="diff0032" /></td></tr>
    676527      <tr><td class="lineno" valign="top"></td><td class="lblock">   HTTP-date = &lt;HTTP-date, <span class="delete">see</span> [RFC7231], Section 7.1.1.1&gt;</td><td> </td><td class="rblock">   HTTP-date = &lt;HTTP-date, <span class="insert">defined in</span> [RFC7231], Section 7.1.1.1&gt;</td><td class="lineno" valign="top"></td></tr>
    677528      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    678529      <tr><td class="lineno" valign="top"></td><td class="left">   If-Range = entity-tag / HTTP-date</td><td> </td><td class="right">   If-Range = entity-tag / HTTP-date</td><td class="lineno" valign="top"></td></tr>
    679530      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    680       <tr><td><a name="diff0042" /></td></tr>
     531      <tr><td><a name="diff0033" /></td></tr>
    681532      <tr><td class="lineno" valign="top"></td><td class="lblock">   OWS = &lt;OWS, <span class="delete">see</span> [RFC7230], Section 3.2.3&gt;</td><td> </td><td class="rblock">   OWS = &lt;OWS, <span class="insert">defined in</span> [RFC7230], Section 3.2.3&gt;</td><td class="lineno" valign="top"></td></tr>
    682533      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    699550      <tr><td class="lineno" valign="top"></td><td class="left">   complete-length = 1*DIGIT</td><td> </td><td class="right">   complete-length = 1*DIGIT</td><td class="lineno" valign="top"></td></tr>
    700551      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    701       <tr><td><a name="diff0043" /></td></tr>
     552      <tr><td><a name="diff0034" /></td></tr>
    702553      <tr><td class="lineno" valign="top"></td><td class="lblock">   entity-tag = &lt;entity-tag, <span class="delete">see</span> [RFC7232], Section 2.3&gt;</td><td> </td><td class="rblock">   entity-tag = &lt;entity-tag, <span class="insert">defined in</span> [RFC7232], Section 2.3&gt;</td><td class="lineno" valign="top"></td></tr>
    703554      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    717568      <tr><td class="lineno" valign="top"></td><td class="left">   suffix-length = 1*DIGIT</td><td> </td><td class="right">   suffix-length = 1*DIGIT</td><td class="lineno" valign="top"></td></tr>
    718569      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    719       <tr><td><a name="diff0044" /></td></tr>
     570      <tr><td><a name="diff0035" /></td></tr>
    720571      <tr><td class="lineno" valign="top"></td><td class="lblock">   token = &lt;token, <span class="delete">see</span> [RFC7230], Section 3.2.6&gt;</td><td> </td><td class="rblock">   token = &lt;token, <span class="insert">defined in</span> [RFC7230], Section 3.2.6&gt;</td><td class="lineno" valign="top"></td></tr>
    721572      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    725576      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    726577      <tr><td class="lineno" valign="top"></td><td class="left">   2</td><td> </td><td class="right">   2</td><td class="lineno" valign="top"></td></tr>
    727       <tr><td><a name="diff0045" /></td></tr>
     578      <tr><td><a name="diff0036" /></td></tr>
    728579      <tr><td class="lineno" valign="top"></td><td class="lblock">      206 Partial Content (status code)  <span class="delete">10</span></td><td> </td><td class="rblock">      206 Partial Content (status code)  <span class="insert">9</span></td><td class="lineno" valign="top"></td></tr>
    729580      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    730581      <tr><td class="lineno" valign="top"></td><td class="left">   4</td><td> </td><td class="right">   4</td><td class="lineno" valign="top"></td></tr>
    731       <tr><td><a name="diff0046" /></td></tr>
     582      <tr><td><a name="diff0037" /></td></tr>
    732583      <tr><td class="lineno" valign="top"></td><td class="lblock">      416 Range Not Satisfiable (status code)  1<span class="delete">5</span></td><td> </td><td class="rblock">      416 Range Not Satisfiable (status code)  1<span class="insert">4</span></td><td class="lineno" valign="top"></td></tr>
    733584      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    734585      <tr><td class="lineno" valign="top"></td><td class="left">   A</td><td> </td><td class="right">   A</td><td class="lineno" valign="top"></td></tr>
    735       <tr><td><a name="diff0047" /></td></tr>
     586      <tr><td><a name="diff0038" /></td></tr>
    736587      <tr><td class="lineno" valign="top"></td><td class="lblock">      Accept-Ranges header field  <span class="delete">7</span></td><td> </td><td class="rblock">      Accept-Ranges header field  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    737588      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    738589      <tr><td class="lineno" valign="top"></td><td class="left">   C</td><td> </td><td class="right">   C</td><td class="lineno" valign="top"></td></tr>
    739       <tr><td><a name="diff0048" /></td></tr>
     590      <tr><td><a name="diff0039" /></td></tr>
    740591      <tr><td class="lineno" valign="top"></td><td class="lblock">      Content-Range header field  1<span class="delete">2</span></td><td> </td><td class="rblock">      Content-Range header field  1<span class="insert">1</span></td><td class="lineno" valign="top"></td></tr>
    741592      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    742593      <tr><td class="lineno" valign="top"></td><td class="left">   G</td><td> </td><td class="right">   G</td><td class="lineno" valign="top"></td></tr>
    743594      <tr><td class="lineno" valign="top"></td><td class="left">      Grammar</td><td> </td><td class="right">      Grammar</td><td class="lineno" valign="top"></td></tr>
    744       <tr><td><a name="diff0049" /></td></tr>
     595      <tr><td><a name="diff0040" /></td></tr>
    745596      <tr><td class="lineno" valign="top"></td><td class="lblock">         Accept-Ranges  <span class="delete">7</span></td><td> </td><td class="rblock">         Accept-Ranges  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    746597      <tr><td class="lineno" valign="top"></td><td class="lblock">         acceptable-ranges  <span class="delete">7</span></td><td> </td><td class="rblock">         acceptable-ranges  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
     
    768619      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    769620      <tr><td class="lineno" valign="top"></td><td class="left">   I</td><td> </td><td class="right">   I</td><td class="lineno" valign="top"></td></tr>
    770       <tr><td><a name="diff0050" /></td></tr>
     621      <tr><td><a name="diff0041" /></td></tr>
    771622      <tr><td class="lineno" valign="top"></td><td class="lblock">      If-Range header field  <span class="delete">9</span></td><td> </td><td class="rblock">      If-Range header field  <span class="insert">8</span></td><td class="lineno" valign="top"></td></tr>
    772623      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    773624      <tr><td class="lineno" valign="top"></td><td class="left">   M</td><td> </td><td class="right">   M</td><td class="lineno" valign="top"></td></tr>
    774625      <tr><td class="lineno" valign="top"></td><td class="left">      Media Type</td><td> </td><td class="right">      Media Type</td><td class="lineno" valign="top"></td></tr>
    775       <tr><td><a name="diff0051" /></td></tr>
     626      <tr><td><a name="diff0042" /></td></tr>
    776627      <tr><td class="lineno" valign="top"></td><td class="lblock">         multipart/byteranges  <span class="delete">17, 20</span></td><td> </td><td class="rblock">         multipart/byteranges  <span class="insert">16, 19</span></td><td class="lineno" valign="top"></td></tr>
    777628      <tr><td class="lineno" valign="top"></td><td class="lblock">         multipart/x-byteranges  <span class="delete">20</span></td><td> </td><td class="rblock">         multipart/x-byteranges  <span class="insert">19</span></td><td class="lineno" valign="top"></td></tr>
     
    780631      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
    781632      <tr><td class="lineno" valign="top"></td><td class="left">   R</td><td> </td><td class="right">   R</td><td class="lineno" valign="top"></td></tr>
    782       <tr><td><a name="diff0052" /></td></tr>
     633      <tr><td><a name="diff0043" /></td></tr>
    783634      <tr><td class="lineno" valign="top"></td><td class="lblock">      Range header field  <span class="delete">7</span></td><td> </td><td class="rblock">      Range header field  <span class="insert">6</span></td><td class="lineno" valign="top"></td></tr>
    784635      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
     
    794645
    795646     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
    796      <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 52 change blocks.&nbsp;</a></th></tr>
    797      <tr class="stats"><td></td><th><i>155 lines changed or deleted</i></th><th><i> </i></th><th><i>135 lines changed or added</i></th><td></td></tr>
     647     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 43 change blocks.&nbsp;</a></th></tr>
     648     <tr class="stats"><td></td><th><i>142 lines changed or deleted</i></th><th><i> </i></th><th><i>123 lines changed or added</i></th><td></td></tr>
    798649     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.38. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
    799650   </table>
  • draft-ietf-httpbis/latest/p5-range.html

    r2667 r2687  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 13, 2014";
     465       content: "Expires November 21, 2014";
    466466  }
    467467  @bottom-right {
     
    506506      <meta name="dct.creator" content="Reschke, J. F.">
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    508       <meta name="dct.issued" scheme="ISO8601" content="2014-05-12">
     508      <meta name="dct.issued" scheme="ISO8601" content="2014-05-20">
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    510510      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    532532            </tr>
    533533            <tr>
    534                <td class="left">Expires: November 13, 2014</td>
     534               <td class="left">Expires: November 21, 2014</td>
    535535               <td class="right">J. Reschke, Editor</td>
    536536            </tr>
     
    541541            <tr>
    542542               <td class="left"></td>
    543                <td class="right">May 12, 2014</td>
     543               <td class="right">May 20, 2014</td>
    544544            </tr>
    545545         </tbody>
     
    568568            in progress”.
    569569         </p>
    570          <p>This Internet-Draft will expire on November 13, 2014.</p>
     570         <p>This Internet-Draft will expire on November 21, 2014.</p>
    571571      </div>
    572572      <div id="rfc.copyrightnotice">
     
    687687            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#byte.ranges" class="smpl">bytes-unit</a>       = "bytes"
    688688</pre><div id="rule.ranges-specifier">
    689                <p id="rfc.section.2.1.p.3">        A byte range request can specify a single range of bytes, or a set of ranges within a single representation.</p>
     689               <p id="rfc.section.2.1.p.3">        A byte-range request can specify a single range of bytes or a set of ranges within a single representation.</p>
    690690            </div>
    691691            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#rule.ranges-specifier" class="smpl">byte-ranges-specifier</a> = <a href="#byte.ranges" class="smpl">bytes-unit</a> "=" <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a>
     
    734734            <p id="rfc.section.2.1.p.13">If a valid <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> includes at least one <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> with a <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> that is less than the current length of the representation, or at least one <a href="#rule.ranges-specifier" class="smpl">suffix-byte-range-spec</a> with a non-zero <a href="#rule.ranges-specifier" class="smpl">suffix-length</a>, then the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is satisfiable. Otherwise, the <a href="#rule.ranges-specifier" class="smpl">byte-range-set</a> is unsatisfiable.
    735735            </p>
    736             <p id="rfc.section.2.1.p.14">In the byte range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
     736            <p id="rfc.section.2.1.p.14">In the byte-range syntax, <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a>, <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a>, and <a href="#rule.ranges-specifier" class="smpl">suffix-length</a> are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients <em class="bcp14">MUST</em> anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
    737737            </p>
    738738         </div>
     
    805805               request to obtain the entire current representation.
    806806            </p>
    807             <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is: if the representation
    808                is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
     807            <p id="rfc.section.3.2.p.2">The "If-Range" header field allows a client to "short-circuit" the second request. Informally, its meaning is as follows:
     808               if the representation is unchanged, send me the part(s) that I am requesting in Range; otherwise, send me the entire representation.
    809809            </p>
    810810            <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  <a href="#header.if-range" class="smpl">If-Range</a> = <a href="#imported.abnf" class="smpl">entity-tag</a> / <a href="#imported.abnf" class="smpl">HTTP-date</a>
     
    840840
    841841... 26012 bytes of partial image data ...
    842 </pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single
    843                part responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
     842</pre><p id="rfc.section.4.1.p.4">If multiple parts are being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a "multipart/byteranges" payload, as defined in <a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>, and a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field containing the multipart/byteranges media type and its required boundary parameter. To avoid confusion with single-part
     843               responses, a server <em class="bcp14">MUST NOT</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field in the HTTP header section of a multiple part response (this field will be sent in each part instead).
    844844            </p>
    845845            <p id="rfc.section.4.1.p.5">Within the header area of each body part in the multipart payload, the server <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field corresponding to the range being enclosed in that body part. If the selected representation would have had a <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> header field in a <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a> response, the server <em class="bcp14">SHOULD</em> generate that same <a href="p2-semantics.html#header.content-type" class="smpl">Content-Type</a> field in the header area of each body part. For example:
     
    918918</pre><p id="rfc.section.4.2.p.9">A Content-Range field value is invalid if it contains a <a href="#header.content-range" class="smpl">byte-range-resp</a> that has a <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value less than its <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> value, or a <a href="#header.content-range" class="smpl">complete-length</a> value less than or equal to its <a href="#rule.ranges-specifier" class="smpl">last-byte-pos</a> value. The recipient of an invalid <a href="#header.content-range" class="smpl">Content-Range</a> <em class="bcp14">MUST NOT</em> attempt to recombine the received content with a stored representation.
    919919            </p>
    920             <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
     920            <p id="rfc.section.4.2.p.10">A server generating a <a href="#status.416" class="smpl">416 (Range Not Satisfiable)</a> response to a byte-range request <em class="bcp14">SHOULD</em> send a Content-Range header field with an <a href="#header.content-range" class="smpl">unsatisfied-range</a> value, as in the following example:
    921921            </p>
    922922            <div id="rfc.figure.u.22"></div><pre class="text">  Content-Range: bytes */1234
     
    967967            </p>
    968968            <p id="rfc.section.4.4.p.2">For byte ranges, failing to overlap the current extent means that the <a href="#rule.ranges-specifier" class="smpl">first-byte-pos</a> of all of the <a href="#rule.ranges-specifier" class="smpl">byte-range-spec</a> values were greater than the current length of the selected representation. When this status code is generated in response
    969                to a byte range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;4.2</a>).
     969               to a byte-range request, the sender <em class="bcp14">SHOULD</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the selected representation (<a href="#header.content-range" id="rfc.xref.header.content-range.2" title="Content-Range">Section&nbsp;4.2</a>).
    970970            </p>
    971971            <div id="rfc.figure.u.27"></div>
     
    984984         <div id="range.unit.registry">
    985985            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#range.unit.registry">Range Unit Registry</a></h2>
    986             <p id="rfc.section.5.1.p.1">The HTTP Range Unit Registry defines the namespace for the range unit names and refers to their corresponding specifications.
     986            <p id="rfc.section.5.1.p.1">The "HTTP Range Unit Registry" defines the namespace for the range unit names and refers to their corresponding specifications.
    987987               The registry will be created and maintained at (the suggested URI) &lt;<a href="http://www.iana.org/assignments/http-parameters">http://www.iana.org/assignments/http-parameters</a>&gt;.
    988988            </p>
     
    10011001            <div id="range.unit.registration">
    10021002               <h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a href="#range.unit.registration">Registrations</a></h3>
    1003                <p id="rfc.section.5.1.2.p.1">The initial HTTP Range Unit Registry shall contain the registrations below:</p>
     1003               <p id="rfc.section.5.1.2.p.1">The initial range unit registry contains the registrations below:</p>
    10041004               <div id="rfc.table.1">
    10051005                  <div id="iana.range.units.table"></div>
     
    10311031         <div id="status.code.registration">
    10321032            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
    1033             <p id="rfc.section.5.2.p.1">The "Hypertext Transfer Protocol (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; has been updated with the registrations below:
     1033            <p id="rfc.section.5.2.p.1">The "Hypertext Transfer Protocol (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; has been updated to include the registrations below:
    10341034            </p>
    10351035            <div id="rfc.table.2">
     
    10621062         <div id="header.field.registration">
    10631063            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
    1064             <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the "Message Headers" registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers/">http://www.iana.org/assignments/message-headers/</a>&gt;.
     1064            <p id="rfc.section.5.3.p.1">HTTP header fields are registered within the "Message Headers" registry maintained at &lt;<a href="http://www.iana.org/assignments/message-headers">http://www.iana.org/assignments/message-headers</a>&gt;.
    10651065            </p>
    10661066            <p id="rfc.section.5.3.p.2">This document defines the following HTTP header fields, so the "Permanent Message Header Field Names" registry has been updated
     
    11161116            <p id="rfc.section.5.4.p.1">IANA maintains the registry of Internet media types <a href="#BCP13" id="rfc.xref.BCP13.1"><cite title="Media Type Specifications and Registration Procedures">[BCP13]</cite></a> at &lt;<a href="http://www.iana.org/assignments/media-types">http://www.iana.org/assignments/media-types</a>&gt;.
    11171117            </p>
    1118             <p id="rfc.section.5.4.p.2">This document serves as the specification for the Internet media type "multipart/byteranges". The following is to be registered
     1118            <p id="rfc.section.5.4.p.2">This document serves as the specification for the Internet media type "multipart/byteranges". The following has been registered
    11191119               with IANA.
    11201120            </p>
  • draft-ietf-httpbis/latest/p5-range.xml

    r2667 r2687  
    229229  <x:anchor-alias value="suffix-byte-range-spec"/>
    230230  <x:anchor-alias value="suffix-length"/>
    231    A byte range request can specify a single range of bytes, or a set
     231   A byte-range request can specify a single range of bytes or a set
    232232   of ranges within a single representation.
    233233</t>
     
    322322</t>
    323323<t>
    324    In the byte range syntax, <x:ref>first-byte-pos</x:ref>,
     324   In the byte-range syntax, <x:ref>first-byte-pos</x:ref>,
    325325   <x:ref>last-byte-pos</x:ref>, and <x:ref>suffix-length</x:ref> are
    326326   expressed as decimal number of octets. Since there is no predefined limit
     
    469469<t>
    470470   The "If-Range" header field allows a client to "short-circuit" the second
    471    request. Informally, its meaning is: if the representation is unchanged,
     471   request. Informally, its meaning is as follows: if the representation is unchanged,
    472472   send me the part(s) that I am requesting in Range; otherwise, send me the
    473473   entire representation.
     
    551551   <x:ref>Content-Type</x:ref> header field containing the
    552552   multipart/byteranges media type and its required boundary parameter.
    553    To avoid confusion with single part responses, a server &MUST-NOT; generate
     553   To avoid confusion with single-part responses, a server &MUST-NOT; generate
    554554   a <x:ref>Content-Range</x:ref> header field in the HTTP header section of a
    555555   multiple part response (this field will be sent in each part instead).
     
    710710<t>
    711711   A server generating a <x:ref>416 (Range Not Satisfiable)</x:ref> response
    712    to a byte range request &SHOULD; send a Content-Range header field with an
     712   to a byte-range request &SHOULD; send a Content-Range header field with an
    713713   <x:ref>unsatisfied-range</x:ref> value, as in the following example:
    714714</t>
     
    823823   <x:ref>first-byte-pos</x:ref> of all of the <x:ref>byte-range-spec</x:ref>
    824824   values were greater than the current length of the selected representation.
    825    When this status code is generated in response to a byte range request, the
     825   When this status code is generated in response to a byte-range request, the
    826826   sender &SHOULD; generate a <x:ref>Content-Range</x:ref> header field
    827827   specifying the current length of the selected representation
     
    855855<section title="Range Unit Registry" anchor="range.unit.registry">
    856856<t>
    857    The HTTP Range Unit Registry defines the namespace for the range
     857   The "HTTP Range Unit Registry" defines the namespace for the range
    858858   unit names and refers to their corresponding specifications.
    859859   The registry will be created and maintained at (the suggested URI)
     
    878878<section title="Registrations" anchor="range.unit.registration">
    879879<t>
    880    The initial HTTP Range Unit Registry shall contain the registrations
     880   The initial range unit registry contains the registrations
    881881   below:
    882882</t>
     
    903903<t>
    904904   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
    905    has been updated with the registrations below:
     905   has been updated to include the registrations below:
    906906</t>
    907907<?BEGININC p5-range.iana-status-codes ?>
     
    930930   HTTP header fields are registered within the "Message Headers" registry
    931931   maintained at
    932    <eref target="http://www.iana.org/assignments/message-headers/"/>.
     932   <eref target="http://www.iana.org/assignments/message-headers"/>.
    933933</t>
    934934<t>
     
    984984<t>
    985985   This document serves as the specification for the Internet media type
    986    "multipart/byteranges". The following is to be registered with
     986   "multipart/byteranges". The following has been registered with
    987987   IANA.
    988988</t>
Note: See TracChangeset for help on using the changeset viewer.