draft-ietf-httpbis-cache-02.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: January 3, 2019 J. Reschke, Ed.		Expires: February 10, 2019 J. Reschke, Ed.
	greenbytes		greenbytes
	July 2, 2018		August 9, 2018
	HTTP Caching		HTTP Caching
	draft-ietf-httpbis-cache-02		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.3.		The changes in this draft are summarized in Appendix C.4.
	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 January 3, 2019.		This Internet-Draft will expire on February 10, 2019.
	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 46 ¶		skipping to change at page 3, line 46 ¶
	8.3. Warn Code Registration . . . . . . . . . . . . . . . . . 36		8.3. Warn Code Registration . . . . . . . . . . . . . . . . . 36
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 36
	9.1. Normative References . . . . . . . . . . . . . . . . . . 36		9.1. Normative References . . . . . . . . . . . . . . . . . . 36
	9.2. Informative References . . . . . . . . . . . . . . . . . 37		9.2. Informative References . . . . . . . . . . . . . . . . . 37
	Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 38		Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 38
	Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 39		Appendix B. Changes from RFC 7234 . . . . . . . . . . . . . . . 39
	Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 39		Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 39
	C.1. Between RFC7234 and draft 00 . . . . . . . . . . . . . . 39		C.1. Between RFC7234 and draft 00 . . . . . . . . . . . . . . 39
	C.2. Since draft-ietf-httpbis-cache-00 . . . . . . . . . . . . 39		C.2. Since draft-ietf-httpbis-cache-00 . . . . . . . . . . . . 39
	C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 39		C.3. Since draft-ietf-httpbis-cache-01 . . . . . . . . . . . . 39
			C.4. Since draft-ietf-httpbis-cache-02 . . . . . . . . . . . . 40
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 42		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 42
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 42
	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 36, line 37 ¶		skipping to change at page 36, line 37 ¶
	registry at <https://www.iana.org/assignments/http-warn-codes> with		registry at <https://www.iana.org/assignments/http-warn-codes> with
	the registration procedure of Section 5.5.8 and the warn code values		the registration procedure of Section 5.5.8 and the warn code values
	summarized in the table of Section 5.5.		summarized in the table of Section 5.5.
	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-02		Ed., "HTTP/1.1 Messaging", draft-ietf-httpbis-messaging-
	(work in progress), July 2018.		latest (work in progress), August 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-02		Ed., "HTTP Semantics", draft-ietf-httpbis-semantics-latest
	(work in progress), July 2018.		(work in progress), August 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
	Transfer Protocol -- HTTP/1.1", RFC 2616,		Transfer Protocol -- HTTP/1.1", RFC 2616,
	skipping to change at page 40, line 5 ¶		skipping to change at page 40, line 5 ¶
	C.3. Since draft-ietf-httpbis-cache-01		C.3. Since draft-ietf-httpbis-cache-01
	o Cite RFC 8126 instead of RFC 5226 (<https://github.com/httpwg/		o Cite RFC 8126 instead of RFC 5226 (<https://github.com/httpwg/
	http-core/issues/75>)		http-core/issues/75>)
	o In Section 5.4, misleading statement about the relation between		o In Section 5.4, misleading statement about the relation between
	Pragma and Cache-Control (<https://github.com/httpwg/http-core/		Pragma and Cache-Control (<https://github.com/httpwg/http-core/
	issues/92>, <https://www.rfc-editor.org/errata/eid4674>)		issues/92>, <https://www.rfc-editor.org/errata/eid4674>)
			C.4. Since draft-ietf-httpbis-cache-02
			None yet.
	Index		Index
	1		1
	110 (warn-code) 33		110 (warn-code) 33
	111 (warn-code) 33		111 (warn-code) 33
	112 (warn-code) 33		112 (warn-code) 33
	113 (warn-code) 34		113 (warn-code) 34
	199 (warn-code) 34		199 (warn-code) 34
	2		2
End of changes. 9 change blocks.
	9 lines changed or deleted		14 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/