| draft-ietf-httpbis-p5-range-09.txt |  | draft-ietf-httpbis-p5-range-10.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 One Laptop per Child |  | Intended status: Standards Track Alcatel-Lucent |
| Expires: September 9, 2010 J. Mogul |  | Expires: January 13, 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 |
| March 8, 2010 |  | July 12, 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-09 |  | draft-ietf-httpbis-p5-range-10 |
| 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/11> 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.10. |  | The changes in this draft are summarized in Appendix D.11. |
| Status of this Memo |  | Status of This Memo |
| This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that |  | Task Force (IETF). Note that other groups may also distribute |
| other groups may also distribute working documents as Internet- |  | working documents as Internet-Drafts. The list of current Internet- |
| Drafts. |  | 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." |
| The list of current Internet-Drafts can be accessed at |  | This Internet-Draft will expire on January 13, 2011. |
| http://www.ietf.org/ietf/1id-abstracts.txt. |  |  |
| The list of Internet-Draft Shadow Directories can be accessed at |  |  |
| http://www.ietf.org/shadow.html. |  |  |
| This Internet-Draft will expire on September 9, 2010. |  |  |
| 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 |
| carefully, as they describe your rights and restrictions with respect |  | carefully, as they describe your rights and restrictions with respect |
| to this document. Code Components extracted from this document must |  | to this document. Code Components extracted from this document must |
| include Simplified BSD License text as described in Section 4.e of |  | include Simplified BSD License text as described in Section 4.e of |
| the Trust Legal Provisions and are provided without warranty as |  | the Trust Legal Provisions and are provided without warranty as |
| described in the BSD License. |  | described in the Simplified BSD License. |
| This document may contain material from IETF Documents or IETF |  | This document may contain material from IETF Documents or IETF |
| Contributions published or made publicly available before November |  | Contributions published or made publicly available before November |
| 10, 2008. The person(s) controlling the copyright in some of this |  | 10, 2008. The person(s) controlling the copyright in some of this |
| material may not have granted the IETF Trust the right to allow |  | material may not have granted the IETF Trust the right to allow |
| 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 |
| skipping to change at page 3, line 32 |  | skipping to change at page 3, line 32 |
| 5.4. Range . . . . . . . . . . . . . . . . . . . . . . . . . . 11 |  | 5.4. Range . . . . . . . . . . . . . . . . . . . . . . . . . . 11 |
| 5.4.1. Byte Ranges . . . . . . . . . . . . . . . . . . . . . 11 |  | 5.4.1. Byte Ranges . . . . . . . . . . . . . . . . . . . . . 11 |
| 5.4.2. Range Retrieval Requests . . . . . . . . . . . . . . . 13 |  | 5.4.2. Range Retrieval Requests . . . . . . . . . . . . . . . 13 |
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 |  | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 |
| 6.1. Status Code Registration . . . . . . . . . . . . . . . . . 14 |  | 6.1. Status Code Registration . . . . . . . . . . . . . . . . . 14 |
| 6.2. Message Header Registration . . . . . . . . . . . . . . . 14 |  | 6.2. Message Header Registration . . . . . . . . . . . . . . . 14 |
| 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 |  | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 |
| 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 |  | 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14 |
| 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 |  | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 |
| 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 |  | 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 |
| 9.2. Informative References . . . . . . . . . . . . . . . . . . 16 |  | 9.2. Informative References . . . . . . . . . . . . . . . . . . 15 |
| Appendix A. Internet Media Type multipart/byteranges . . . . . . 16 |  | Appendix A. Internet Media Type multipart/byteranges . . . . . . 16 |
| Appendix B. Compatibility with Previous Versions . . . . . . . . 18 |  | Appendix B. Compatibility with Previous Versions . . . . . . . . 18 |
| B.1. Changes from RFC 2068 . . . . . . . . . . . . . . . . . . 18 |  | B.1. Changes from RFC 2068 . . . . . . . . . . . . . . . . . . 18 |
| B.2. Changes from RFC 2616 . . . . . . . . . . . . . . . . . . 19 |  | B.2. Changes from RFC 2616 . . . . . . . . . . . . . . . . . . 18 |
| Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 19 |  | 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) . . . . . . . . . . . . . . . . . . . . 20 |  | publication) . . . . . . . . . . . . . . . . . . . . 20 |
| D.1. Since RFC2616 . . . . . . . . . . . . . . . . . . . . . . 20 |  | 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 . . . . . . . . . . . 21 |  | D.3. Since draft-ietf-httpbis-p5-range-01 . . . . . . . . . . . 20 |
| D.4. Since draft-ietf-httpbis-p5-range-02 . . . . . . . . . . . 21 |  | D.4. Since draft-ietf-httpbis-p5-range-02 . . . . . . . . . . . 21 |
| D.5. Since draft-ietf-httpbis-p5-range-03 . . . . . . . . . . . 21 |  | D.5. Since draft-ietf-httpbis-p5-range-03 . . . . . . . . . . . 21 |
| D.6. Since draft-ietf-httpbis-p5-range-04 . . . . . . . . . . . 21 |  | 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 . . . . . . . . . . . 22 |  | D.8. Since draft-ietf-httpbis-p5-range-06 . . . . . . . . . . . 22 |
| D.9. Since draft-ietf-httpbis-p5-range-07 . . . . . . . . . . . 22 |  | 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 |
| Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 |  | D.11. Since draft-ietf-httpbis-p5-range-09 . . . . . . . . . . . 22 |
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24 |  | Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 |
| 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 4, line 37 |  | skipping to change at page 4, line 37 |
| extensible range types, this specification only defines requests for |  | extensible range types, this specification only defines requests for |
| byte ranges. |  | byte ranges. |
| 1.1. Requirements |  | 1.1. Requirements |
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |  | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |  | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| document are to be interpreted as described in [RFC2119]. |  | document are to be interpreted as described in [RFC2119]. |
| An implementation is not compliant if it fails to satisfy one or more |  | An implementation is not compliant if it fails to satisfy one or more |
| of the MUST or REQUIRED level requirements for the protocols it |  | of the "MUST" or "REQUIRED" level requirements for the protocols it |
| implements. An implementation that satisfies all the MUST or |  | implements. An implementation that satisfies all the "MUST" or |
| REQUIRED level and all the SHOULD level requirements for its |  | "REQUIRED" level and all the "SHOULD" level requirements for its |
| protocols is said to be "unconditionally compliant"; one that |  | protocols is said to be "unconditionally compliant"; one that |
| satisfies all the MUST level requirements but not all the SHOULD |  | satisfies all the "MUST" level requirements but not all the "SHOULD" |
| level requirements for its protocols is said to be "conditionally |  | level requirements for its protocols is said to be "conditionally |
| compliant." |  | compliant". |
| 1.2. Syntax Notation |  | 1.2. Syntax Notation |
| This specification uses the ABNF syntax defined in Section 1.2 of |  | This specification uses the ABNF syntax defined in Section 1.2 of |
| [Part1] (which extends the syntax defined in [RFC5234] with a list |  | [Part1] (which extends the syntax defined in [RFC5234] with a list |
| rule). Appendix C shows the collected ABNF, with the list rule |  | rule). Appendix C shows the collected ABNF, with the list rule |
| expanded. |  | expanded. |
| The following core rules are included by reference, as defined in |  | The following core rules are included by reference, as defined in |
| skipping to change at page 6, line 49 |  | skipping to change at page 6, line 49 |
| MUST NOT cache 206 (Partial Content) responses. Furthermore, if a |  | MUST NOT cache 206 (Partial Content) responses. Furthermore, if a |
| response uses a range unit that is not understood by the cache, then |  | response uses a range unit that is not understood by the cache, then |
| it MUST NOT be cached either. |  | it MUST NOT be cached either. |
| 3.2. 416 Requested Range Not Satisfiable |  | 3.2. 416 Requested Range Not Satisfiable |
| A server SHOULD return a response with this status code if a request |  | A server SHOULD return a response with this status code if a request |
| included a Range request-header field (Section 5.4), and none of the |  | included a Range request-header field (Section 5.4), and none of the |
| ranges-specifier values in this field overlap the current extent of |  | ranges-specifier values in this field overlap the current extent of |
| the selected resource, and the request did not include an If-Range |  | the selected resource, and the request did not include an If-Range |
| request-header field. (For byte-ranges, this means that the first- |  | request-header field (Section 5.3). (For byte-ranges, this means |
| byte-pos of all of the byte-range-spec values were greater than the |  | that the first-byte-pos of all of the byte-range-spec values were |
| current length of the selected resource.) |  | greater than the current length of the selected resource.) |
| When this status code is returned for a byte-range request, the |  | When this status code is returned for a byte-range request, the |
| response SHOULD include a Content-Range entity-header field |  | response SHOULD include a Content-Range entity-header field |
| specifying the current length of the selected resource (see |  | specifying the current length of the selected resource (see |
| Section 5.2). This response MUST NOT use the multipart/byteranges |  | Section 5.2). This response MUST NOT use the multipart/byteranges |
| content-type. |  | content-type. |
| 4. Combining Ranges |  | 4. Combining Ranges |
| A response might transfer only a subrange of an entity-body, either |  | A response might transfer only a subrange of an entity-body, either |
| because the request included one or more Range specifications, or |  | because the request included one or more Range specifications, or |
| skipping to change at page 15, line 11 |  | skipping to change at page 15, line 4 |
| 8. Acknowledgments |  | 8. Acknowledgments |
| Most of the specification of ranges is based on work originally done |  | Most of the specification of ranges is based on work originally done |
| by Ari Luotonen and John Franks, with additional input from Steve |  | by Ari Luotonen and John Franks, with additional input from Steve |
| Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin |  | Zilles, Daniel W. Connolly, Roy T. Fielding, Jim Gettys, Martin |
| Hamilton, Koen Holtman, Shel Kaplan, Paul Leach, Alex Lopez-Ortiz, |  | Hamilton, Koen Holtman, Shel Kaplan, Paul Leach, Alex Lopez-Ortiz, |
| 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-09 |  | and Message Parsing", draft-ietf-httpbis-p1-messaging-10 |
| (work in progress), March 2010. |  | (work in progress), July 2010. |
| [Part3] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part3] 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 3: Message Payload |  | and J. Reschke, Ed., "HTTP/1.1, part 3: Message Payload |
| and Content Negotiation", draft-ietf-httpbis-p3-payload-09 |  | and Content Negotiation", draft-ietf-httpbis-p3-payload-10 |
| (work in progress), March 2010. |  | (work in progress), July 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-09 (work in |  | Requests", draft-ietf-httpbis-p4-conditional-10 (work in |
| progress), March 2010. |  | progress), July 2010. |
| [Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H., |  | [Part6] 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., |
| Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part |  | Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part |
| 6: Caching", draft-ietf-httpbis-p6-cache-09 (work in |  | 6: Caching", draft-ietf-httpbis-p6-cache-10 (work in |
| progress), March 2010. |  | progress), July 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 22, line 45 |  | skipping to change at page 22, line 19 |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/161>: "base for |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/161>: "base for |
| numeric protocol elements" |  | numeric protocol elements" |
| D.9. Since draft-ietf-httpbis-p5-range-07 |  | D.9. Since draft-ietf-httpbis-p5-range-07 |
| Closed issues: |  | Closed issues: |
| o Fixed discrepancy in the If-Range definition about allowed |  | o Fixed discrepancy in the If-Range definition about allowed |
| validators. |  | validators. |
| o <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/150>: |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/150>: "multipart/ |
| "multipart/byteranges for custom range units" |  | byteranges for custom range units" |
| o <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/151>: "range |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/151>: "range unit |
| unit missing from other-ranges-specifier in Range header" |  | missing from other-ranges-specifier in Range header" |
| o <http://tools.ietf.org/wg/httpbis/trac/ticket/198>: "move IANA |  | o <http://tools.ietf.org/wg/httpbis/trac/ticket/198>: "move IANA |
| registrations for optional status codes" |  | registrations for optional status codes" |
| D.10. Since draft-ietf-httpbis-p5-range-08 |  | D.10. Since draft-ietf-httpbis-p5-range-08 |
| No significant changes. |  | No significant changes. |
|  |  | D.11. Since draft-ietf-httpbis-p5-range-09 |
|  |  | No significant changes. |
| Index |  | Index |
| 2 |  | 2 |
| 206 Partial Content (status code) 6 |  | 206 Partial Content (status code) 6 |
| 4 |  | 4 |
| 416 Requested Range Not Satisfiable (status code) 6 |  | 416 Requested Range Not Satisfiable (status code) 6 |
| A |  | A |
| Accept-Ranges header 7 |  | Accept-Ranges header 7 |
| skipping to change at page 23, line 38 |  | skipping to change at page 23, line 16 |
| byte-content-range-spec 8 |  | byte-content-range-spec 8 |
| byte-range-resp-spec 8 |  | byte-range-resp-spec 8 |
| byte-range-set 11 |  | byte-range-set 11 |
| byte-range-spec 11 |  | byte-range-spec 11 |
| byte-ranges-specifier 11 |  | byte-ranges-specifier 11 |
| bytes-unit 5 |  | bytes-unit 5 |
| Content-Range 8 |  | Content-Range 8 |
| content-range-spec 8 |  | content-range-spec 8 |
| Content-Range-v 8 |  | Content-Range-v 8 |
| first-byte-pos 11 |  | first-byte-pos 11 |
| If-Range 11 |  | If-Range 10 |
| If-Range-v 11 |  | If-Range-v 10 |
| instance-length 8 |  | instance-length 8 |
| last-byte-pos 11 |  | last-byte-pos 11 |
| other-range-unit 5 |  | other-range-unit 5 |
| Range 13 |  | Range 13 |
| range-unit 5 |  | range-unit 5 |
| ranges-specifier 11 |  | ranges-specifier 11 |
| suffix-byte-range-spec 12 |  | suffix-byte-range-spec 12 |
| suffix-length 12 |  | suffix-length 12 |
| H |  | H |
| skipping to change at page 24, line 36 |  | skipping to change at page 24, line 15 |
| 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 |
| Fax: +1-949-706-5305 |  | Fax: +1-949-706-5305 |
| Email: fielding@gbiv.com |  | EMail: fielding@gbiv.com |
| URI: http://roy.gbiv.com/ |  | URI: http://roy.gbiv.com/ |
| Jim Gettys |  | Jim Gettys |
| One Laptop per Child |  | Alcatel-Lucent Bell Labs |
| 21 Oak Knoll Road |  | 21 Oak Knoll Road |
| Carlisle, MA 01741 |  | Carlisle, MA 01741 |
| USA |  | USA |
| Email: jg@laptop.org |  | EMail: jg@freedesktop.org |
| URI: http://www.laptop.org/ |  | URI: http://gettys.wordpress.com/ |
| Jeffrey C. Mogul |  | Jeffrey C. Mogul |
| Hewlett-Packard Company |  | Hewlett-Packard Company |
| HP Labs, Large Scale Systems Group |  | HP Labs, Large Scale Systems Group |
| 1501 Page Mill Road, MS 1177 |  | 1501 Page Mill Road, MS 1177 |
| Palo Alto, CA 94304 |  | Palo Alto, CA 94304 |
| USA |  | USA |
| Email: JeffMogul@acm.org |  | EMail: JeffMogul@acm.org |
| Henrik Frystyk Nielsen |  | Henrik Frystyk Nielsen |
| Microsoft Corporation |  | Microsoft Corporation |
| 1 Microsoft Way |  | 1 Microsoft Way |
| Redmond, WA 98052 |  | Redmond, WA 98052 |
| USA |  | USA |
| Email: henrikn@microsoft.com |  | EMail: henrikn@microsoft.com |
| Larry Masinter |  | Larry Masinter |
| Adobe Systems, Incorporated |  | Adobe Systems, Incorporated |
| 345 Park Ave |  | 345 Park Ave |
| San Jose, CA 95110 |  | San Jose, CA 95110 |
| USA |  | USA |
| Email: LMM@acm.org |  | EMail: LMM@acm.org |
| URI: http://larry.masinter.net/ |  | URI: http://larry.masinter.net/ |
| Paul J. Leach |  | Paul J. Leach |
| Microsoft Corporation |  | Microsoft Corporation |
| 1 Microsoft Way |  | 1 Microsoft Way |
| Redmond, WA 98052 |  | Redmond, WA 98052 |
| Email: paulle@microsoft.com |  | EMail: paulle@microsoft.com |
| Tim Berners-Lee |  | Tim Berners-Lee |
| World Wide Web Consortium |  | World Wide Web Consortium |
| MIT Computer Science and Artificial Intelligence Laboratory |  | MIT Computer Science and Artificial Intelligence Laboratory |
| The Stata Center, Building 32 |  | The Stata Center, Building 32 |
| 32 Vassar Street |  | 32 Vassar Street |
| Cambridge, MA 02139 |  | Cambridge, MA 02139 |
| USA |  | USA |
| Email: timbl@w3.org |  | EMail: timbl@w3.org |
| URI: http://www.w3.org/People/Berners-Lee/ |  | URI: http://www.w3.org/People/Berners-Lee/ |
| Yves Lafon (editor) |  | Yves Lafon (editor) |
| World Wide Web Consortium |  | World Wide Web Consortium |
| W3C / ERCIM |  | W3C / ERCIM |
| 2004, rte des Lucioles |  | 2004, rte des Lucioles |
| Sophia-Antipolis, AM 06902 |  | Sophia-Antipolis, AM 06902 |
| France |  | France |
| Email: ylafon@w3.org |  | EMail: ylafon@w3.org |
| URI: http://www.raubacapeu.net/people/yves/ |  | URI: http://www.raubacapeu.net/people/yves/ |
| Julian F. Reschke (editor) |  | Julian F. Reschke (editor) |
| greenbytes GmbH |  | greenbytes GmbH |
| Hafenweg 16 |  | Hafenweg 16 |
| Muenster, NW 48155 |  | Muenster, NW 48155 |
| Germany |  | Germany |
| Phone: +49 251 2807760 |  | Phone: +49 251 2807760 |
| Fax: +49 251 2807761 |  | Fax: +49 251 2807761 |
| Email: julian.reschke@greenbytes.de |  | EMail: julian.reschke@greenbytes.de |
| URI: http://greenbytes.de/tech/webdav/ |  | URI: http://greenbytes.de/tech/webdav/ |
End of changes. 40 change blocks.
| 63 lines changed or deleted |  | 60 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/