draft-ietf-httpbis-cache-19.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: March 14, 2022 J. Reschke, Ed.		Expires: April 11, 2022 J. Reschke, Ed.
	greenbytes		greenbytes
	September 10, 2021		October 8, 2021
	HTTP Caching		HTTP Caching
	draft-ietf-httpbis-cache-19		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.20.		The changes in this draft are summarized in Appendix C.21.
	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 March 14, 2022.		This Internet-Draft will expire on April 11, 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2021 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	skipping to change at page 4, line 31 ¶		skipping to change at page 4, line 31 ¶
	C.11. Since draft-ietf-httpbis-cache-09 . . . . . . . . . . . . 43		C.11. Since draft-ietf-httpbis-cache-09 . . . . . . . . . . . . 43
	C.12. Since draft-ietf-httpbis-cache-10 . . . . . . . . . . . . 43		C.12. Since draft-ietf-httpbis-cache-10 . . . . . . . . . . . . 43
	C.13. Since draft-ietf-httpbis-cache-11 . . . . . . . . . . . . 43		C.13. Since draft-ietf-httpbis-cache-11 . . . . . . . . . . . . 43
	C.14. Since draft-ietf-httpbis-cache-12 . . . . . . . . . . . . 43		C.14. Since draft-ietf-httpbis-cache-12 . . . . . . . . . . . . 43
	C.15. Since draft-ietf-httpbis-cache-13 . . . . . . . . . . . . 45		C.15. Since draft-ietf-httpbis-cache-13 . . . . . . . . . . . . 45
	C.16. Since draft-ietf-httpbis-cache-14 . . . . . . . . . . . . 45		C.16. Since draft-ietf-httpbis-cache-14 . . . . . . . . . . . . 45
	C.17. Since draft-ietf-httpbis-cache-15 . . . . . . . . . . . . 46		C.17. Since draft-ietf-httpbis-cache-15 . . . . . . . . . . . . 46
	C.18. Since draft-ietf-httpbis-cache-16 . . . . . . . . . . . . 46		C.18. Since draft-ietf-httpbis-cache-16 . . . . . . . . . . . . 46
	C.19. Since draft-ietf-httpbis-cache-17 . . . . . . . . . . . . 46		C.19. Since draft-ietf-httpbis-cache-17 . . . . . . . . . . . . 46
	C.20. Since draft-ietf-httpbis-cache-18 . . . . . . . . . . . . 46		C.20. Since draft-ietf-httpbis-cache-18 . . . . . . . . . . . . 46
	Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 46		C.21. Since draft-ietf-httpbis-cache-19 . . . . . . . . . . . . 46
			Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 47
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 49
	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. It is typically used for distributed		hypertext information systems. It is typically used for distributed
	information systems, where the use of response caches can improve		information systems, where the use of response caches can improve
	performance. This document defines aspects of HTTP related to		performance. This document defines aspects of HTTP related to
	caching and reusing response messages.		caching and reusing response messages.
	skipping to change at page 36, line 40 ¶		skipping to change at page 36, line 40 ¶
	First, introduce the new "Hypertext Transfer Protocol (HTTP) Field		First, introduce the new "Hypertext Transfer Protocol (HTTP) Field
	Name Registry" at <https://www.iana.org/assignments/http-fields> as		Name Registry" at <https://www.iana.org/assignments/http-fields> as
	described in Section 18.4 of [HTTP].		described in Section 18.4 of [HTTP].
	Then, please update the registry with the field names listed in the		Then, please update the registry with the field names listed in the
	table below:		table below:
	+---------------+-----------+------+----------+		+---------------+-----------+------+----------+
	| Field Name | Status | Ref. | Comments |		| Field Name | Status | Ref. | Comments |
	+---------------+-----------+------+----------+		+---------------+-----------+------+----------+
	| Age | standard | 5.1 | |		| Age | permanent | 5.1 | |
	| Cache-Control | standard | 5.2 | |		| Cache-Control | permanent | 5.2 | |
	| Expires | standard | 5.3 | |		| Expires | permanent | 5.3 | |
	| Pragma | standard | 5.4 | |		| Pragma | permanent | 5.4 | |
	| Warning | obsoleted | 5.5 | |		| Warning | obsoleted | 5.5 | |
	+---------------+-----------+------+----------+		+---------------+-----------+------+----------+
	Table 1		Table 1
	8.2. Cache Directive Registration		8.2. Cache Directive Registration
	Please update the "Hypertext Transfer Protocol (HTTP) Cache Directive		Please update the "Hypertext Transfer Protocol (HTTP) Cache Directive
	Registry" at <https://www.iana.org/assignments/http-cache-directives>		Registry" at <https://www.iana.org/assignments/http-cache-directives>
	with the registration procedure of Section 5.2.4 and the cache		with the registration procedure of Section 5.2.4 and the cache
	skipping to change at page 37, line 44 ¶		skipping to change at page 37, line 44 ¶
	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
	[HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Semantics", Work in Progress, Internet-Draft,		Ed., "HTTP Semantics", Work in Progress, Internet-Draft,
	draft-ietf-httpbis-semantics-latest, September 2021,		draft-ietf-httpbis-semantics-latest, October 2021,
	<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-		<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-
	semantics-latest>.		semantics-latest>.
	[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,
	skipping to change at page 38, line 26 ¶		skipping to change at page 38, line 26 ¶
	May 2017, <https://www.rfc-editor.org/info/rfc8174>.		May 2017, <https://www.rfc-editor.org/info/rfc8174>.
	9.2. Informative References		9.2. Informative References
	[COOKIE] Barth, A., "HTTP State Management Mechanism", RFC 6265,		[COOKIE] Barth, A., "HTTP State Management Mechanism", RFC 6265,
	DOI 10.17487/RFC6265, April 2011,		DOI 10.17487/RFC6265, April 2011,
	<https://www.rfc-editor.org/info/rfc6265>.		<https://www.rfc-editor.org/info/rfc6265>.
	[HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[HTTP/1.1] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP/1.1", Work in Progress, Internet-Draft, draft-		Ed., "HTTP/1.1", Work in Progress, Internet-Draft, draft-
	ietf-httpbis-messaging-latest, September 2021,		ietf-httpbis-messaging-latest, October 2021,
	<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-		<https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-
	messaging-latest>.		messaging-latest>.
	[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,
	DOI 10.17487/RFC2616, June 1999,		DOI 10.17487/RFC2616, June 1999,
	<https://www.rfc-editor.org/info/rfc2616>.		<https://www.rfc-editor.org/info/rfc2616>.
	[RFC5861] Nottingham, M., "HTTP Cache-Control Extensions for Stale		[RFC5861] Nottingham, M., "HTTP Cache-Control Extensions for Stale
	skipping to change at page 46, line 44 ¶		skipping to change at page 46, line 44 ¶
	o Use term "clock" defined in Section 6.6.1 of [HTTP] throughout		o Use term "clock" defined in Section 6.6.1 of [HTTP] throughout
	(<https://github.com/httpwg/http-core/issues/953>)		(<https://github.com/httpwg/http-core/issues/953>)
	o Throughout, disambiguate "selected representation" and "selected		o Throughout, disambiguate "selected representation" and "selected
	response" (now "chosen response") (<https://github.com/httpwg/		response" (now "chosen response") (<https://github.com/httpwg/
	http-core/issues/958>)		http-core/issues/958>)
	C.20. Since draft-ietf-httpbis-cache-18		C.20. Since draft-ietf-httpbis-cache-18
			o In Section 8.1, change status 'standard' to 'permanent'
			(<https://github.com/httpwg/http-core/issues/978>)
			C.21. Since draft-ietf-httpbis-cache-19
	o None.		o None.
	Acknowledgements		Acknowledgements
	See Appendix "Acknowledgements" of [HTTP].		See Appendix "Acknowledgements" of [HTTP].
	Index		Index
	A C E F G H M N O P S V W		A C E F G H M N O P S V W
End of changes. 11 change blocks.
	13 lines changed or deleted		19 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/