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

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

editorial fixes (#553)

  • Property svn:eol-style set to native
File size: 20.9 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 21, 2014                               J. Reschke, Ed.
10                                                               greenbytes
11                                                             May 20, 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 21, 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.2., paragraph 17:
248OLD:
249
250    The "Content-Range" header field has no meaning for status codes that
251    do not explicitly describe its semantic.  For this specification,
252    only the 206 (Partial Content) and 416 (Range Not Satisfiable) status
253    codes describe a meaning for Content-Range.
254
255NEW:
256
257    The Content-Range header field has no meaning for status codes that
258    do not explicitly describe its semantic.  For this specification,
259    only the 206 (Partial Content) and 416 (Range Not Satisfiable) status
260    codes describe a meaning for Content-Range.
261
262
263Section 4.3., paragraph 3:
264OLD:
265
266    If the most recent response is an incomplete 200 (OK) response, then
267    the header fields of that response are used for any combined response
268    and replace those of the matching stored responses.
269
270NEW:
271
272    If the most recent response is an incomplete 200 (OK) response, then
273    the header fields of that response are used for any combined response
274    and they replace those of the matching stored responses.
275
276
277Section 5.1., paragraph 1:
278OLD:
279
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)
283    <http://www.iana.org/assignments/http-parameters>.
284
285NEW:
286
287    The "HTTP Range Unit Registry" defines the namespace for the range
288    unit names and refers to their corresponding specifications.  The
289    registry will be created and maintained at
290    <http://www.iana.org/assignments/http-parameters>.
291
292
293Section 5.1.2., paragraph 1:
294OLD:
295
296    The initial range unit registry contains the registrations below:
297
298NEW:
299
300    The initial "HTTP Range Unit Registry" contains the registrations
301    below:
302
303
304Section 5.3., paragraph 2:
305OLD:
306
307    This document defines the following HTTP header fields, so the
308    "Permanent Message Header Field Names" registry has been updated
309    accordingly (see [BCP90]).
310
311NEW:
312
313    This document defines the following HTTP header fields; their
314    associated registry entries have been updated according to the
315    permanent registrations below (see [BCP90]):
316
317
318Section 5.4.1., paragraph 16:
319OLD:
320
321    Person and email address to contact for further information:  See
322       Authors' Addresses Section.
323
324NEW:
325
326    Person and email address to contact for further information:
327       See Authors' Addresses section of RFC 7233.
328
329
330Section 5.4.1., paragraph 19:
331OLD:
332
333    Author:  See Authors' Addresses Section.
334
335NEW:
336
337    Author:  See Authors Section.
338
339
340Section 6., paragraph 2:
341OLD:
342
343 6.1.  Denial of Service Attacks using Range
344
345NEW:
346
347 6.1.  Denial-of-Service Attacks Using Range
348
349
350Section 8.1., paragraph 4:
351OLD:
352
353    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
354               Protocol (HTTP/1.1): Message Syntax and Routing",
355               draft-ietf-httpbis-p1-messaging-latest (work in progress),
356               May 2014.
357
358NEW:
359
360    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
361               Protocol (HTTP/1.1): Message Syntax and Routing",
362               RFC 7230, May 2014.
363
364
365Section 8.1., paragraph 5:
366OLD:
367
368    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
369               Protocol (HTTP/1.1): Semantics and Content",
370               draft-ietf-httpbis-p2-semantics-latest (work in progress),
371               May 2014.
372
373NEW:
374
375    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
376               Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
377               May 2014.
378
379
380Section 8.1., paragraph 6:
381OLD:
382
383    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
384               Protocol (HTTP/1.1): Conditional Requests",
385               draft-ietf-httpbis-p4-conditional-latest (work in
386               progress), May 2014.
387
388NEW:
389
390    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
391               Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
392               May 2014.
393
394
395Section 8.1., paragraph 7:
396OLD:
397
398    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
399               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
400               draft-ietf-httpbis-p6-cache-latest (work in progress),
401               May 2014.
402
403NEW:
404
405    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
406               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
407               RFC 7234, May 2014.
408
409
410Section 2., paragraph 1:
411OLD:
412
413    3.  A number of clients and servers were coded to an early draft of
414        the byteranges specification that used a media type of multipart/
415        x-byteranges, which is almost (but not quite) compatible with
416        this type.
417
418NEW:
419
420    3.  A number of clients and servers were coded to an early draft
421        version of the byteranges specification that used a media type of
422        multipart/x-byteranges, which is almost (but not quite)
423        compatible with this type.
424
425
426Appendix B., paragraph 1:
427OLD:
428
429    Servers are given more leeway in how they respond to a range request,
430    in order to mitigate abuse by malicious (or just greedy) clients.
431    (Section 3.1)
432
433NEW:
434
435    Servers are given more leeway in how they respond to a range request,
436    in order to mitigate abuse by malicious (or just greedy) clients
437    (Section 3.1).
438
439
440Appendix B., paragraph 2:
441OLD:
442
443    A weak validator cannot be used in a 206 response.  (Section 4.1)
444
445NEW:
446
447    A weak validator cannot be used in a 206 response (Section 4.1).
448
449
450Appendix B., paragraph 3:
451OLD:
452
453    The Content-Range header field only has meaning when the status code
454    explicitly defines its use.  (Section 4.2)
455
456NEW:
457
458    The Content-Range header field only has meaning when the status code
459    explicitly defines its use (Section 4.2).
460
461
462Appendix B., paragraph 4:
463OLD:
464
465    This specification introduces a Range Unit Registry.  (Section 5.1)
466
467NEW:
468
469    This specification introduces a the "HTTP Range Unit Registry"
470    (Section 5.1).
471
472
473Appendix B., paragraph 5:
474OLD:
475
476    multipart/byteranges can consist of a single part.  (Appendix A)
477
478NEW:
479
480    multipart/byteranges can consist of a single part (Appendix A).
481
482
483Appendix C., paragraph 4:
484OLD:
485
486      OWS        = <OWS, see [RFC7230], Section 3.2.3>
487      token      = <token, see [RFC7230], Section 3.2.6>
488
489NEW:
490
491      OWS        = <OWS, defined in [RFC7230], Section 3.2.3>
492      token      = <token, defined in [RFC7230], Section 3.2.6>
493
494
495Appendix C., paragraph 6:
496OLD:
497
498      HTTP-date  = <HTTP-date, see [RFC7231], Section 7.1.1.1>
499      entity-tag = <entity-tag, see [RFC7232], Section 2.3>
500
501NEW:
502
503      HTTP-date  = <HTTP-date, defined in [RFC7231], Section 7.1.1.1>
504      entity-tag = <entity-tag, defined in [RFC7232], Section 2.3>
505
506
507Section 1.2, paragraph 3:
508OLD:
509
510    HTTP-date = <HTTP-date, see [RFC7231], Section 7.1.1.1>
511
512NEW:
513
514    HTTP-date = <HTTP-date, defined in [RFC7231], Section 7.1.1.1>
515
516
517Section 1.2, paragraph 5:
518OLD:
519
520    OWS = <OWS, see [RFC7230], Section 3.2.3>
521
522NEW:
523
524    OWS = <OWS, defined in [RFC7230], Section 3.2.3>
525
526
527Section 1.2, paragraph 10:
528OLD:
529
530    entity-tag = <entity-tag, see [RFC7232], Section 2.3>
531
532NEW:
533
534    entity-tag = <entity-tag, defined in [RFC7232], Section 2.3>
535
536
537Section 1.2, paragraph 16:
538OLD:
539
540    token = <token, see [RFC7230], Section 3.2.6>
541
542NEW:
543
544    token = <token, defined in [RFC7230], Section 3.2.6>
545
546
547Section 1.2, paragraph 19:
548OLD:
549
550    2
551       206 Partial Content (status code)  10
552
553NEW:
554
555    2
556       206 Partial Content (status code)  9
557
558
559Section 1.2, paragraph 20:
560OLD:
561
562    4
563       416 Range Not Satisfiable (status code)  15
564
565NEW:
566
567    4
568       416 Range Not Satisfiable (status code)  14
569
570
571Section 1.2, paragraph 21:
572OLD:
573
574    A
575       Accept-Ranges header field  7
576
577NEW:
578
579    A
580       Accept-Ranges header field  6
581
582
583Section 1.2, paragraph 22:
584OLD:
585
586    C
587       Content-Range header field  12
588
589NEW:
590
591    C
592       Content-Range header field  11
593
594
595Section 1.2, paragraph 23:
596OLD:
597
598    G
599       Grammar
600          Accept-Ranges  7
601          acceptable-ranges  7
602          byte-content-range  12
603          byte-range  12
604          byte-range-resp  12
605          byte-range-set  5
606          byte-range-spec  5
607          byte-ranges-specifier  5
608          bytes-unit  5
609          complete-length  12
610          Content-Range  12
611          first-byte-pos  5
612          If-Range  9
613          last-byte-pos  5
614          other-content-range  12
615          other-range-resp  12
616          other-range-unit  5, 7
617          Range  7
618          range-unit  5
619          ranges-specifier  5
620          suffix-byte-range-spec  6
621          suffix-length  6
622          unsatisfied-range  12
623
624NEW:
625
626    G
627       Grammar
628          Accept-Ranges  6
629          acceptable-ranges  6
630          byte-content-range  11
631          byte-range  11
632          byte-range-resp  11
633          byte-range-set  4
634          byte-range-spec  4
635          byte-ranges-specifier  4
636          bytes-unit  4
637          complete-length  11
638          Content-Range  11
639          first-byte-pos  4
640          If-Range  8
641          last-byte-pos  4
642          other-content-range  11
643          other-range-resp  11
644          other-range-unit  4, 6
645          Range  6
646          range-unit  4
647          ranges-specifier  4
648          suffix-byte-range-spec  5
649          suffix-length  5
650          unsatisfied-range  11
651
652
653Section 1.2, paragraph 24:
654OLD:
655
656    I
657       If-Range header field  9
658
659NEW:
660
661    I
662       If-Range header field  8
663
664
665Section 1.2, paragraph 25:
666OLD:
667
668    M
669       Media Type
670          multipart/byteranges  17, 20
671          multipart/x-byteranges  20
672       multipart/byteranges Media Type  17, 20
673       multipart/x-byteranges Media Type  20
674
675NEW:
676
677    M
678       Media Type
679          multipart/byteranges  16, 19
680          multipart/x-byteranges  19
681       multipart/byteranges Media Type  16, 19
682       multipart/x-byteranges Media Type  19
683
684
685Section 1.2, paragraph 26:
686OLD:
687
688    R
689       Range header field  7
690
691NEW:
692
693    R
694       Range header field  6
695
Note: See TracBrowser for help on using the repository browser.