draft-fielding-httpbis-http-range-00.txt		draft-fielding-httpbis-http-range-latest.txt
	Network Working Group R. Fielding, Ed.		Network Working Group R. Fielding, Ed.
	Internet-Draft Adobe		Internet-Draft Adobe
	Obsoletes: 7233 (if approved) Y. Lafon, Ed.		Obsoletes: 7233 (if approved) Y. Lafon, Ed.
	Intended status: Standards Track W3C		Intended status: Standards Track W3C
	Expires: September 6, 2018 J. Reschke, Ed.		Expires: September 18, 2018 J. Reschke, Ed.
	greenbytes		greenbytes
	March 5, 2018		March 17, 2018
	Hypertext Transfer Protocol (HTTP): Range Requests		Hypertext Transfer Protocol (HTTP): Range Requests
	draft-fielding-httpbis-http-range-00		draft-fielding-httpbis-http-range-latest
	Abstract		Abstract
	The Hypertext Transfer Protocol (HTTP) is a stateless application-		The Hypertext Transfer Protocol (HTTP) is a stateless application-
	level protocol for distributed, collaborative, hypertext information		level protocol for distributed, collaborative, hypertext information
	systems. This document defines range requests and the rules for		systems. This document defines range requests and the rules for
	constructing and combining responses to those requests.		constructing and combining responses to those requests.
	This document obsoletes RFC 7233.		This document obsoletes RFC 7233.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	item of the HTTP Working Group._		item of the HTTP Working Group._
	Discussion of this draft takes place on the HTTP working group		Discussion of this draft takes place on the HTTP working group
	mailing list (ietf-http-wg@w3.org), which is archived at		mailing list (ietf-http-wg@w3.org), which is archived at
	<http://lists.w3.org/Archives/Public/ietf-http-wg/>.		<http://lists.w3.org/Archives/Public/ietf-http-wg/>.
	Errata for RFC 7233 have been collected at <https://www.rfc-		Errata for RFC 7233 have been collected at <https://www.rfc-
	editor.org/errata_search.php?rfc=7233>, and an additional issues list		editor.org/errata_search.php?rfc=7233>, and an additional issues list
	lives at <https://github.com/httpwg/http11bis/issues>.		lives at <https://github.com/httpwg/http11bis/issues>.
	The changes in this draft are summarized in Appendix E.1.		The changes in this draft are summarized in Appendix E.2.
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 September 6, 2018.		This Internet-Draft will expire on September 18, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 26 ¶		skipping to change at page 3, line 26 ¶
	6.1. Denial-of-Service Attacks Using Range . . . . . . . . . . 18		6.1. Denial-of-Service Attacks Using Range . . . . . . . . . . 18
	7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18		7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
	7.1. Normative References . . . . . . . . . . . . . . . . . . 18		7.1. Normative References . . . . . . . . . . . . . . . . . . 18
	7.2. Informative References . . . . . . . . . . . . . . . . . 19		7.2. Informative References . . . . . . . . . . . . . . . . . 19
	Appendix A. Internet Media Type multipart/byteranges . . . . . . 20		Appendix A. Internet Media Type multipart/byteranges . . . . . . 20
	Appendix B. Changes from RFC 7233 . . . . . . . . . . . . . . . 21		Appendix B. Changes from RFC 7233 . . . . . . . . . . . . . . . 21
	Appendix C. Imported ABNF . . . . . . . . . . . . . . . . . . . 21		Appendix C. Imported ABNF . . . . . . . . . . . . . . . . . . . 21
	Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 21		Appendix D. Collected ABNF . . . . . . . . . . . . . . . . . . . 21
	Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 23		Appendix E. Change Log . . . . . . . . . . . . . . . . . . . . . 23
	E.1. Since RFC 7233 . . . . . . . . . . . . . . . . . . . . . 23		E.1. Since RFC 7233 . . . . . . . . . . . . . . . . . . . . . 23
			E.2. Since draft-fielding-httpbis-range-00 . . . . . . . . . . 23
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 24		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 24
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
	1. Introduction		1. Introduction
	Hypertext Transfer Protocol (HTTP) clients often encounter		Hypertext Transfer Protocol (HTTP) clients often encounter
	interrupted data transfers as a result of canceled requests or		interrupted data transfers as a result of canceled requests or
	dropped connections. When a client has stored a partial		dropped connections. When a client has stored a partial
	representation, it is desirable to request the remainder of that		representation, it is desirable to request the remainder of that
	skipping to change at page 18, line 24 ¶		skipping to change at page 18, line 24 ¶
	particularly when the ranges are requested out of order for no		particularly when the ranges are requested out of order for no
	apparent reason. Multipart range requests are not designed to		apparent reason. Multipart range requests are not designed to
	support random access.		support random access.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft-		Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft-
	fielding-httpbis-http-cache-00 (work in progress), March		fielding-httpbis-http-cache-latest (work in progress),
	2018.		March 2018.
	[CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Conditional Requests", draft-fielding-		Protocol (HTTP): Conditional Requests", draft-fielding-
	httpbis-http-conditional-00 (work in progress), March		httpbis-http-conditional-latest (work in progress), March
	2018.		2018.
	[MESSGNG] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[MESSGNG] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP/1.1): Message Syntax and Routing", draft-		Protocol (HTTP/1.1): Message Syntax and Routing", draft-
	fielding-httpbis-http-messaging-00 (work in progress),		fielding-httpbis-http-messaging-latest (work in progress),
	March 2018.		March 2018.
	[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,
	DOI 10.17487/RFC2046, November 1996,		DOI 10.17487/RFC2046, November 1996,
	<https://www.rfc-editor.org/info/rfc2046>.		<https://www.rfc-editor.org/info/rfc2046>.
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[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,		Specifications: ABNF", STD 68, RFC 5234,
	DOI 10.17487/RFC5234, January 2008,		DOI 10.17487/RFC5234, January 2008,
	<https://www.rfc-editor.org/info/rfc5234>.		<https://www.rfc-editor.org/info/rfc5234>.
	[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Semantics and Content", draft-fielding-		Protocol (HTTP): Semantics and Content", draft-fielding-
	httpbis-http-semantics-00 (work in progress), March 2018.		httpbis-http-semantics-latest (work in progress), March
			2018.
	7.2. Informative References		7.2. Informative References
	[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type		[BCP13] Freed, N., Klensin, J., and T. Hansen, "Media Type
	Specifications and Registration Procedures", BCP 13,		Specifications and Registration Procedures", BCP 13,
	RFC 6838, January 2013,		RFC 6838, January 2013,
	<https://www.rfc-editor.org/info/bcp13>.		<https://www.rfc-editor.org/info/bcp13>.
	[BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration		[BCP90] Klyne, G., Nottingham, M., and J. Mogul, "Registration
	Procedures for Message Header Fields", BCP 90, RFC 3864,		Procedures for Message Header Fields", BCP 90, RFC 3864,
	skipping to change at page 23, line 30 ¶		skipping to change at page 23, line 30 ¶
	o Update links to sibling specifications.		o Update links to sibling specifications.
	o Replace sections listing changes from RFC 2616 by new empty		o Replace sections listing changes from RFC 2616 by new empty
	sections referring to RFC 723x.		sections referring to RFC 723x.
	o Remove acknowledgements specific to RFC 723x.		o Remove acknowledgements specific to RFC 723x.
	o Move "Acknowledgements" to the very end and make them unnumbered.		o Move "Acknowledgements" to the very end and make them unnumbered.
			E.2. Since draft-fielding-httpbis-range-00
			None yet.
	Index		Index
	2		2
	206 Partial Content (status code) 9		206 Partial Content (status code) 9
	4		4
	416 Range Not Satisfiable (status code) 14		416 Range Not Satisfiable (status code) 14
	A		A
	Accept-Ranges header field 6		Accept-Ranges header field 6
End of changes. 11 change blocks.
	10 lines changed or deleted		16 lines changed or added
This html diff was produced by rfcdiff 1.44jr. The latest version is available from http://tools.ietf.org/tools/rfcdiff/