draft-ietf-httpbis-cache-03.txt		draft-ietf-httpbis-cache-latest.txt
	HTTP Working Group R. Fielding, Ed.		HTTP 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: April 21, 2019 J. Reschke, Ed.		Expires: April 21, 2019 J. Reschke, Ed.
	greenbytes		greenbytes
	October 18, 2018		October 18, 2018
	HTTP Caching		HTTP Caching
	draft-ietf-httpbis-cache-03		draft-ietf-httpbis-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 36 ¶		skipping to change at page 1, line 36 ¶
	This note is to be removed before publishing as an RFC.		This note is to be removed before publishing as an RFC.
	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
	<https://lists.w3.org/Archives/Public/ietf-http-wg/>.		<https://lists.w3.org/Archives/Public/ietf-http-wg/>.
	Working Group information can be found at <https://httpwg.org/>;		Working Group information can be found at <https://httpwg.org/>;
	source code and issues list for this draft can be found at		source code and issues list for this draft can be found at
	<https://github.com/httpwg/http-core>.		<https://github.com/httpwg/http-core>.
	The changes in this draft are summarized in Appendix C.4.		The changes in this draft are summarized in Appendix C.5.
	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/.
	skipping to change at page 4, line 7 ¶		skipping to change at page 4, line 7 ¶
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 32		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 32
	9.1. Normative References . . . . . . . . . . . . . . . . . . 32		9.1. Normative References . . . . . . . . . . . . . . . . . . 32
	9.2. Informative References . . . . . . . . . . . . . . . . . 33		9.2. Informative References . . . . . . . . . . . . . . . . . 33
	Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 35		Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 35
	Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 35		Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 35
	Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 36		Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 36
	C.1. Between RFC7234 and draft 00 . . . . . . . . . . . . . . 36		C.1. Between RFC7234 and draft 00 . . . . . . . . . . . . . . 36
	C.2. Since draft-ietf-httpbis-cache-00 . . . . . . . . . . . . 36		C.2. Since draft-ietf-httpbis-cache-00 . . . . . . . . . . . . 36
	C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 36		C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 36
	C.4. Since draft-ietf-httpbis-cache-02 . . . . . . . . . . . . 36		C.4. Since draft-ietf-httpbis-cache-02 . . . . . . . . . . . . 36
			C.5. Since draft-ietf-httpbis-cache-03 . . . . . . . . . . . . 37
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 39		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 39
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
	1. Introduction		1. Introduction
	The Hypertext Transfer Protocol (HTTP) is a stateless application-		The Hypertext Transfer Protocol (HTTP) is a stateless application-
	level request/response protocol that uses extensible semantics and		level request/response protocol that uses extensible semantics and
	self-descriptive messages for flexible interaction with network-based		self-descriptive messages for flexible interaction with network-based
	hypertext information systems. HTTP is defined by a series of		hypertext information systems. HTTP is defined by a series of
	skipping to change at page 32, line 50 ¶		skipping to change at page 32, line 50 ¶
	Please add a note to the "Hypertext Transfer Protocol (HTTP) Warn		Please add a note to the "Hypertext Transfer Protocol (HTTP) Warn
	Codes" registry at <https://www.iana.org/assignments/http-warn-codes>		Codes" registry at <https://www.iana.org/assignments/http-warn-codes>
	to the effect that Warning is obsoleted.		to the effect that Warning is obsoleted.
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[Messaging]		[Messaging]
	Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP/1.1 Messaging", draft-ietf-httpbis-messaging-03		Ed., "HTTP/1.1 Messaging", draft-ietf-httpbis-messaging-
	(work in progress), October 2018.		latest (work in progress), October 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>.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform		[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
	Resource Identifier (URI): Generic Syntax", STD 66,		Resource Identifier (URI): Generic Syntax", STD 66,
	RFC 3986, DOI 10.17487/RFC3986, January 2005,		RFC 3986, DOI 10.17487/RFC3986, January 2005,
	<https://www.rfc-editor.org/info/rfc3986>.		<https://www.rfc-editor.org/info/rfc3986>.
	[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>.
	[Semantics]		[Semantics]
	Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-03		Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-latest
	(work in progress), October 2018.		(work in progress), October 2018.
	[USASCII] American National Standards Institute, "Coded Character		[USASCII] American National Standards Institute, "Coded Character
	Set -- 7-bit American Standard Code for Information		Set -- 7-bit American Standard Code for Information
	Interchange", ANSI X3.4, 1986.		Interchange", ANSI X3.4, 1986.
	9.2. Informative References		9.2. Informative References
	[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
	skipping to change at page 37, line 20 ¶		skipping to change at page 37, line 20 ¶
	o Revise Section 6 to apply to more than just History Lists		o Revise Section 6 to apply to more than just History Lists
	(<https://github.com/httpwg/http-core/issues/126>)		(<https://github.com/httpwg/http-core/issues/126>)
	o In Section 5.5, deprecated "Warning" header field		o In Section 5.5, deprecated "Warning" header field
	(<https://github.com/httpwg/http-core/issues/139>)		(<https://github.com/httpwg/http-core/issues/139>)
	o In Section 3.2, remove a spurious note		o In Section 3.2, remove a spurious note
	(<https://github.com/httpwg/http-core/issues/141>)		(<https://github.com/httpwg/http-core/issues/141>)
			C.5. Since draft-ietf-httpbis-cache-03
			None yet.
	Index		Index
	A		A
	Age header field 21		Age header field 21
	age 11		age 11
	C		C
	Cache-Control header field 21		Cache-Control header field 21
	cache 4		cache 4
	cache entry 6		cache entry 6
End of changes. 6 change blocks.
	5 lines changed or deleted		10 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/