draft-ietf-httpbis-p5-range-11.txt   draft-ietf-httpbis-p5-range-latest.txt 
HTTPbis Working Group R. Fielding, Ed. HTTPbis Working Group R. Fielding, Ed.
Internet-Draft Day Software Internet-Draft Day Software
Obsoletes: 2616 (if approved) J. Gettys Obsoletes: 2616 (if approved) J. Gettys
Intended status: Standards Track Alcatel-Lucent Intended status: Standards Track Alcatel-Lucent
Expires: February 5, 2011 J. Mogul Expires: March 6, 2011 J. Mogul
HP HP
H. Frystyk H. Frystyk
Microsoft Microsoft
L. Masinter L. Masinter
Adobe Systems Adobe Systems
P. Leach P. Leach
Microsoft Microsoft
T. Berners-Lee T. Berners-Lee
W3C/MIT W3C/MIT
Y. Lafon, Ed. Y. Lafon, Ed.
W3C W3C
J. Reschke, Ed. J. Reschke, Ed.
greenbytes greenbytes
August 4, 2010 September 2, 2010
HTTP/1.1, part 5: Range Requests and Partial Responses HTTP/1.1, part 5: Range Requests and Partial Responses
draft-ietf-httpbis-p5-range-11 draft-ietf-httpbis-p5-range-latest
Abstract Abstract
The Hypertext Transfer Protocol (HTTP) is an application-level The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information protocol for distributed, collaborative, hypermedia information
systems. HTTP has been in use by the World Wide Web global systems. HTTP has been in use by the World Wide Web global
information initiative since 1990. This document is Part 5 of the information initiative since 1990. This document is Part 5 of the
seven-part specification that defines the protocol referred to as seven-part specification that defines the protocol referred to as
"HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines
range-specific requests and the rules for constructing and combining range-specific requests and the rules for constructing and combining
responses to those requests. responses to those requests.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
Discussion of this draft should take place on the HTTPBIS working Discussion of this draft should take place on the HTTPBIS working
group mailing list (ietf-http-wg@w3.org). The current issues list is group mailing list (ietf-http-wg@w3.org). The current issues list is
at <http://tools.ietf.org/wg/httpbis/trac/report/3> and related at <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
documents (including fancy diffs) can be found at documents (including fancy diffs) can be found at
<http://tools.ietf.org/wg/httpbis/>. <http://tools.ietf.org/wg/httpbis/>.
The changes in this draft are summarized in Appendix D.12. The changes in this draft are summarized in Appendix D.13.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 5, 2011. This Internet-Draft will expire on March 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 7 skipping to change at page 2, line 47
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . . 5 1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . . 4
1.2. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 5 1.2. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 4
1.2.1. Core Rules . . . . . . . . . . . . . . . . . . . . . . 6 1.2.1. Core Rules . . . . . . . . . . . . . . . . . . . . . . 5
1.2.2. ABNF Rules defined in other Parts of the 1.2.2. ABNF Rules defined in other Parts of the
Specification . . . . . . . . . . . . . . . . . . . . 6 Specification . . . . . . . . . . . . . . . . . . . . 5
2. Range Units . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Range Units . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1. Range Specifier Registry . . . . . . . . . . . . . . . . . 6 2.1. Range Specifier Registry . . . . . . . . . . . . . . . . . 5
3. Status Code Definitions . . . . . . . . . . . . . . . . . . . 7 3. Status Code Definitions . . . . . . . . . . . . . . . . . . . 6
3.1. 206 Partial Content . . . . . . . . . . . . . . . . . . . 7 3.1. 206 Partial Content . . . . . . . . . . . . . . . . . . . 6
3.2. 416 Requested Range Not Satisfiable . . . . . . . . . . . 8 3.2. 416 Requested Range Not Satisfiable . . . . . . . . . . . 7
4. Combining Ranges . . . . . . . . . . . . . . . . . . . . . . . 8 4. Combining Ranges . . . . . . . . . . . . . . . . . . . . . . . 7
5. Header Field Definitions . . . . . . . . . . . . . . . . . . . 8 5. Header Field Definitions . . . . . . . . . . . . . . . . . . . 7
5.1. Accept-Ranges . . . . . . . . . . . . . . . . . . . . . . 9 5.1. Accept-Ranges . . . . . . . . . . . . . . . . . . . . . . 8
5.2. Content-Range . . . . . . . . . . . . . . . . . . . . . . 9 5.2. Content-Range . . . . . . . . . . . . . . . . . . . . . . 8
5.3. If-Range . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.3. If-Range . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.4. Range . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.4. Range . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.4.1. Byte Ranges . . . . . . . . . . . . . . . . . . . . . 12 5.4.1. Byte Ranges . . . . . . . . . . . . . . . . . . . . . 11
5.4.2. Range Retrieval Requests . . . . . . . . . . . . . . . 14 5.4.2. Range Retrieval Requests . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6.1. Status Code Registration . . . . . . . . . . . . . . . . . 15 6.1. Status Code Registration . . . . . . . . . . . . . . . . . 14
6.2. Header Field Registration . . . . . . . . . . . . . . . . 15 6.2. Header Field Registration . . . . . . . . . . . . . . . . 14
6.3. Range Specifier Registration . . . . . . . . . . . . . . . 16 6.3. Range Specifier Registration . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16 7. Security Considerations . . . . . . . . . . . . . . . . . . . 15
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 16 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . . 16
Appendix A. Internet Media Type multipart/byteranges . . . . . . 17 Appendix A. Internet Media Type multipart/byteranges . . . . . . 16
Appendix B. Compatibility with Previous Versions . . . . . . . . 20 Appendix B. Compatibility with Previous Versions . . . . . . . . 19
B.1. Changes from RFC 2616 . . . . . . . . . . . . . . . . . . 20 B.1. Changes from RFC 2616 . . . . . . . . . . . . . . . . . . 19
Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 20 Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 19
Appendix D. Change Log (to be removed by RFC Editor before Appendix D. Change Log (to be removed by RFC Editor before
publication) . . . . . . . . . . . . . . . . . . . . 21 publication) . . . . . . . . . . . . . . . . . . . . 20
D.1. Since RFC2616 . . . . . . . . . . . . . . . . . . . . . . 21 D.1. Since RFC2616 . . . . . . . . . . . . . . . . . . . . . . 20
D.2. Since draft-ietf-httpbis-p5-range-00 . . . . . . . . . . . 21 D.2. Since draft-ietf-httpbis-p5-range-00 . . . . . . . . . . . 20
D.3. Since draft-ietf-httpbis-p5-range-01 . . . . . . . . . . . 22 D.3. Since draft-ietf-httpbis-p5-range-01 . . . . . . . . . . . 21
D.4. Since draft-ietf-httpbis-p5-range-02 . . . . . . . . . . . 22 D.4. Since draft-ietf-httpbis-p5-range-02 . . . . . . . . . . . 21
D.5. Since draft-ietf-httpbis-p5-range-03 . . . . . . . . . . . 22 D.5. Since draft-ietf-httpbis-p5-range-03 . . . . . . . . . . . 21
D.6. Since draft-ietf-httpbis-p5-range-04 . . . . . . . . . . . 22 D.6. Since draft-ietf-httpbis-p5-range-04 . . . . . . . . . . . 21
D.7. Since draft-ietf-httpbis-p5-range-05 . . . . . . . . . . . 22 D.7. Since draft-ietf-httpbis-p5-range-05 . . . . . . . . . . . 21
D.8. Since draft-ietf-httpbis-p5-range-06 . . . . . . . . . . . 23 D.8. Since draft-ietf-httpbis-p5-range-06 . . . . . . . . . . . 22
D.9. Since draft-ietf-httpbis-p5-range-07 . . . . . . . . . . . 23 D.9. Since draft-ietf-httpbis-p5-range-07 . . . . . . . . . . . 22
D.10. Since draft-ietf-httpbis-p5-range-08 . . . . . . . . . . . 23 D.10. Since draft-ietf-httpbis-p5-range-08 . . . . . . . . . . . 22
D.11. Since draft-ietf-httpbis-p5-range-09 . . . . . . . . . . . 23 D.11. Since draft-ietf-httpbis-p5-range-09 . . . . . . . . . . . 22
D.12. Since draft-ietf-httpbis-p5-range-10 . . . . . . . . . . . 23 D.12. Since draft-ietf-httpbis-p5-range-10 . . . . . . . . . . . 22
D.13. Since draft-ietf-httpbis-p5-range-11 . . . . . . . . . . . 23
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
HTTP clients often encounter interrupted data transfers as a result HTTP clients often encounter interrupted data transfers as a result
of cancelled requests or dropped connections. When a cache has of cancelled requests or dropped connections. When a cache has
stored a partial representation, it is desirable to request the stored a partial representation, it is desirable to request the
remainder of that representation in a subsequent request rather than remainder of that representation in a subsequent request rather than
transfer the entire representation. There are also a number of Web transfer the entire representation. There are also a number of Web
applications that benefit from being able to request only a subset of applications that benefit from being able to request only a subset of
a larger representation, such as a single page of a very large a larger representation, such as a single page of a very large
skipping to change at page 16, line 44 skipping to change at page 15, line 44
Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi Larry Masinter, Jeff Mogul, Lou Montulli, David W. Morris, Luigi
Rizzo, and Bill Weihl. Rizzo, and Bill Weihl.
9. References 9. References
9.1. Normative References 9.1. Normative References
[Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part1] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections, and J. Reschke, Ed., "HTTP/1.1, part 1: URIs, Connections,
and Message Parsing", draft-ietf-httpbis-p1-messaging-11 and Message Parsing",
(work in progress), August 2010. draft-ietf-httpbis-p1-messaging-latest (work in progress),
September 2010.
[Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., [Part4] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed., Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
and J. Reschke, Ed., "HTTP/1.1, part 4: Conditional and J. Reschke, Ed., "HTTP/1.1, part 4: Conditional
Requests", draft-ietf-httpbis-p4-conditional-11 (work in Requests", draft-ietf-httpbis-p4-conditional-latest (work
progress), August 2010. in progress), September 2010.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996. November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
skipping to change at page 24, line 16 skipping to change at page 23, line 16
entity / representation / variant terminology" entity / representation / variant terminology"
o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider
removing the 'changes from 2068' sections" removing the 'changes from 2068' sections"
Ongoing work on Custom Ranges Ongoing work on Custom Ranges
(<http://tools.ietf.org/wg/httpbis/trac/ticket/85>): (<http://tools.ietf.org/wg/httpbis/trac/ticket/85>):
o Add IANA registry. o Add IANA registry.
D.13. Since draft-ietf-httpbis-p5-range-11
None yet.
Index Index
2 2
206 Partial Content (status code) 7 206 Partial Content (status code) 6
4 4
416 Requested Range Not Satisfiable (status code) 8 416 Requested Range Not Satisfiable (status code) 7
A A
Accept-Ranges header 9 Accept-Ranges header 8
C C
Content-Range header 9 Content-Range header 8
G G
Grammar Grammar
Accept-Ranges 9 Accept-Ranges 8
Accept-Ranges-v 9 Accept-Ranges-v 8
acceptable-ranges 9 acceptable-ranges 8
byte-content-range-spec 9 byte-content-range-spec 8
byte-range-resp-spec 9 byte-range-resp-spec 8
byte-range-set 12 byte-range-set 11
byte-range-spec 12 byte-range-spec 11
byte-ranges-specifier 12 byte-ranges-specifier 11
bytes-unit 6 bytes-unit 5
Content-Range 9 Content-Range 8
content-range-spec 9 content-range-spec 8
Content-Range-v 9 Content-Range-v 8
first-byte-pos 12 first-byte-pos 11
If-Range 12 If-Range 11
If-Range-v 12 If-Range-v 11
instance-length 9 instance-length 8
last-byte-pos 12 last-byte-pos 11
other-range-unit 6 other-range-unit 5
Range 14 Range 13
range-unit 6 range-unit 5
ranges-specifier 12 ranges-specifier 11
suffix-byte-range-spec 13 suffix-byte-range-spec 12
suffix-length 13 suffix-length 12
H H
Headers Headers
Accept-Ranges 9 Accept-Ranges 8
Content-Range 9 Content-Range 8
If-Range 11 If-Range 10
Range 12 Range 11
I I
If-Range header 11 If-Range header 10
M M
Media Type Media Type
multipart/byteranges 17 multipart/byteranges 16
multipart/x-byteranges 20 multipart/x-byteranges 19
multipart/byteranges Media Type 17 multipart/byteranges Media Type 16
multipart/x-byteranges Media Type 20 multipart/x-byteranges Media Type 19
R R
Range header 12 Range header 11
S S
Status Codes Status Codes
206 Partial Content 7 206 Partial Content 6
416 Requested Range Not Satisfiable 8 416 Requested Range Not Satisfiable 7
Authors' Addresses Authors' Addresses
Roy T. Fielding (editor) Roy T. Fielding (editor)
Day Software Day Software
23 Corporate Plaza DR, Suite 280 23 Corporate Plaza DR, Suite 280
Newport Beach, CA 92660 Newport Beach, CA 92660
USA USA
Phone: +1-949-706-5300 Phone: +1-949-706-5300
 End of changes. 21 change blocks. 
94 lines changed or deleted 99 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/