draft-fielding-httpbis-http-cache-00.txt		draft-fielding-httpbis-http-cache-latest.txt
	Network Working Group R. Fielding, Ed.		Network Working Group R. Fielding, Ed.
	Internet-Draft Adobe		Internet-Draft Adobe
	Obsoletes: 7234 (if approved) M. Nottingham, Ed.		Obsoletes: 7234 (if approved) M. Nottingham, Ed.
	Intended status: Standards Track Fastly		Intended status: Standards Track Fastly
	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): Caching		Hypertext Transfer Protocol (HTTP): Caching
	draft-fielding-httpbis-http-cache-00		draft-fielding-httpbis-http-cache-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 HTTP caches and the associated header		systems. This document defines HTTP caches and the associated header
	fields that control cache behavior or indicate cacheable response		fields that control cache behavior or indicate cacheable response
	messages.		messages.
	This document obsoletes RFC 7234.		This document obsoletes RFC 7234.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	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 7234 have been collected at <https://www.rfc-		Errata for RFC 7234 have been collected at <https://www.rfc-
	editor.org/errata_search.php?rfc=7234>, and an additional issues list		editor.org/errata_search.php?rfc=7234>, 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 D.1.		The changes in this draft are summarized in Appendix D.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 4, line 5 ¶		skipping to change at page 4, line 5 ¶
	7.3. Header Field Registration . . . . . . . . . . . . . . . . 34		7.3. Header Field Registration . . . . . . . . . . . . . . . . 34
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 35		8. Security Considerations . . . . . . . . . . . . . . . . . . . 35
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
	9.1. Normative References . . . . . . . . . . . . . . . . . . 36		9.1. Normative References . . . . . . . . . . . . . . . . . . 36
	9.2. Informative References . . . . . . . . . . . . . . . . . 36		9.2. Informative References . . . . . . . . . . . . . . . . . 36
	Appendix A. Changes from RFC 7234 . . . . . . . . . . . . . . . 38		Appendix A. Changes from RFC 7234 . . . . . . . . . . . . . . . 38
	Appendix B. Imported ABNF . . . . . . . . . . . . . . . . . . . 38		Appendix B. Imported ABNF . . . . . . . . . . . . . . . . . . . 38
	Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 38		Appendix C. Collected ABNF . . . . . . . . . . . . . . . . . . . 38
	Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 39		Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 39
	D.1. Since RFC 7234 . . . . . . . . . . . . . . . . . . . . . 40		D.1. Since RFC 7234 . . . . . . . . . . . . . . . . . . . . . 40
			D.2. Since draft-fielding-httpbis-cache-00 . . . . . . . . . . 40
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 42		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 42
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
	1. Introduction		1. Introduction
	HTTP is typically used for distributed information systems, where		HTTP is typically used for distributed information systems, where
	performance can be improved by the use of response caches. This		performance can be improved by the use of response caches. This
	document defines aspects of HTTP/1.1 related to caching and reusing		document defines aspects of HTTP/1.1 related to caching and reusing
	response messages.		response messages.
	skipping to change at page 36, line 11 ¶		skipping to change at page 36, line 11 ¶
	can be (and often is) used to satisfy subsequent requests to caches.		can be (and often is) used to satisfy subsequent requests to caches.
	Servers who wish to control caching of these responses are encouraged		Servers who wish to control caching of these responses are encouraged
	to emit appropriate Cache-Control response header fields.		to emit appropriate Cache-Control response header fields.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Authentication", draft-fielding-httpbis-		Protocol (HTTP): Authentication", draft-fielding-httpbis-
	http-auth-00 (work in progress), March 2018.		http-auth-latest (work in progress), 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.
	[RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,		[RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
	"Hypertext Transfer Protocol (HTTP): Range Requests",		"Hypertext Transfer Protocol (HTTP): Range Requests",
	draft-fielding-httpbis-http-range-00 (work in progress),		draft-fielding-httpbis-http-range-latest (work in
	March 2018.		progress), March 2018.
	[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.
	9.2. Informative References		9.2. Informative References
	[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,
	September 2004, <https://www.rfc-editor.org/info/bcp90>.		September 2004, <https://www.rfc-editor.org/info/bcp90>.
	[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,		[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext		Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
	Transfer Protocol -- HTTP/1.1", RFC 2616,		Transfer Protocol -- HTTP/1.1", RFC 2616,
	skipping to change at page 40, line 26 ¶		skipping to change at page 40, line 26 ¶
	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.
			D.2. Since draft-fielding-httpbis-cache-00
			None yet.
	Index		Index
	1		1
	110 (warn-code) 31		110 (warn-code) 31
	111 (warn-code) 31		111 (warn-code) 31
	112 (warn-code) 31		112 (warn-code) 31
	113 (warn-code) 31		113 (warn-code) 31
	199 (warn-code) 31		199 (warn-code) 31
	2		2
End of changes. 12 change blocks.
	11 lines changed or deleted		17 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/