source: draft-ietf-httpbis/latest/auth48/rfc7233.abdiff.txt @ 2688

Last change on this file since 2688 was 2688, checked in by julian.reschke@…, 6 years ago

editorial fixes (#553)
  • Property svn:eol-style set to native
File size: 20.2 KB
Line 
1
2INTRODUCTION, paragraph 1:
3OLD:
4
5 HTTPbis Working Group                                   R. Fielding, Ed.
6 Internet-Draft                                                     Adobe
7 Obsoletes: 2616 (if approved)                              Y. Lafon, Ed.
8 Intended status: Standards Track                                     W3C
9 Expires: November 22, 2014                               J. Reschke, Ed.
10                                                               greenbytes
11                                                             May 21, 2014
12
13NEW:
14
15 Internet Engineering Task Force (IETF)                  R. Fielding, Ed.
16 Request for Comments: 7233                                         Adobe
17 Obsoletes: 2616                                            Y. Lafon, Ed.
18 Category: Standards Track                                            W3C
19 ISSN: 2070-1721                                          J. Reschke, Ed.
20                                                               greenbytes
21                                                                 May 2014
22
23
24INTRODUCTION, paragraph 2:
25OLD:
26
27          Hypertext Transfer Protocol (HTTP/1.1): Range Requests
28                    draft-ietf-httpbis-p5-range-latest
29
30NEW:
31
32          Hypertext Transfer Protocol (HTTP/1.1): Range Requests
33
34
35INTRODUCTION, paragraph 5:
36OLD:
37
38 Editorial Note (To be removed by RFC Editor)
39 
40    Discussion of this draft takes place on the HTTPBIS working group
41    mailing list (ietf-http-wg@w3.org), which is archived at
42    <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
43 
44    The current issues list is at
45    <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
46    documents (including fancy diffs) can be found at
47    <http://tools.ietf.org/wg/httpbis/>.
48 
49    _This is a temporary document for the purpose of tracking the
50    editorial changes made during the AUTH48 (RFC publication) phase._
51 
52 Status of This Memo
53
54NEW:
55
56 Status of This Memo
57
58
59INTRODUCTION, paragraph 6:
60OLD:
61
62    This Internet-Draft is submitted in full conformance with the
63    provisions of BCP 78 and BCP 79.
64
65NEW:
66
67    This is an Internet Standards Track document.
68
69
70INTRODUCTION, paragraph 7:
71OLD:
72
73    Internet-Drafts are working documents of the Internet Engineering
74    Task Force (IETF).  Note that other groups may also distribute
75    working documents as Internet-Drafts.  The list of current Internet-
76    Drafts is at http://datatracker.ietf.org/drafts/current/.
77
78NEW:
79
80    This document is a product of the Internet Engineering Task Force
81    (IETF).  It represents the consensus of the IETF community.  It has
82    received public review and has been approved for publication by the
83    Internet Engineering Steering Group (IESG).  Further information on
84    Internet Standards is available in Section 2 of RFC 5741.
85
86
87INTRODUCTION, paragraph 8:
88OLD:
89
90    Internet-Drafts are draft documents valid for a maximum of six months
91    and may be updated, replaced, or obsoleted by other documents at any
92    time.  It is inappropriate to use Internet-Drafts as reference
93    material or to cite them other than as "work in progress."
94    This Internet-Draft will expire on November 22, 2014.
95
96NEW:
97
98    Information about the current status of this document, any errata,
99    and how to provide feedback on it may be obtained at
100    http://www.rfc-editor.org/info/rfc7233.
101
102
103INTRODUCTION, paragraph 14:
104OLD:
105
106    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
107      1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  4
108      1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  4
109    2.  Range Units  . . . . . . . . . . . . . . . . . . . . . . . . .  4
110      2.1.  Byte Ranges  . . . . . . . . . . . . . . . . . . . . . . .  5
111      2.2.  Other Range Units  . . . . . . . . . . . . . . . . . . . .  7
112      2.3.  Accept-Ranges  . . . . . . . . . . . . . . . . . . . . . .  7
113    3.  Range Requests . . . . . . . . . . . . . . . . . . . . . . . .  7
114      3.1.  Range  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
115      3.2.  If-Range . . . . . . . . . . . . . . . . . . . . . . . . .  9
116    4.  Responses to a Range Request . . . . . . . . . . . . . . . . . 10
117      4.1.  206 Partial Content  . . . . . . . . . . . . . . . . . . . 10
118      4.2.  Content-Range  . . . . . . . . . . . . . . . . . . . . . . 12
119      4.3.  Combining Ranges . . . . . . . . . . . . . . . . . . . . . 14
120      4.4.  416 Range Not Satisfiable  . . . . . . . . . . . . . . . . 15
121    5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 15
122      5.1.  Range Unit Registry  . . . . . . . . . . . . . . . . . . . 15
123        5.1.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 15
124        5.1.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 16
125      5.2.  Status Code Registration . . . . . . . . . . . . . . . . . 16
126      5.3.  Header Field Registration  . . . . . . . . . . . . . . . . 16
127      5.4.  Internet Media Type Registration . . . . . . . . . . . . . 17
128        5.4.1.  Internet Media Type multipart/byteranges . . . . . . . 17
129    6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 18
130      6.1.  Denial-of-Service Attacks Using Range  . . . . . . . . . . 18
131    7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 18
132    8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
133      8.1.  Normative References . . . . . . . . . . . . . . . . . . . 19
134      8.2.  Informative References . . . . . . . . . . . . . . . . . . 19
135    Appendix A.  Internet Media Type multipart/byteranges  . . . . . . 20
136    Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 21
137    Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 21
138    Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 21
139    Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
140
141NEW:
142
143    1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
144      1.1.  Conformance and Error Handling . . . . . . . . . . . . . .  3
145      1.2.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  3
146    2.  Range Units  . . . . . . . . . . . . . . . . . . . . . . . . .  3
147      2.1.  Byte Ranges  . . . . . . . . . . . . . . . . . . . . . . .  4
148      2.2.  Other Range Units  . . . . . . . . . . . . . . . . . . . .  6
149      2.3.  Accept-Ranges  . . . . . . . . . . . . . . . . . . . . . .  6
150    3.  Range Requests . . . . . . . . . . . . . . . . . . . . . . . .  6
151      3.1.  Range  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
152      3.2.  If-Range . . . . . . . . . . . . . . . . . . . . . . . . .  8
153    4.  Responses to a Range Request . . . . . . . . . . . . . . . . .  9
154      4.1.  206 Partial Content  . . . . . . . . . . . . . . . . . . .  9
155      4.2.  Content-Range  . . . . . . . . . . . . . . . . . . . . . . 11
156      4.3.  Combining Ranges . . . . . . . . . . . . . . . . . . . . . 13
157      4.4.  416 Range Not Satisfiable  . . . . . . . . . . . . . . . . 14
158    5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 14
159      5.1.  Range Unit Registry  . . . . . . . . . . . . . . . . . . . 14
160        5.1.1.  Procedure  . . . . . . . . . . . . . . . . . . . . . . 14
161        5.1.2.  Registrations  . . . . . . . . . . . . . . . . . . . . 15
162      5.2.  Status Code Registration . . . . . . . . . . . . . . . . . 15
163      5.3.  Header Field Registration  . . . . . . . . . . . . . . . . 15
164      5.4.  Internet Media Type Registration . . . . . . . . . . . . . 16
165        5.4.1.  Internet Media Type multipart/byteranges . . . . . . . 16
166    6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
167      6.1.  Denial-of-Service Attacks Using Range  . . . . . . . . . . 17
168    7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 17
169    8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 18
170      8.1.  Normative References . . . . . . . . . . . . . . . . . . . 18
171      8.2.  Informative References . . . . . . . . . . . . . . . . . . 18
172    Appendix A.  Internet Media Type multipart/byteranges  . . . . . . 19
173    Appendix B.  Changes from RFC 2616 . . . . . . . . . . . . . . . . 20
174    Appendix C.  Imported ABNF . . . . . . . . . . . . . . . . . . . . 20
175    Appendix D.  Collected ABNF  . . . . . . . . . . . . . . . . . . . 20
176    Index  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
177
178
179Section 1., paragraph 2:
180OLD:
181
182    This document defines HTTP/1.1 range requests, partial responses, and
183    the multipart/byteranges media type.  Range requests are an OPTIONAL
184    feature of HTTP, designed so that recipients not implementing this
185    feature (or not supporting it for the target resource) can respond as
186    if it is a normal GET request without impacting interoperability.
187    Partial responses are indicated by a distinct status code to not be
188    mistaken for full responses by caches that might not implement the
189    feature.
190
191NEW:
192
193    This document defines HTTP/1.1 range requests, partial responses, and
194    the multipart/byteranges media type.  Range requests are an OPTIONAL
195    feature of HTTP, designed so that recipients not implementing this
196    feature (or not supporting it for the target resource) can respond as
197    if it is a normal GET request without impacting interoperability.
198    Partial responses are indicated by a distinct status code not to be
199    mistaken for full responses by caches that might not implement the
200    feature.
201
202
203Section 3.2., paragraph 4:
204OLD:
205
206    A client MUST NOT generate an If-Range header field in a request that
207    does not contain a Range header field.  A server MUST ignore an If-
208    Range header field received in a request that does not contain a
209    Range header field.  An origin server MUST ignore an If-Range header
210    field received in a request for a target resource that does not
211    support Range requests.
212
213NEW:
214
215    A client MUST NOT generate an If-Range header field in a request that
216    does not contain a Range header field.  A server MUST ignore an
217    If-Range header field received in a request that does not contain a
218    Range header field.  An origin server MUST ignore an If-Range header
219    field received in a request for a target resource that does not
220    support Range requests.
221
222
223Section 3.2., paragraph 7:
224OLD:
225
226    If the validator given in the If-Range header field matches the
227    current validator for the selected representation of the target
228    resource, then the server SHOULD process the Range header field as
229    requested.  If the validator does not match, the server MUST ignore
230    the Range header field.  Note that this comparison by exact match,
231    including when the validator is an HTTP-date, differs from the
232    "earlier than or equal to" comparison used when evaluating an If-
233    Unmodified-Since conditional.
234
235NEW:
236
237    If the validator given in the If-Range header field matches the
238    current validator for the selected representation of the target
239    resource, then the server SHOULD process the Range header field as
240    requested.  If the validator does not match, the server MUST ignore
241    the Range header field.  Note that this comparison by exact match,
242    including when the validator is an HTTP-date, differs from the
243    "earlier than or equal to" comparison used when evaluating an
244    If-Unmodified-Since conditional.
245
246
247Section 4.3., paragraph 3:
248OLD:
249
250    If the most recent response is an incomplete 200 (OK) response, then
251    the header fields of that response are used for any combined response
252    and replace those of the matching stored responses.
253
254NEW:
255
256    If the most recent response is an incomplete 200 (OK) response, then
257    the header fields of that response are used for any combined response
258    and they replace those of the matching stored responses.
259
260
261Section 5.1., paragraph 1:
262OLD:
263
264    The "HTTP Range Unit Registry" defines the namespace for the range
265    unit names and refers to their corresponding specifications.  The
266    registry has been created and is now maintained at
267    <http://www.iana.org/assignments/http-parameters>.
268
269NEW:
270
271    The "HTTP Range Unit Registry" defines the namespace for the range
272    unit names and refers to their corresponding specifications.  The
273    registry will be created and maintained at
274    <http://www.iana.org/assignments/http-parameters>.
275
276
277Section 5.1.2., paragraph 1:
278OLD:
279
280    The initial range unit registry contains the registrations below:
281
282NEW:
283
284    The initial "HTTP Range Unit Registry" contains the registrations
285    below:
286
287
288Section 5.3., paragraph 2:
289OLD:
290
291    This document defines the following HTTP header fields, so the
292    "Permanent Message Header Field Names" registry has been updated
293    accordingly (see [BCP90]).
294
295NEW:
296
297    This document defines the following HTTP header fields; their
298    associated registry entries have been updated according to the
299    permanent registrations below (see [BCP90]):
300
301
302Section 5.4.1., paragraph 16:
303OLD:
304
305    Person and email address to contact for further information:  See
306       Authors' Addresses Section.
307
308NEW:
309
310    Person and email address to contact for further information:
311       See Authors' Addresses section of RFC 7233.
312
313
314Section 5.4.1., paragraph 19:
315OLD:
316
317    Author:  See Authors' Addresses Section.
318
319NEW:
320
321    Author:  See Authors Section.
322
323
324Section 8.1., paragraph 4:
325OLD:
326
327    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
328               Protocol (HTTP/1.1): Message Syntax and Routing",
329               draft-ietf-httpbis-p1-messaging-latest (work in progress),
330               May 2014.
331
332NEW:
333
334    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
335               Protocol (HTTP/1.1): Message Syntax and Routing",
336               RFC 7230, May 2014.
337
338
339Section 8.1., paragraph 5:
340OLD:
341
342    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
343               Protocol (HTTP/1.1): Semantics and Content",
344               draft-ietf-httpbis-p2-semantics-latest (work in progress),
345               May 2014.
346
347NEW:
348
349    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
350               Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
351               May 2014.
352
353
354Section 8.1., paragraph 6:
355OLD:
356
357    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
358               Protocol (HTTP/1.1): Conditional Requests",
359               draft-ietf-httpbis-p4-conditional-latest (work in
360               progress), May 2014.
361
362NEW:
363
364    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
365               Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
366               May 2014.
367
368
369Section 8.1., paragraph 7:
370OLD:
371
372    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
373               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
374               draft-ietf-httpbis-p6-cache-latest (work in progress),
375               May 2014.
376
377NEW:
378
379    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
380               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
381               RFC 7234, May 2014.
382
383
384Section 2., paragraph 1:
385OLD:
386
387    3.  A number of clients and servers were coded to an early draft of
388        the byteranges specification that used a media type of multipart/
389        x-byteranges, which is almost (but not quite) compatible with
390        this type.
391
392NEW:
393
394    3.  A number of clients and servers were coded to an early draft
395        version of the byteranges specification that used a media type of
396        multipart/x-byteranges, which is almost (but not quite)
397        compatible with this type.
398
399
400Appendix B., paragraph 1:
401OLD:
402
403    Servers are given more leeway in how they respond to a range request,
404    in order to mitigate abuse by malicious (or just greedy) clients.
405    (Section 3.1)
406
407NEW:
408
409    Servers are given more leeway in how they respond to a range request,
410    in order to mitigate abuse by malicious (or just greedy) clients
411    (Section 3.1).
412
413
414Appendix B., paragraph 2:
415OLD:
416
417    A weak validator cannot be used in a 206 response.  (Section 4.1)
418
419NEW:
420
421    A weak validator cannot be used in a 206 response (Section 4.1).
422
423
424Appendix B., paragraph 3:
425OLD:
426
427    The Content-Range header field only has meaning when the status code
428    explicitly defines its use.  (Section 4.2)
429
430NEW:
431
432    The Content-Range header field only has meaning when the status code
433    explicitly defines its use (Section 4.2).
434
435
436Appendix B., paragraph 4:
437OLD:
438
439    This specification introduces a Range Unit Registry.  (Section 5.1)
440
441NEW:
442
443    This specification introduces a the "HTTP Range Unit Registry"
444    (Section 5.1).
445
446
447Appendix B., paragraph 5:
448OLD:
449
450    multipart/byteranges can consist of a single part.  (Appendix A)
451
452NEW:
453
454    multipart/byteranges can consist of a single part (Appendix A).
455
456
457Appendix C., paragraph 4:
458OLD:
459
460      OWS        = <OWS, see [RFC7230], Section 3.2.3>
461      token      = <token, see [RFC7230], Section 3.2.6>
462
463NEW:
464
465      OWS        = <OWS, defined in [RFC7230], Section 3.2.3>
466      token      = <token, defined in [RFC7230], Section 3.2.6>
467
468
469Appendix C., paragraph 6:
470OLD:
471
472      HTTP-date  = <HTTP-date, see [RFC7231], Section 7.1.1.1>
473      entity-tag = <entity-tag, see [RFC7232], Section 2.3>
474
475NEW:
476
477      HTTP-date  = <HTTP-date, defined in [RFC7231], Section 7.1.1.1>
478      entity-tag = <entity-tag, defined in [RFC7232], Section 2.3>
479
480
481Section 1.2, paragraph 3:
482OLD:
483
484    HTTP-date = <HTTP-date, see [RFC7231], Section 7.1.1.1>
485
486NEW:
487
488    HTTP-date = <HTTP-date, defined in [RFC7231], Section 7.1.1.1>
489
490
491Section 1.2, paragraph 5:
492OLD:
493
494    OWS = <OWS, see [RFC7230], Section 3.2.3>
495
496NEW:
497
498    OWS = <OWS, defined in [RFC7230], Section 3.2.3>
499
500
501Section 1.2, paragraph 10:
502OLD:
503
504    entity-tag = <entity-tag, see [RFC7232], Section 2.3>
505
506NEW:
507
508    entity-tag = <entity-tag, defined in [RFC7232], Section 2.3>
509
510
511Section 1.2, paragraph 16:
512OLD:
513
514    token = <token, see [RFC7230], Section 3.2.6>
515
516NEW:
517
518    token = <token, defined in [RFC7230], Section 3.2.6>
519
520
521Section 1.2, paragraph 19:
522OLD:
523
524    2
525       206 Partial Content (status code)  10
526
527NEW:
528
529    2
530       206 Partial Content (status code)  9
531
532
533Section 1.2, paragraph 20:
534OLD:
535
536    4
537       416 Range Not Satisfiable (status code)  15
538
539NEW:
540
541    4
542       416 Range Not Satisfiable (status code)  14
543
544
545Section 1.2, paragraph 21:
546OLD:
547
548    A
549       Accept-Ranges header field  7
550
551NEW:
552
553    A
554       Accept-Ranges header field  6
555
556
557Section 1.2, paragraph 22:
558OLD:
559
560    C
561       Content-Range header field  12
562
563NEW:
564
565    C
566       Content-Range header field  11
567
568
569Section 1.2, paragraph 23:
570OLD:
571
572    G
573       Grammar
574          Accept-Ranges  7
575          acceptable-ranges  7
576          byte-content-range  12
577          byte-range  12
578          byte-range-resp  12
579          byte-range-set  5
580          byte-range-spec  5
581          byte-ranges-specifier  5
582          bytes-unit  5
583          complete-length  12
584          Content-Range  12
585          first-byte-pos  5
586          If-Range  9
587          last-byte-pos  5
588          other-content-range  12
589          other-range-resp  12
590          other-range-unit  5, 7
591          Range  7
592          range-unit  5
593          ranges-specifier  5
594          suffix-byte-range-spec  6
595          suffix-length  6
596          unsatisfied-range  12
597
598NEW:
599
600    G
601       Grammar
602          Accept-Ranges  6
603          acceptable-ranges  6
604          byte-content-range  11
605          byte-range  11
606          byte-range-resp  11
607          byte-range-set  4
608          byte-range-spec  4
609          byte-ranges-specifier  4
610          bytes-unit  4
611          complete-length  11
612          Content-Range  11
613          first-byte-pos  4
614          If-Range  8
615          last-byte-pos  4
616          other-content-range  11
617          other-range-resp  11
618          other-range-unit  4, 6
619          Range  6
620          range-unit  4
621          ranges-specifier  4
622          suffix-byte-range-spec  5
623          suffix-length  5
624          unsatisfied-range  11
625
626
627Section 1.2, paragraph 24:
628OLD:
629
630    I
631       If-Range header field  9
632
633NEW:
634
635    I
636       If-Range header field  8
637
638
639Section 1.2, paragraph 25:
640OLD:
641
642    M
643       Media Type
644          multipart/byteranges  17, 20
645          multipart/x-byteranges  20
646       multipart/byteranges Media Type  17, 20
647       multipart/x-byteranges Media Type  20
648
649NEW:
650
651    M
652       Media Type
653          multipart/byteranges  16, 19
654          multipart/x-byteranges  19
655       multipart/byteranges Media Type  16, 19
656       multipart/x-byteranges Media Type  19
657
658
659Section 1.2, paragraph 26:
660OLD:
661
662    R
663       Range header field  7
664
665NEW:
666
667    R
668       Range header field  6
669
Note: See TracBrowser for help on using the repository browser.