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

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

Consistently say "Authors .. section" (#553)

  • Property svn:eol-style set to native
File size: 14.4 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 29, 2014                               J. Reschke, Ed.
10                                                               greenbytes
11                                                             May 28, 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 29, 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 3.2., paragraph 4:
180OLD:
181
182    A client MUST NOT generate an If-Range header field in a request that
183    does not contain a Range header field.  A server MUST ignore an If-
184    Range header field received in a request that does not contain a
185    Range header field.  An origin server MUST ignore an If-Range header
186    field received in a request for a target resource that does not
187    support Range requests.
188
189NEW:
190
191    A client MUST NOT generate an If-Range header field in a request that
192    does not contain a Range header field.  A server MUST ignore an
193    If-Range header field received in a request that does not contain a
194    Range header field.  An origin server MUST ignore an If-Range header
195    field received in a request for a target resource that does not
196    support Range requests.
197
198
199Section 3.2., paragraph 7:
200OLD:
201
202    If the validator given in the If-Range header field matches the
203    current validator for the selected representation of the target
204    resource, then the server SHOULD process the Range header field as
205    requested.  If the validator does not match, the server MUST ignore
206    the Range header field.  Note that this comparison by exact match,
207    including when the validator is an HTTP-date, differs from the
208    "earlier than or equal to" comparison used when evaluating an If-
209    Unmodified-Since conditional.
210
211NEW:
212
213    If the validator given in the If-Range header field matches the
214    current validator for the selected representation of the target
215    resource, then the server SHOULD process the Range header field as
216    requested.  If the validator does not match, the server MUST ignore
217    the Range header field.  Note that this comparison by exact match,
218    including when the validator is an HTTP-date, differs from the
219    "earlier than or equal to" comparison used when evaluating an
220    If-Unmodified-Since conditional.
221
222
223Section 8.1., paragraph 4:
224OLD:
225
226    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
227               Protocol (HTTP/1.1): Message Syntax and Routing",
228               draft-ietf-httpbis-p1-messaging-latest (work in progress),
229               May 2014.
230
231NEW:
232
233    [RFC7230]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
234               Protocol (HTTP/1.1): Message Syntax and Routing",
235               RFC 7230, May 2014.
236
237
238Section 8.1., paragraph 5:
239OLD:
240
241    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
242               Protocol (HTTP/1.1): Semantics and Content",
243               draft-ietf-httpbis-p2-semantics-latest (work in progress),
244               May 2014.
245
246NEW:
247
248    [RFC7231]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
249               Protocol (HTTP/1.1): Semantics and Content", RFC 7231,
250               May 2014.
251
252
253Section 8.1., paragraph 6:
254OLD:
255
256    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
257               Protocol (HTTP/1.1): Conditional Requests",
258               draft-ietf-httpbis-p4-conditional-latest (work in
259               progress), May 2014.
260
261NEW:
262
263    [RFC7232]  Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
264               Protocol (HTTP/1.1): Conditional Requests", RFC 7232,
265               May 2014.
266
267
268Section 8.1., paragraph 7:
269OLD:
270
271    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
272               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
273               draft-ietf-httpbis-p6-cache-latest (work in progress),
274               May 2014.
275
276NEW:
277
278    [RFC7234]  Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
279               Ed., "Hypertext Transfer Protocol (HTTP/1.1): Caching",
280               RFC 7234, May 2014.
281
282
283Section 1.2, paragraph 19:
284OLD:
285
286    2
287       206 Partial Content (status code)  10
288
289NEW:
290
291    2
292       206 Partial Content (status code)  9
293
294
295Section 1.2, paragraph 20:
296OLD:
297
298    4
299       416 Range Not Satisfiable (status code)  15
300
301NEW:
302
303    4
304       416 Range Not Satisfiable (status code)  14
305
306
307Section 1.2, paragraph 21:
308OLD:
309
310    A
311       Accept-Ranges header field  7
312
313NEW:
314
315    A
316       Accept-Ranges header field  6
317
318
319Section 1.2, paragraph 22:
320OLD:
321
322    C
323       Content-Range header field  12
324
325NEW:
326
327    C
328       Content-Range header field  11
329
330
331Section 1.2, paragraph 23:
332OLD:
333
334    G
335       Grammar
336          Accept-Ranges  7
337          acceptable-ranges  7
338          byte-content-range  12
339          byte-range  12
340          byte-range-resp  12
341          byte-range-set  5
342          byte-range-spec  5
343          byte-ranges-specifier  5
344          bytes-unit  5
345          complete-length  12
346          Content-Range  12
347          first-byte-pos  5
348          If-Range  9
349          last-byte-pos  5
350          other-content-range  12
351          other-range-resp  12
352          other-range-unit  5, 7
353          Range  7
354          range-unit  5
355          ranges-specifier  5
356          suffix-byte-range-spec  6
357          suffix-length  6
358          unsatisfied-range  12
359
360NEW:
361
362    G
363       Grammar
364          Accept-Ranges  6
365          acceptable-ranges  6
366          byte-content-range  11
367          byte-range  11
368          byte-range-resp  11
369          byte-range-set  4
370          byte-range-spec  4
371          byte-ranges-specifier  4
372          bytes-unit  4
373          complete-length  11
374          Content-Range  11
375          first-byte-pos  4
376          If-Range  8
377          last-byte-pos  4
378          other-content-range  11
379          other-range-resp  11
380          other-range-unit  4, 6
381          Range  6
382          range-unit  4
383          ranges-specifier  4
384          suffix-byte-range-spec  5
385          suffix-length  5
386          unsatisfied-range  11
387
388
389Section 1.2, paragraph 24:
390OLD:
391
392    I
393       If-Range header field  9
394
395NEW:
396
397    I
398       If-Range header field  8
399
400
401Section 1.2, paragraph 25:
402OLD:
403
404    M
405       Media Type
406          multipart/byteranges  17, 20
407          multipart/x-byteranges  20
408       multipart/byteranges Media Type  17, 20
409       multipart/x-byteranges Media Type  20
410
411NEW:
412
413    M
414       Media Type
415          multipart/byteranges  16, 19
416          multipart/x-byteranges  19
417       multipart/byteranges Media Type  16, 19
418       multipart/x-byteranges Media Type  19
419
420
421Section 1.2, paragraph 26:
422OLD:
423
424    R
425       Range header field  7
426
427NEW:
428
429    R
430       Range header field  6
431
Note: See TracBrowser for help on using the repository browser.