draft-ietf-httpbis-p1-messaging-11.txt		draft-ietf-httpbis-p1-messaging-latest.txt
	HTTPbis Working Group R. Fielding, Ed.		HTTPbis Working Group R. Fielding, Ed.
	Internet-Draft Day Software		Internet-Draft Day Software
	Obsoletes: 2616 (if approved) J. Gettys		Obsoletes: 2616 (if approved) J. Gettys
	Updates: 2817 (if approved) Alcatel-Lucent		Updates: 2817 (if approved) Alcatel-Lucent
	Intended status: Standards Track J. Mogul		Intended status: Standards Track J. Mogul
	Expires: February 5, 2011 HP		Expires: March 6, 2011 HP
	H. Frystyk		H. Frystyk
	Microsoft		Microsoft
	L. Masinter		L. Masinter
	Adobe Systems		Adobe Systems
	P. Leach		P. Leach
	Microsoft		Microsoft
	T. Berners-Lee		T. Berners-Lee
	W3C/MIT		W3C/MIT
	Y. Lafon, Ed.		Y. Lafon, Ed.
	W3C		W3C
	J. Reschke, Ed.		J. Reschke, Ed.
	greenbytes		greenbytes
	August 4, 2010		September 2, 2010
	HTTP/1.1, part 1: URIs, Connections, and Message Parsing		HTTP/1.1, part 1: URIs, Connections, and Message Parsing
	draft-ietf-httpbis-p1-messaging-11		draft-ietf-httpbis-p1-messaging-latest
	Abstract		Abstract
	The Hypertext Transfer Protocol (HTTP) is an application-level		The Hypertext Transfer Protocol (HTTP) is an application-level
	protocol for distributed, collaborative, hypertext information		protocol for distributed, collaborative, hypertext information
	systems. HTTP has been in use by the World Wide Web global		systems. HTTP has been in use by the World Wide Web global
	information initiative since 1990. This document is Part 1 of the		information initiative since 1990. This document is Part 1 of the
	seven-part specification that defines the protocol referred to as		seven-part specification that defines the protocol referred to as
	"HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides		"HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides
	an overview of HTTP and its associated terminology, defines the		an overview of HTTP and its associated terminology, defines the
	skipping to change at page 1, line 47		skipping to change at page 1, line 47
	frames, and describes general security concerns for implementations.		frames, and describes general security concerns for implementations.
	Editorial Note (To be removed by RFC Editor)		Editorial Note (To be removed by RFC Editor)
	Discussion of this draft should take place on the HTTPBIS working		Discussion of this draft should take place on the HTTPBIS working
	group mailing list (ietf-http-wg@w3.org). The current issues list is		group mailing list (ietf-http-wg@w3.org). The current issues list is
	at <http://tools.ietf.org/wg/httpbis/trac/report/3> and related		at <http://tools.ietf.org/wg/httpbis/trac/report/3> and related
	documents (including fancy diffs) can be found at		documents (including fancy diffs) can be found at
	<http://tools.ietf.org/wg/httpbis/>.		<http://tools.ietf.org/wg/httpbis/>.
	The changes in this draft are summarized in Appendix D.12.		The changes in this draft are summarized in Appendix D.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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 5, 2011.		This Internet-Draft will expire on March 6, 2011.
	Copyright Notice		Copyright Notice
	Copyright (c) 2010 IETF Trust and the persons identified as the		Copyright (c) 2010 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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 5, line 14		skipping to change at page 5, line 14
	D.3. Since draft-ietf-httpbis-p1-messaging-01 . . . . . . . . . 80		D.3. Since draft-ietf-httpbis-p1-messaging-01 . . . . . . . . . 80
	D.4. Since draft-ietf-httpbis-p1-messaging-02 . . . . . . . . . 81		D.4. Since draft-ietf-httpbis-p1-messaging-02 . . . . . . . . . 81
	D.5. Since draft-ietf-httpbis-p1-messaging-03 . . . . . . . . . 81		D.5. Since draft-ietf-httpbis-p1-messaging-03 . . . . . . . . . 81
	D.6. Since draft-ietf-httpbis-p1-messaging-04 . . . . . . . . . 82		D.6. Since draft-ietf-httpbis-p1-messaging-04 . . . . . . . . . 82
	D.7. Since draft-ietf-httpbis-p1-messaging-05 . . . . . . . . . 82		D.7. Since draft-ietf-httpbis-p1-messaging-05 . . . . . . . . . 82
	D.8. Since draft-ietf-httpbis-p1-messaging-06 . . . . . . . . . 83		D.8. Since draft-ietf-httpbis-p1-messaging-06 . . . . . . . . . 83
	D.9. Since draft-ietf-httpbis-p1-messaging-07 . . . . . . . . . 84		D.9. Since draft-ietf-httpbis-p1-messaging-07 . . . . . . . . . 84
	D.10. Since draft-ietf-httpbis-p1-messaging-08 . . . . . . . . . 84		D.10. Since draft-ietf-httpbis-p1-messaging-08 . . . . . . . . . 84
	D.11. Since draft-ietf-httpbis-p1-messaging-09 . . . . . . . . . 85		D.11. Since draft-ietf-httpbis-p1-messaging-09 . . . . . . . . . 85
	D.12. Since draft-ietf-httpbis-p1-messaging-10 . . . . . . . . . 85		D.12. Since draft-ietf-httpbis-p1-messaging-10 . . . . . . . . . 85
			D.13. Since draft-ietf-httpbis-p1-messaging-11 . . . . . . . . . 86
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
	1. Introduction		1. Introduction
	The Hypertext Transfer Protocol (HTTP) is an application-level		The Hypertext Transfer Protocol (HTTP) is an application-level
	request/response protocol that uses extensible semantics and MIME-		request/response protocol that uses extensible semantics and MIME-
	like message payloads for flexible interaction with network-based		like message payloads for flexible interaction with network-based
	hypertext information systems. HTTP relies upon the Uniform Resource		hypertext information systems. HTTP relies upon the Uniform Resource
	Identifier (URI) standard [RFC3986] to indicate request targets and		Identifier (URI) standard [RFC3986] to indicate request targets and
	relationships between resources. Messages are passed in a format		relationships between resources. Messages are passed in a format
	skipping to change at page 30, line 26		skipping to change at page 30, line 26
	o the authority component, as specified in the Host header		o the authority component, as specified in the Host header
	(Section 9.4) and determined by the rules in Section 4.2,		(Section 9.4) and determined by the rules in Section 4.2,
	[[effrequri-nohost: Do we need to include the handling of missing		[[effrequri-nohost: Do we need to include the handling of missing
	hosts in HTTP/1.0 messages, as described in Section 4.2? -- See		hosts in HTTP/1.0 messages, as described in Section 4.2? -- See
	<http://tools.ietf.org/wg/httpbis/trac/ticket/221> --jre]] and		<http://tools.ietf.org/wg/httpbis/trac/ticket/221> --jre]] and
	o the request-target obtained from the Request-Line, unless the		o the request-target obtained from the Request-Line, unless the
	request-target is just the asterisk "*".		request-target is just the asterisk "*".
	Otherwise, when request-target uses the authority form, the effective		Otherwise, when request-target uses the authority form, the effective
	Request URI is undefined.		request URI is undefined.
	Example 1: the effective request URI for the message		Example 1: the effective request URI for the message
	GET /pub/WWW/TheProject.html HTTP/1.1		GET /pub/WWW/TheProject.html HTTP/1.1
	Host: www.example.org:8080		Host: www.example.org:8080
	(received over an insecure TCP connection) is "http", plus "://",		(received over an insecure TCP connection) is "http", plus "://",
	plus the authority component "www.example.org:8080", plus the		plus the authority component "www.example.org:8080", plus the
	request-target "/pub/WWW/TheProject.html", thus		request-target "/pub/WWW/TheProject.html", thus
	"http://www.example.org:8080/pub/WWW/TheProject.html".		"http://www.example.org:8080/pub/WWW/TheProject.html".
	skipping to change at page 66, line 36		skipping to change at page 66, line 36
	13.1. Normative References		13.1. Normative References
	[ISO-8859-1] International Organization for Standardization,		[ISO-8859-1] International Organization for Standardization,
	"Information technology -- 8-bit single-byte coded		"Information technology -- 8-bit single-byte coded
	graphic character sets -- Part 1: Latin alphabet No.		graphic character sets -- Part 1: Latin alphabet No.
	1", ISO/IEC 8859-1:1998, 1998.		1", ISO/IEC 8859-1:1998, 1998.
	[Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,		[Part2] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
	Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message		Ed., and J. Reschke, Ed., "HTTP/1.1, part 2: Message
	Semantics", draft-ietf-httpbis-p2-semantics-11 (work in		Semantics", draft-ietf-httpbis-p2-semantics-latest
	progress), August 2010.		(work in progress), September 2010.
	[Part3] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,		[Part3] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
	Ed., and J. Reschke, Ed., "HTTP/1.1, part 3: Message		Ed., and J. Reschke, Ed., "HTTP/1.1, part 3: Message
	Payload and Content Negotiation",		Payload and Content Negotiation",
	draft-ietf-httpbis-p3-payload-11 (work in progress),		draft-ietf-httpbis-p3-payload-latest (work in
	August 2010.		progress), September 2010.
	[Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,		[Part6] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y.,
	Ed., Nottingham, M., Ed., and J. Reschke, Ed.,		Ed., Nottingham, M., Ed., and J. Reschke, Ed.,
	"HTTP/1.1, part 6: Caching",		"HTTP/1.1, part 6: Caching",
	draft-ietf-httpbis-p6-cache-11 (work in progress),		draft-ietf-httpbis-p6-cache-latest (work in progress),
	August 2010.		September 2010.
	[RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data		[RFC1950] Deutsch, L. and J-L. Gailly, "ZLIB Compressed Data
	Format Specification version 3.3", RFC 1950, May 1996.		Format Specification version 3.3", RFC 1950, May 1996.
	RFC 1950 is an Informational RFC, thus it might be less		RFC 1950 is an Informational RFC, thus it might be less
	stable than this specification. On the other hand,		stable than this specification. On the other hand,
	this downward reference was present since the		this downward reference was present since the
	publication of RFC 2068 in 1997 ([RFC2068]), therefore		publication of RFC 2068 in 1997 ([RFC2068]), therefore
	it is unlikely to cause problems in practice. See also		it is unlikely to cause problems in practice. See also
	[BCP97].		[BCP97].
	skipping to change at page 86, line 10		skipping to change at page 86, line 10
	entity / representation / variant terminology"		entity / representation / variant terminology"
	o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider		o <http://tools.ietf.org/wg/httpbis/trac/ticket/220>: "consider
	removing the 'changes from 2068' sections"		removing the 'changes from 2068' sections"
	Partly resolved issues:		Partly resolved issues:
	o <http://tools.ietf.org/wg/httpbis/trac/ticket/159>: "HTTP(s) URI		o <http://tools.ietf.org/wg/httpbis/trac/ticket/159>: "HTTP(s) URI
	scheme definitions"		scheme definitions"
			D.13. Since draft-ietf-httpbis-p1-messaging-11
			None yet.
	Index		Index
	A		A
	application/http Media Type 61		application/http Media Type 61
	B		B
	browser 10		browser 10
	C		C
	cache 13		cache 13
End of changes. 11 change blocks.
	12 lines changed or deleted		17 lines changed or added
This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/