draft-ietf-httpbis-cache-06.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: May 7, 2020 J. Reschke, Ed.		Expires: June 8, 2020 J. Reschke, Ed.
	greenbytes		greenbytes
	November 4, 2019		December 6, 2019
	HTTP Caching		HTTP Caching
	draft-ietf-httpbis-cache-06		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.7.		The changes in this draft are summarized in Appendix C.8.
	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 May 7, 2020.		This Internet-Draft will expire on June 8, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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 13 ¶		skipping to change at page 4, line 13 ¶
	Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 36		Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 36
	Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 36		Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 36
	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 . . . . . . . . . . . . 37		C.2. Since draft-ietf-httpbis-cache-00 . . . . . . . . . . . . 37
	C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 37		C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 37
	C.4. Since draft-ietf-httpbis-cache-02 . . . . . . . . . . . . 37		C.4. Since draft-ietf-httpbis-cache-02 . . . . . . . . . . . . 37
	C.5. Since draft-ietf-httpbis-cache-03 . . . . . . . . . . . . 38		C.5. Since draft-ietf-httpbis-cache-03 . . . . . . . . . . . . 38
	C.6. Since draft-ietf-httpbis-cache-04 . . . . . . . . . . . . 38		C.6. Since draft-ietf-httpbis-cache-04 . . . . . . . . . . . . 38
	C.7. Since draft-ietf-httpbis-cache-05 . . . . . . . . . . . . 38		C.7. Since draft-ietf-httpbis-cache-05 . . . . . . . . . . . . 38
			C.8. Since draft-ietf-httpbis-cache-06 . . . . . . . . . . . . 39
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 40		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 40
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
	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 28, line 41 ¶		skipping to change at page 28, line 41 ¶
	Argument syntax:		Argument syntax:
	delta-seconds (see Section 1.3)		delta-seconds (see Section 1.3)
	The "s-maxage" response directive indicates that, in shared caches,		The "s-maxage" response directive indicates that, in shared caches,
	the maximum age specified by this directive overrides the maximum age		the maximum age specified by this directive overrides the maximum age
	specified by either the max-age directive or the Expires header		specified by either the max-age directive or the Expires header
	field. The s-maxage directive also implies the semantics of the		field. The s-maxage directive also implies the semantics of the
	proxy-revalidate response directive.		proxy-revalidate response directive.
	The must-revalidate directive also has the effect of allowing a		The s-maxage directive also has the effect of allowing a stored
	stored response to be used to satisfy a request with an Authorization		response to be used to satisfy a request with an Authorization header
	header field; see Section 3.2.		field; see Section 3.2.
	This directive uses the token form of the argument syntax: e.g.,		This directive uses the token form of the argument syntax: e.g.,
	's-maxage=10' not 's-maxage="10"'. A sender SHOULD NOT generate the		's-maxage=10' not 's-maxage="10"'. A sender SHOULD NOT generate the
	quoted-string form.		quoted-string form.
	5.2.3. Cache Control Extensions		5.2.3. Cache Control Extensions
	The Cache-Control header field can be extended through the use of one		The Cache-Control header field can be extended through the use of one
	or more cache-extension tokens, each with an optional value. A cache		or more cache-extension tokens, each with an optional value. A cache
	MUST ignore unrecognized cache directives.		MUST ignore unrecognized cache directives.
	skipping to change at page 33, line 51 ¶		skipping to change at page 33, line 51 ¶
	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-		Ed., "HTTP/1.1 Messaging", draft-ietf-httpbis-messaging-
	latest (work in progress), November 2019.		latest (work in progress), December 2019.
	[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>.
	skipping to change at page 34, line 27 ¶		skipping to change at page 34, line 27 ¶
	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>.
	[RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF",		[RFC7405] Kyzivat, P., "Case-Sensitive String Support in ABNF",
	RFC 7405, DOI 10.17487/RFC7405, December 2014,		RFC 7405, DOI 10.17487/RFC7405, December 2014,
	<https://www.rfc-editor.org/info/rfc7405>.		<https://www.rfc-editor.org/info/rfc7405>.
	[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-latest		Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-latest
	(work in progress), November 2019.		(work in progress), December 2019.
	[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
	Transfer Protocol -- HTTP/1.1", RFC 2616,		Transfer Protocol -- HTTP/1.1", RFC 2616,
	skipping to change at page 38, line 39 ¶		skipping to change at page 38, line 39 ¶
	o In Section 5.2, remove the registrations for stale-if-error and		o In Section 5.2, remove the registrations for stale-if-error and
	stale-while-revalidate which happened in RFC 7234		stale-while-revalidate which happened in RFC 7234
	(<https://github.com/httpwg/http-core/issues/207>)		(<https://github.com/httpwg/http-core/issues/207>)
	C.7. Since draft-ietf-httpbis-cache-05		C.7. Since draft-ietf-httpbis-cache-05
	o In Section 3.1, clarify how weakly framed content is considered		o In Section 3.1, clarify how weakly framed content is considered
	for purposes of completeness (<https://github.com/httpwg/http-		for purposes of completeness (<https://github.com/httpwg/http-
	core/issues/25>)		core/issues/25>)
	o Througout, describe Vary and cache key operations more clearly		o Throughout, describe Vary and cache key operations more clearly
	(<https://github.com/httpwg/http-core/issues/28>)		(<https://github.com/httpwg/http-core/issues/28>)
	o In Section 3, remove concept of "cacheable methods" in favor of		o In Section 3, remove concept of "cacheable methods" in favor of
	prose (<https://github.com/httpwg/http-core/issues/54>)		prose (<https://github.com/httpwg/http-core/issues/54>,
			<https://www.rfc-editor.org/errata/eid5300>)
	o Refactored Section 7, and added a section on timing attacks		o Refactored Section 7, and added a section on timing attacks
	(<https://github.com/httpwg/http-core/issues/233>)		(<https://github.com/httpwg/http-core/issues/233>)
	o Changed "cacheable by default" to "heuristically cacheable"		o Changed "cacheable by default" to "heuristically cacheable"
	throughout (<https://github.com/httpwg/http-core/issues/242>)		throughout (<https://github.com/httpwg/http-core/issues/242>)
			C.8. Since draft-ietf-httpbis-cache-06
			o Fix typo in Section 5.2.2.9 (<https://github.com/httpwg/http-core/
			issues/264>)
	Index		Index
	A		A
	Age header field 21		Age header field 21
	age 12		age 12
	C		C
	Cache-Control header field 22		Cache-Control header field 22
	cache 4		cache 4
	cache key 6		cache key 6
End of changes. 12 change blocks.
	12 lines changed or deleted		19 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/