Diff: draft-ietf-httpbis-semantics-11.txt - draft-ietf-httpbis-semantics-latest.txt

	draft-ietf-httpbis-semantics-11.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. Reschke, Ed.
	Expires: February 28, 2021 greenbytes	Expires: April 2, 2021 greenbytes
	August 27, 2020	September 29, 2020

	HTTP Semantics	HTTP Semantics

	draft-ietf-httpbis-semantics-11	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 C.12.	The changes in this draft are summarized in Appendix C.13.

	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 February 28, 2021.	This Internet-Draft will expire on April 2, 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 35 ¶	skipping to change at page 7, line 35 ¶
	13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 187	13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 187
	13.1. URI Scheme Registration . . . . . . . . . . . . . . . . 187	13.1. URI Scheme Registration . . . . . . . . . . . . . . . . 187
	13.2. Method Registration . . . . . . . . . . . . . . . . . . 187	13.2. Method Registration . . . . . . . . . . . . . . . . . . 187
	13.3. Status Code Registration . . . . . . . . . . . . . . . . 187	13.3. Status Code Registration . . . . . . . . . . . . . . . . 187
	13.4. HTTP Field Name Registration . . . . . . . . . . . . . . 188	13.4. HTTP Field Name Registration . . . . . . . . . . . . . . 188
	13.5. Authentication Scheme Registration . . . . . . . . . . . 189	13.5. Authentication Scheme Registration . . . . . . . . . . . 189
	13.6. Content Coding Registration . . . . . . . . . . . . . . 189	13.6. Content Coding Registration . . . . . . . . . . . . . . 189
	13.7. Range Unit Registration . . . . . . . . . . . . . . . . 189	13.7. Range Unit Registration . . . . . . . . . . . . . . . . 189
	13.8. Media Type Registration . . . . . . . . . . . . . . . . 189	13.8. Media Type Registration . . . . . . . . . . . . . . . . 189
	13.9. Port Registration . . . . . . . . . . . . . . . . . . . 189	13.9. Port Registration . . . . . . . . . . . . . . . . . . . 189

		13.10. Upgrade Token Registration . . . . . . . . . . . . . . . 189
	14. References . . . . . . . . . . . . . . . . . . . . . . . . . 189	14. References . . . . . . . . . . . . . . . . . . . . . . . . . 189

	14.1. Normative References . . . . . . . . . . . . . . . . . . 189	14.1. Normative References . . . . . . . . . . . . . . . . . . 190
	14.2. Informative References . . . . . . . . . . . . . . . . . 191	14.2. Informative References . . . . . . . . . . . . . . . . . 192
	Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 197	Appendix A. Collected ABNF . . . . . . . . . . . . . . . . . . . 197
	Appendix B. Changes from previous RFCs . . . . . . . . . . . . . 202	Appendix B. Changes from previous RFCs . . . . . . . . . . . . . 202
	B.1. Changes from RFC 2818 . . . . . . . . . . . . . . . . . . 202	B.1. Changes from RFC 2818 . . . . . . . . . . . . . . . . . . 202
	B.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 202	B.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 202

	B.3. Changes from RFC 7231 . . . . . . . . . . . . . . . . . . 203	B.3. Changes from RFC 7231 . . . . . . . . . . . . . . . . . . 204
	B.4. Changes from RFC 7232 . . . . . . . . . . . . . . . . . . 204	B.4. Changes from RFC 7232 . . . . . . . . . . . . . . . . . . 205
	B.5. Changes from RFC 7233 . . . . . . . . . . . . . . . . . . 205	B.5. Changes from RFC 7233 . . . . . . . . . . . . . . . . . . 205
	B.6. Changes from RFC 7235 . . . . . . . . . . . . . . . . . . 205	B.6. Changes from RFC 7235 . . . . . . . . . . . . . . . . . . 205
	B.7. Changes from RFC 7538 . . . . . . . . . . . . . . . . . . 205	B.7. Changes from RFC 7538 . . . . . . . . . . . . . . . . . . 205
	B.8. Changes from RFC 7615 . . . . . . . . . . . . . . . . . . 205	B.8. Changes from RFC 7615 . . . . . . . . . . . . . . . . . . 205
	B.9. Changes from RFC 7694 . . . . . . . . . . . . . . . . . . 205	B.9. Changes from RFC 7694 . . . . . . . . . . . . . . . . . . 205
	Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 205	Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 205

	C.1. Between RFC723x and draft 00 . . . . . . . . . . . . . . 205	C.1. Between RFC723x and draft 00 . . . . . . . . . . . . . . 206
	C.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 206	C.2. Since draft-ietf-httpbis-semantics-00 . . . . . . . . . . 206
	C.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 206	C.3. Since draft-ietf-httpbis-semantics-01 . . . . . . . . . . 206
	C.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 208	C.4. Since draft-ietf-httpbis-semantics-02 . . . . . . . . . . 208

	C.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 208	C.5. Since draft-ietf-httpbis-semantics-03 . . . . . . . . . . 209
	C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 209	C.6. Since draft-ietf-httpbis-semantics-04 . . . . . . . . . . 210
	C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 210	C.7. Since draft-ietf-httpbis-semantics-05 . . . . . . . . . . 210
	C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 211	C.8. Since draft-ietf-httpbis-semantics-06 . . . . . . . . . . 211

	C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 212	C.9. Since draft-ietf-httpbis-semantics-07 . . . . . . . . . . 213
	C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 214	C.10. Since draft-ietf-httpbis-semantics-08 . . . . . . . . . . 214
	C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 215	C.11. Since draft-ietf-httpbis-semantics-09 . . . . . . . . . . 215
	C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 215	C.12. Since draft-ietf-httpbis-semantics-10 . . . . . . . . . . 215

		C.13. Since draft-ietf-httpbis-semantics-11 . . . . . . . . . . 217
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 217	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 217

	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 217	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 218

	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
	enable flexible interaction with network-based hypertext information	enable flexible interaction with network-based hypertext information
	systems.	systems.

	skipping to change at page 189, line 45 ¶	skipping to change at page 189, line 45 ¶
	Please update the "Service Name and Transport Protocol Port Number"	Please update the "Service Name and Transport Protocol Port Number"
	registry at <https://www.iana.org/assignments/service-names-port-	registry at <https://www.iana.org/assignments/service-names-port-
	numbers/> for the services on ports 80 and 443 that use UDP or TCP	numbers/> for the services on ports 80 and 443 that use UDP or TCP
	to:	to:

	1. use this document as "Reference", and	1. use this document as "Reference", and

	2. when currently unspecified, set "Assignee" to "IESG" and	2. when currently unspecified, set "Assignee" to "IESG" and
	"Contact" to "IETF_Chair".	"Contact" to "IETF_Chair".


	14. References	13.10. Upgrade Token Registration

		Please update the "Hypertext Transfer Protocol (HTTP) Upgrade Token
		Registry" at <https://www.iana.org/assignments/http-upgrade-tokens>
		with the registration procedure of Section 6.7.2 and the upgrade
		token names summarized in the table of Section 6.7.1.


		14. References
	14.1. Normative References	14.1. Normative References


	[Caching] Fielding, R., Ed., Nottingham, M., Ed., and J. F. Reschke,	[Caching] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Caching", Work in Progress, Internet-Draft,	Ed., "HTTP Caching", Work in Progress, Internet-Draft,

	draft-ietf-httpbis-cache-11, August 27, 2020,	draft-ietf-httpbis-cache-latest, September 2020,
	<https://tools.ietf.org/html/draft-ietf-httpbis-cache-11>.	<https://tools.ietf.org/html/draft-ietf-httpbis-cache-
		latest>.

	[Messaging]	[Messaging]

	Fielding, R., Ed., Nottingham, M., Ed., and J. F. Reschke,	Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP/1.1 Messaging", Work in Progress, Internet-	Ed., "HTTP/1.1 Messaging", Work in Progress, Internet-

	Draft, draft-ietf-httpbis-messaging-11, August 27, 2020,	Draft, draft-ietf-httpbis-messaging-latest, September
	<https://tools.ietf.org/html/draft-ietf-httpbis-messaging-	2020, <https://tools.ietf.org/html/draft-ietf-httpbis-
	11>.	messaging-latest>.

	[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,	[RFC0793] Postel, J., "Transmission Control Protocol", STD 7,
	RFC 793, DOI 10.17487/RFC0793, September 1981,	RFC 793, DOI 10.17487/RFC0793, September 1981,
	<https://www.rfc-editor.org/info/rfc793>.	<https://www.rfc-editor.org/info/rfc793>.

	[RFC1950] Deutsch, L.P. and J-L. Gailly, "ZLIB Compressed Data	[RFC1950] Deutsch, L.P. and J-L. Gailly, "ZLIB Compressed Data
	Format Specification version 3.3", RFC 1950,	Format Specification version 3.3", RFC 1950,
	DOI 10.17487/RFC1950, May 1996,	DOI 10.17487/RFC1950, May 1996,
	<https://www.rfc-editor.org/info/rfc1950>.	<https://www.rfc-editor.org/info/rfc1950>.


	skipping to change at page 217, line 20 ¶	skipping to change at page 217, line 34 ¶
	o Moved definitions of "TE" and "Upgrade" from [Messaging]	o Moved definitions of "TE" and "Upgrade" from [Messaging]
	(<https://github.com/httpwg/http-core/issues/392>)	(<https://github.com/httpwg/http-core/issues/392>)

	o Moved 1.1-specific discussion of TLS to Messaging and rewrote	o Moved 1.1-specific discussion of TLS to Messaging and rewrote
	Section 6.3.3.3 to refer to RFC6125 (<https://github.com/httpwg/	Section 6.3.3.3 to refer to RFC6125 (<https://github.com/httpwg/
	http-core/issues/404>)	http-core/issues/404>)

	o Moved definition of "Connection" from [Messaging]	o Moved definition of "Connection" from [Messaging]
	(<https://github.com/httpwg/http-core/issues/407>)	(<https://github.com/httpwg/http-core/issues/407>)


		C.13. Since draft-ietf-httpbis-semantics-11

		o Move IANA Upgrade Token Registry instructions from [Messaging]
		(<https://github.com/httpwg/http-core/issues/450>)

	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.


	skipping to change at page 218, line 4 ¶	skipping to change at page 218, line 24 ¶
	Authors' Addresses	Authors' Addresses

	Roy T. Fielding (editor)	Roy T. Fielding (editor)
	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	Prahran VIC
	Australia	Australia

	Email: mnot@mnot.net	Email: mnot@mnot.net
	URI: https://www.mnot.net/	URI: https://www.mnot.net/


	Julian F. Reschke (editor)	Julian Reschke (editor)
	greenbytes GmbH	greenbytes GmbH
	Hafenweg 16	Hafenweg 16
	48155 Münster	48155 Münster
	Germany	Germany

	Email: julian.reschke@greenbytes.de	Email: julian.reschke@greenbytes.de
	URI: https://greenbytes.de/tech/webdav/	URI: https://greenbytes.de/tech/webdav/

End of changes. 21 change blocks.
	24 lines changed or deleted	39 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/