draft-fielding-httpbis-http-messaging-00.txt		draft-fielding-httpbis-http-messaging-latest.txt
	Network Working Group R. Fielding, Ed.		Network Working Group R. Fielding, Ed.
	Internet-Draft Adobe		Internet-Draft Adobe
	Obsoletes: 7230 (if approved) J. Reschke, Ed.		Obsoletes: 7230 (if approved) J. Reschke, Ed.
	Intended status: Standards Track greenbytes		Intended status: Standards Track greenbytes
	Expires: September 6, 2018 March 5, 2018		Expires: September 18, 2018 March 17, 2018
	Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing		Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
	draft-fielding-httpbis-http-messaging-00		draft-fielding-httpbis-http-messaging-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 provides an overview of HTTP architecture and		systems. This document provides an overview of HTTP architecture and
	its associated terminology, defines the "http" and "https" Uniform		its associated terminology, defines the "http" and "https" Uniform
	Resource Identifier (URI) schemes, defines the HTTP/1.1 message		Resource Identifier (URI) schemes, defines the HTTP/1.1 message
	syntax and parsing requirements, and describes related security		syntax and parsing requirements, and describes related security
	concerns for implementations.		concerns for implementations.
	skipping to change at page 1, line 40 ¶		skipping to change at page 1, line 40 ¶
	item of the HTTP Working Group._		item of the HTTP Working Group._
	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
	<http://lists.w3.org/Archives/Public/ietf-http-wg/>.		<http://lists.w3.org/Archives/Public/ietf-http-wg/>.
	Errata for RFC 7230 have been collected at <https://www.rfc-		Errata for RFC 7230 have been collected at <https://www.rfc-
	editor.org/errata_search.php?rfc=7230>, and an additional issues list		editor.org/errata_search.php?rfc=7230>, and an additional issues list
	lives at <https://github.com/httpwg/http11bis/issues>.		lives at <https://github.com/httpwg/http11bis/issues>.
	The changes in this draft are summarized in Appendix C.1.		The changes in this draft are summarized in Appendix C.2.
	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 September 6, 2018.		This Internet-Draft will expire on September 18, 2018.
	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 4, line 48 ¶		skipping to change at page 4, line 48 ¶
	10.2. Informative References . . . . . . . . . . . . . . . . . 72		10.2. Informative References . . . . . . . . . . . . . . . . . 72
	Appendix A. HTTP Version History . . . . . . . . . . . . . . . . 75		Appendix A. HTTP Version History . . . . . . . . . . . . . . . . 75
	A.1. Changes from HTTP/1.0 . . . . . . . . . . . . . . . . . . 75		A.1. Changes from HTTP/1.0 . . . . . . . . . . . . . . . . . . 75
	A.1.1. Multihomed Web Servers . . . . . . . . . . . . . . . 75		A.1.1. Multihomed Web Servers . . . . . . . . . . . . . . . 75
	A.1.2. Keep-Alive Connections . . . . . . . . . . . . . . . 76		A.1.2. Keep-Alive Connections . . . . . . . . . . . . . . . 76
	A.1.3. Introduction of Transfer-Encoding . . . . . . . . . . 76		A.1.3. Introduction of Transfer-Encoding . . . . . . . . . . 76
	A.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 77		A.2. Changes from RFC 7230 . . . . . . . . . . . . . . . . . . 77
	Appendix B. Collected ABNF . . . . . . . . . . . . . . . . . . . 77		Appendix B. Collected ABNF . . . . . . . . . . . . . . . . . . . 77
	Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 79		Appendix C. Change Log . . . . . . . . . . . . . . . . . . . . . 79
	C.1. Since RFC 7230 . . . . . . . . . . . . . . . . . . . . . 79		C.1. Since RFC 7230 . . . . . . . . . . . . . . . . . . . . . 79
			C.2. Since draft-fielding-httpbis-messaging-00 . . . . . . . . 80
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
	Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 84		Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 84
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 84
	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 message payloads for flexible interaction with		self-descriptive message payloads for flexible interaction with
	network-based hypertext information systems. This document is the		network-based hypertext information systems. This document is the
	skipping to change at page 70, line 49 ¶		skipping to change at page 70, line 49 ¶
	provided query parameters, as soon as that information is no longer		provided query parameters, as soon as that information is no longer
	necessary to support operational needs for security, auditing, or		necessary to support operational needs for security, auditing, or
	fraud control.		fraud control.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[AUTHFRM] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Authentication", draft-fielding-httpbis-		Protocol (HTTP): Authentication", draft-fielding-httpbis-
	http-auth-00 (work in progress), March 2018.		http-auth-latest (work in progress), March 2018.
	[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[CACHING] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft-		Ed., "Hypertext Transfer Protocol (HTTP): Caching", draft-
	fielding-httpbis-http-cache-00 (work in progress), March		fielding-httpbis-http-cache-latest (work in progress),
	2018.		March 2018.
	[CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[CONDTNL] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Conditional Requests", draft-fielding-		Protocol (HTTP): Conditional Requests", draft-fielding-
	httpbis-http-conditional-00 (work in progress), March		httpbis-http-conditional-latest (work in progress), March
	2018.		2018.
	[RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,		[RANGERQ] Fielding, R., Ed., Lafon, Y., Ed., and J. Reschke, Ed.,
	"Hypertext Transfer Protocol (HTTP): Range Requests",		"Hypertext Transfer Protocol (HTTP): Range Requests",
	draft-fielding-httpbis-http-range-00 (work in progress),		draft-fielding-httpbis-http-range-latest (work in
	March 2018.		progress), March 2018.
	[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. and J-L. Gailly, "ZLIB Compressed Data Format		[RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data Format
	Specification version 3.3", RFC 1950,		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 72, line 7 ¶		skipping to change at page 72, line 7 ¶
	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>.
	[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer		[SEMNTCS] Fielding, R., Ed. and J. Reschke, Ed., "Hypertext Transfer
	Protocol (HTTP): Semantics and Content", draft-fielding-		Protocol (HTTP): Semantics and Content", draft-fielding-
	httpbis-http-semantics-00 (work in progress), March 2018.		httpbis-http-semantics-latest (work in progress), March
			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.
	[Welch] Welch, T., "A Technique for High-Performance Data		[Welch] Welch, T., "A Technique for High-Performance Data
	Compression", IEEE Computer 17(6), June 1984.		Compression", IEEE Computer 17(6), June 1984.
	10.2. Informative References		10.2. Informative References
	skipping to change at page 80, line 5 ¶		skipping to change at page 80, line 5 ¶
	o Update links to sibling specifications.		o Update links to sibling specifications.
	o Replace sections listing changes from RFC 2616 by new empty		o Replace sections listing changes from RFC 2616 by new empty
	sections referring to RFC 723x.		sections referring to RFC 723x.
	o Remove acknowledgements specific to RFC 723x.		o Remove acknowledgements specific to RFC 723x.
	o Move "Acknowledgements" to the very end and make them unnumbered.		o Move "Acknowledgements" to the very end and make them unnumbered.
			C.2. Since draft-fielding-httpbis-messaging-00
			None yet.
	Index		Index
	A		A
	absolute-form (of request-target) 41		absolute-form (of request-target) 41
	accelerator 10		accelerator 10
	application/http Media Type 62		application/http Media Type 62
	asterisk-form (of request-target) 42		asterisk-form (of request-target) 42
	authoritative response 66		authoritative response 66
	authority-form (of request-target) 42		authority-form (of request-target) 42
End of changes. 11 change blocks.
	11 lines changed or deleted		17 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/