draft-ietf-httpbis-semantics-14.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
	Updates: 3864 (if approved) J. Reschke, Ed.		Updates: 3864 (if approved) J. Reschke, Ed.
	Intended status: Standards Track greenbytes		Intended status: Standards Track greenbytes
	Expires: July 17, 2021 January 13, 2021		Expires: July 20, 2021 January 16, 2021
	HTTP Semantics		HTTP Semantics
	draft-ietf-httpbis-semantics-14		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 describes the overall architecture of HTTP,		systems. This document describes the overall architecture of HTTP,
	establishes common terminology, and defines aspects of the protocol		establishes common terminology, and defines aspects of the protocol
	that are shared by all versions. In this definition are core		that are shared by all versions. In this definition are core
	protocol elements, extensibility mechanisms, and the "http" and		protocol elements, extensibility mechanisms, and the "http" and
	"https" Uniform Resource Identifier (URI) schemes.		"https" Uniform Resource Identifier (URI) schemes.
	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 C.15.		The changes in this draft are summarized in Appendix C.16.
	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 July 17, 2021.		This Internet-Draft will expire on July 20, 2021.
	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 2, line 42 ¶		skipping to change at page 2, line 42 ¶
	the copyright in such materials, this document may not be modified		the copyright in such materials, this document may not be modified
	outside the IETF Standards Process, and derivative works of it may		outside the IETF Standards Process, and derivative works of it may
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 9
	1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 9		1.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 9
	1.2. History and Evolution . . . . . . . . . . . . . . . . . . 10		1.2. History and Evolution . . . . . . . . . . . . . . . . . . 9
	1.3. Core Semantics . . . . . . . . . . . . . . . . . . . . . 10		1.3. Core Semantics . . . . . . . . . . . . . . . . . . . . . 10
	1.4. Specifications Obsoleted by this Document . . . . . . . . 11		1.4. Specifications Obsoleted by this Document . . . . . . . . 11
	2. Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 12		2. Conformance . . . . . . . . . . . . . . . . . . . . . . . . . 11
	2.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 12		2.1. Syntax Notation . . . . . . . . . . . . . . . . . . . . . 11
	2.2. Requirements Notation . . . . . . . . . . . . . . . . . . 12		2.2. Requirements Notation . . . . . . . . . . . . . . . . . . 12
	2.3. Length Requirements . . . . . . . . . . . . . . . . . . . 13		2.3. Length Requirements . . . . . . . . . . . . . . . . . . . 13
	2.4. Error Handling . . . . . . . . . . . . . . . . . . . . . 14		2.4. Error Handling . . . . . . . . . . . . . . . . . . . . . 14
	2.5. Protocol Version . . . . . . . . . . . . . . . . . . . . 14		2.5. Protocol Version . . . . . . . . . . . . . . . . . . . . 14
	3. Terminology and Core Concepts . . . . . . . . . . . . . . . . 15		3. Terminology and Core Concepts . . . . . . . . . . . . . . . . 15
	3.1. Resources . . . . . . . . . . . . . . . . . . . . . . . . 15		3.1. Resources . . . . . . . . . . . . . . . . . . . . . . . . 15
	3.2. Representations . . . . . . . . . . . . . . . . . . . . . 16		3.2. Representations . . . . . . . . . . . . . . . . . . . . . 16
	3.3. Connections, Clients and Servers . . . . . . . . . . . . 16		3.3. Connections, Clients and Servers . . . . . . . . . . . . 16
	3.4. Messages . . . . . . . . . . . . . . . . . . . . . . . . 17		3.4. Messages . . . . . . . . . . . . . . . . . . . . . . . . 17
	3.5. User Agents . . . . . . . . . . . . . . . . . . . . . . . 17		3.5. User Agents . . . . . . . . . . . . . . . . . . . . . . . 17
	skipping to change at page 9, line 5 ¶		skipping to change at page 9, line 5 ¶
	C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 215		C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 215
	C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 215		C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 215
	C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 217		C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 217
	C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 218		C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 218
	C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 219		C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 219
	C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 221		C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 221
	C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 221		C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 221
	C.13. Since draft-ietf-httpbis-semantics-11 . . . . . . . . . . 222		C.13. Since draft-ietf-httpbis-semantics-11 . . . . . . . . . . 222
	C.14. Since draft-ietf-httpbis-semantics-12 . . . . . . . . . . 223		C.14. Since draft-ietf-httpbis-semantics-12 . . . . . . . . . . 223
	C.15. Since draft-ietf-httpbis-semantics-13 . . . . . . . . . . 225		C.15. Since draft-ietf-httpbis-semantics-13 . . . . . . . . . . 225
			C.16. Since draft-ietf-httpbis-semantics-14 . . . . . . . . . . 225
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 225		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 225
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 226		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 226
	1. Introduction		1. Introduction
	1.1. Purpose		1.1. Purpose
	The Hypertext Transfer Protocol (HTTP) is a family of stateless,		The Hypertext Transfer Protocol (HTTP) is a family of stateless,
	application-level, request/response protocols that share a generic		application-level, request/response protocols that share a generic
	interface, extensible semantics, and self-descriptive messages to		interface, extensible semantics, and self-descriptive messages to
	skipping to change at page 225, line 39 ¶		skipping to change at page 225, line 39 ¶
	frames (<https://github.com/httpwg/http-core/issues/654>)		frames (<https://github.com/httpwg/http-core/issues/654>)
	o In Section 13.1.3, Section 13.1.4, and Section 13.1.5, specify		o In Section 13.1.3, Section 13.1.4, and Section 13.1.5, specify
	evaluation in a way similar to other conditional header fields		evaluation in a way similar to other conditional header fields
	(<https://github.com/httpwg/http-core/issues/665>)		(<https://github.com/httpwg/http-core/issues/665>)
	o In Section 10.2.2, specify that recipients can replace an invalid		o In Section 10.2.2, specify that recipients can replace an invalid
	Date header field value with the time received		Date header field value with the time received
	(<https://github.com/httpwg/http-core/issues/669>)		(<https://github.com/httpwg/http-core/issues/669>)
			C.16. Since draft-ietf-httpbis-semantics-14
			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,
	Jean-François Groff, Ari Luotonen, Roy T. Fielding, Henrik Frystyk		Jean-François Groff, Ari Luotonen, Roy T. Fielding, Henrik Frystyk
	Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter, Paul J.		Nielsen, Jim Gettys, Jeffrey C. Mogul, Larry Masinter, Paul J.
	Leach, Eric Rescorla, and Yves Lafon.		Leach, Eric Rescorla, and Yves Lafon.
End of changes. 8 change blocks.
	7 lines changed or deleted		12 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/