draft-ietf-httpbis-semantics-10.txt		draft-ietf-httpbis-semantics-latest.txt
	HTTP Working Group R. Fielding, Ed.		HTTP Working Group R. Fielding, Ed.
	Internet-Draft Adobe		Internet-Draft Adobe
	Obsoletes: 2818, 7230, 7231, 7232, 7233, 7235, M. Nottingham, Ed.		Obsoletes: 2818, 7230, 7231, 7232, 7233, 7235, M. Nottingham, Ed.
	7538, 7615, 7694 (if approved) Fastly		7538, 7615, 7694 (if approved) Fastly
	Intended status: Standards Track J. F. Reschke, Ed.		Intended status: Standards Track J. F. Reschke, Ed.
	Expires: January 13, 2021 greenbytes		Expires: January 14, 2021 greenbytes
	July 12, 2020		July 13, 2020
	HTTP Semantics		HTTP Semantics
	draft-ietf-httpbis-semantics-10		draft-ietf-httpbis-semantics-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 the semantics of HTTP: its		systems. This document defines the semantics of HTTP: its
	architecture, terminology, the "http" and "https" Uniform Resource		architecture, terminology, the "http" and "https" Uniform Resource
	Identifier (URI) schemes, core request methods, request header		Identifier (URI) schemes, core request methods, request header
	fields, response status codes, response header fields, and content		fields, response status codes, response header fields, and content
	negotiation.		negotiation.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 D.11.		The changes in this draft are summarized in Appendix D.12.
	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 13, 2021.		This Internet-Draft will expire on January 14, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 7, line 51 ¶		skipping to change at page 7, line 51 ¶
	D.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 195		D.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 195
	D.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 196		D.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 196
	D.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 197		D.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 197
	D.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 198		D.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 198
	D.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 199		D.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 199
	D.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 199		D.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 199
	D.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 201		D.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 201
	D.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 202		D.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 202
	D.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 203		D.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 203
	D.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 204		D.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 204
			D.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 205
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 205		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 205
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 205		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 205
	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
	documents that collectively form the HTTP/1.1 specification:		documents that collectively form the HTTP/1.1 specification:
	skipping to change at page 205, line 7 ¶		skipping to change at page 205, line 7 ¶
	cacheable status codes (<https://github.com/httpwg/http-core/		cacheable status codes (<https://github.com/httpwg/http-core/
	issues/385>)		issues/385>)
	o In Section 7.2.2, make it clearer that "identity" is not to be		o In Section 7.2.2, make it clearer that "identity" is not to be
	included (<https://github.com/httpwg/http-core/issues/388>)		included (<https://github.com/httpwg/http-core/issues/388>)
	D.11. Since draft-ietf-httpbis-semantics-09		D.11. Since draft-ietf-httpbis-semantics-09
	o Switch to xml2rfc v3 mode for draft generation		o Switch to xml2rfc v3 mode for draft generation
	(<https://github.com/httpwg/http-core/issues/394>)		(<https://github.com/httpwg/http-core/issues/394>)
			D.12. Since draft-ietf-httpbis-semantics-10
			o None yet.
	Acknowledgments		Acknowledgments
	This edition of the HTTP specification builds on the many		This edition of the HTTP specification builds on the many
	contributions that went into RFC 1945, RFC 2068, RFC 2145, RFC 2616,		contributions that went into RFC 1945, RFC 2068, RFC 2145, RFC 2616,
	and RFC 2818, including substantial contributions made by the		and RFC 2818, including substantial contributions made by the
	previous authors, editors, and Working Group Chairs: Tim Berners-Lee,		previous authors, editors, and Working Group Chairs: Tim Berners-Lee,
	Ari Luotonen, Roy T. Fielding, Henrik Frystyk Nielsen, Jim Gettys,		Ari Luotonen, Roy T. Fielding, Henrik Frystyk Nielsen, Jim Gettys,
	Jeffrey C. Mogul, Larry Masinter, Paul J. Leach, Eric Rescorla, and		Jeffrey C. Mogul, Larry Masinter, Paul J. Leach, Eric Rescorla, and
	Yves Lafon.		Yves Lafon.
	skipping to change at page 205, line 42 ¶		skipping to change at page 205, line 46 ¶
	Adobe		Adobe
	345 Park Ave		345 Park Ave
	San Jose, CA 95110		San Jose, CA 95110
	United States of America		United States of America
	Email: fielding@gbiv.com		Email: fielding@gbiv.com
	URI: https://roy.gbiv.com/		URI: https://roy.gbiv.com/
	Mark Nottingham (editor)		Mark Nottingham (editor)
	Fastly		Fastly
			Prahran VIC
			Australia
	Email: mnot@mnot.net		Email: mnot@mnot.net
	URI: https://www.mnot.net/		URI: https://www.mnot.net/
	Julian F. Reschke (editor)		Julian F. Reschke (editor)
	greenbytes GmbH		greenbytes GmbH
	Hafenweg 16		Hafenweg 16
	48155 Münster		48155 Münster
	Germany		Germany
End of changes. 7 change blocks.
	5 lines changed or deleted		13 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/