draft-ietf-httpbis-p1-messaging-09.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) One Laptop per Child		Updates: 2817 (if approved) One Laptop per Child
	Intended status: Standards Track J. Mogul		Intended status: Standards Track J. Mogul
	Expires: September 9, 2010 HP		Expires: September 12, 2010 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
	March 8, 2010		March 11, 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-09		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/11> and related		at <http://tools.ietf.org/wg/httpbis/trac/report/11> 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.10.		The changes in this draft are summarized in Appendix D.11.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted to IETF in full conformance with the		This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	skipping to change at page 2, line 23		skipping to change at page 2, line 23
	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."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	This Internet-Draft will expire on September 9, 2010.		This Internet-Draft will expire on September 12, 2010.
	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 3, line 28		skipping to change at page 3, line 28
	2.4. Transport Independence . . . . . . . . . . . . . . . . . . 14		2.4. Transport Independence . . . . . . . . . . . . . . . . . . 14
	2.5. HTTP Version . . . . . . . . . . . . . . . . . . . . . . . 14		2.5. HTTP Version . . . . . . . . . . . . . . . . . . . . . . . 14
	2.6. Uniform Resource Identifiers . . . . . . . . . . . . . . . 16		2.6. Uniform Resource Identifiers . . . . . . . . . . . . . . . 16
	2.6.1. http URI scheme . . . . . . . . . . . . . . . . . . . 16		2.6.1. http URI scheme . . . . . . . . . . . . . . . . . . . 16
	2.6.2. https URI scheme . . . . . . . . . . . . . . . . . . . 17		2.6.2. https URI scheme . . . . . . . . . . . . . . . . . . . 17
	2.6.3. http and https URI Normalization and Comparison . . . 18		2.6.3. http and https URI Normalization and Comparison . . . 18
	3. HTTP Message . . . . . . . . . . . . . . . . . . . . . . . . . 19		3. HTTP Message . . . . . . . . . . . . . . . . . . . . . . . . . 19
	3.1. Message Parsing Robustness . . . . . . . . . . . . . . . . 19		3.1. Message Parsing Robustness . . . . . . . . . . . . . . . . 19
	3.2. Header Fields . . . . . . . . . . . . . . . . . . . . . . 20		3.2. Header Fields . . . . . . . . . . . . . . . . . . . . . . 20
	3.3. Message Body . . . . . . . . . . . . . . . . . . . . . . . 22		3.3. Message Body . . . . . . . . . . . . . . . . . . . . . . . 22
	3.4. Message Length . . . . . . . . . . . . . . . . . . . . . . 23		3.4. Message Length . . . . . . . . . . . . . . . . . . . . . . 22
	3.5. General Header Fields . . . . . . . . . . . . . . . . . . 24		3.5. General Header Fields . . . . . . . . . . . . . . . . . . 24
	4. Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 25		4. Request . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
	4.1. Request-Line . . . . . . . . . . . . . . . . . . . . . . . 25		4.1. Request-Line . . . . . . . . . . . . . . . . . . . . . . . 25
	4.1.1. Method . . . . . . . . . . . . . . . . . . . . . . . . 25		4.1.1. Method . . . . . . . . . . . . . . . . . . . . . . . . 25
	4.1.2. request-target . . . . . . . . . . . . . . . . . . . . 25		4.1.2. request-target . . . . . . . . . . . . . . . . . . . . 25
	4.2. The Resource Identified by a Request . . . . . . . . . . . 27		4.2. The Resource Identified by a Request . . . . . . . . . . . 27
	5. Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 28		5. Response . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
	5.1. Status-Line . . . . . . . . . . . . . . . . . . . . . . . 28		5.1. Status-Line . . . . . . . . . . . . . . . . . . . . . . . 28
	5.1.1. Status Code and Reason Phrase . . . . . . . . . . . . 28		5.1.1. Status Code and Reason Phrase . . . . . . . . . . . . 28
	6. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 29		6. Protocol Parameters . . . . . . . . . . . . . . . . . . . . . 29
	6.1. Date/Time Formats: Full Date . . . . . . . . . . . . . . . 29		6.1. Date/Time Formats: Full Date . . . . . . . . . . . . . . . 29
	6.2. Transfer Codings . . . . . . . . . . . . . . . . . . . . . 31		6.2. Transfer Codings . . . . . . . . . . . . . . . . . . . . . 31
	skipping to change at page 5, line 19		skipping to change at page 5, line 19
	D.1. Since RFC2616 . . . . . . . . . . . . . . . . . . . . . . 76		D.1. Since RFC2616 . . . . . . . . . . . . . . . . . . . . . . 76
	D.2. Since draft-ietf-httpbis-p1-messaging-00 . . . . . . . . . 76		D.2. Since draft-ietf-httpbis-p1-messaging-00 . . . . . . . . . 76
	D.3. Since draft-ietf-httpbis-p1-messaging-01 . . . . . . . . . 77		D.3. Since draft-ietf-httpbis-p1-messaging-01 . . . . . . . . . 77
	D.4. Since draft-ietf-httpbis-p1-messaging-02 . . . . . . . . . 78		D.4. Since draft-ietf-httpbis-p1-messaging-02 . . . . . . . . . 78
	D.5. Since draft-ietf-httpbis-p1-messaging-03 . . . . . . . . . 79		D.5. Since draft-ietf-httpbis-p1-messaging-03 . . . . . . . . . 79
	D.6. Since draft-ietf-httpbis-p1-messaging-04 . . . . . . . . . 79		D.6. Since draft-ietf-httpbis-p1-messaging-04 . . . . . . . . . 79
	D.7. Since draft-ietf-httpbis-p1-messaging-05 . . . . . . . . . 80		D.7. Since draft-ietf-httpbis-p1-messaging-05 . . . . . . . . . 80
	D.8. Since draft-ietf-httpbis-p1-messaging-06 . . . . . . . . . 81		D.8. Since draft-ietf-httpbis-p1-messaging-06 . . . . . . . . . 81
	D.9. Since draft-ietf-httpbis-p1-messaging-07 . . . . . . . . . 81		D.9. Since draft-ietf-httpbis-p1-messaging-07 . . . . . . . . . 81
	D.10. Since draft-ietf-httpbis-p1-messaging-08 . . . . . . . . . 82		D.10. Since draft-ietf-httpbis-p1-messaging-08 . . . . . . . . . 82
			D.11. Since draft-ietf-httpbis-p1-messaging-09 . . . . . . . . . 82
	Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82		Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 86		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 87
	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
	similar to that used by Internet mail [RFC5322] and the Multipurpose		similar to that used by Internet mail [RFC5322] and the Multipurpose
	skipping to change at page 16, line 21		skipping to change at page 16, line 21
	interface that can be used to interact with a resource via HTTP.		interface that can be used to interact with a resource via HTTP.
	More information on the scope of URIs and resources can be found in		More information on the scope of URIs and resources can be found in
	[RFC3986].		[RFC3986].
	This specification adopts the definitions of "URI-reference",		This specification adopts the definitions of "URI-reference",
	"absolute-URI", "relative-part", "port", "host", "path-abempty",		"absolute-URI", "relative-part", "port", "host", "path-abempty",
	"path-absolute", "query", and "authority" from [RFC3986]. In		"path-absolute", "query", and "authority" from [RFC3986]. In
	addition, we define a partial-URI rule for protocol elements that		addition, we define a partial-URI rule for protocol elements that
	allow a relative URI without a fragment.		allow a relative URI without a fragment.
	URI = <URI, defined in [RFC3986], Section 3>
	URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>		URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>
	absolute-URI = <absolute-URI, defined in [RFC3986], Section 4.3>		absolute-URI = <absolute-URI, defined in [RFC3986], Section 4.3>
	relative-part = <relative-part, defined in [RFC3986], Section 4.2>		relative-part = <relative-part, defined in [RFC3986], Section 4.2>
	authority = <authority, defined in [RFC3986], Section 3.2>		authority = <authority, defined in [RFC3986], Section 3.2>
	path-abempty = <path-abempty, defined in [RFC3986], Section 3.3>		path-abempty = <path-abempty, defined in [RFC3986], Section 3.3>
	path-absolute = <path-absolute, defined in [RFC3986], Section 3.3>		path-absolute = <path-absolute, defined in [RFC3986], Section 3.3>
	port = <port, defined in [RFC3986], Section 3.2.3>		port = <port, defined in [RFC3986], Section 3.2.3>
	query = <query, defined in [RFC3986], Section 3.4>		query = <query, defined in [RFC3986], Section 3.4>
	uri-host = <host, defined in [RFC3986], Section 3.2.2>		uri-host = <host, defined in [RFC3986], Section 3.2.2>
	skipping to change at page 63, line 37		skipping to change at page 63, line 37
	[ISO-8859-1]		[ISO-8859-1]
	International Organization for Standardization,		International Organization for Standardization,
	"Information technology -- 8-bit single-byte coded graphic		"Information technology -- 8-bit single-byte coded graphic
	character sets -- Part 1: Latin alphabet No. 1", ISO/		character sets -- Part 1: Latin alphabet No. 1", ISO/
	IEC 8859-1:1998, 1998.		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., Ed.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
	and J. Reschke, Ed., "HTTP/1.1, part 2: Message		and J. Reschke, Ed., "HTTP/1.1, part 2: Message
	Semantics", draft-ietf-httpbis-p2-semantics-09 (work in		Semantics", draft-ietf-httpbis-p2-semantics-latest (work
	progress), March 2010.		in progress), March 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., Ed.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
	and J. Reschke, Ed., "HTTP/1.1, part 3: Message Payload		and J. Reschke, Ed., "HTTP/1.1, part 3: Message Payload
	and Content Negotiation", draft-ietf-httpbis-p3-payload-09		and Content Negotiation",
	(work in progress), March 2010.		draft-ietf-httpbis-p3-payload-latest (work in progress),
			March 2010.
	[Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,		[Part5] Fielding, R., Ed., Gettys, J., Mogul, J., Frystyk, H.,
	Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
	and J. Reschke, Ed., "HTTP/1.1, part 5: Range Requests and		and J. Reschke, Ed., "HTTP/1.1, part 5: Range Requests and
	Partial Responses", draft-ietf-httpbis-p5-range-09 (work		Partial Responses", draft-ietf-httpbis-p5-range-latest
	in progress), March 2010.		(work in progress), March 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., Ed.,		Masinter, L., Leach, P., Berners-Lee, T., Lafon, Y., Ed.,
	Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part		Nottingham, M., Ed., and J. Reschke, Ed., "HTTP/1.1, part
	6: Caching", draft-ietf-httpbis-p6-cache-09 (work in		6: Caching", draft-ietf-httpbis-p6-cache-latest (work in
	progress), March 2010.		progress), March 2010.
	[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, May 1996.		Specification version 3.3", RFC 1950, May 1996.
	RFC 1950 is an Informational RFC, thus it may be less		RFC 1950 is an Informational RFC, thus it may be less
	stable than this specification. On the other hand, this		stable than this specification. On the other hand, this
	downward reference was present since the publication of		downward reference was present since the publication of
	RFC 2068 in 1997 ([RFC2068]), therefore it is unlikely to		RFC 2068 in 1997 ([RFC2068]), therefore it is unlikely to
	cause problems in practice. See also [BCP97].		cause problems in practice. See also [BCP97].
	skipping to change at page 72, line 35		skipping to change at page 72, line 35
	Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF		Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
	TE = "TE:" OWS TE-v		TE = "TE:" OWS TE-v
	TE-v = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]		TE-v = [ ( "," / t-codings ) *( OWS "," [ OWS t-codings ] ) ]
	Trailer = "Trailer:" OWS Trailer-v		Trailer = "Trailer:" OWS Trailer-v
	Trailer-v = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )		Trailer-v = *( "," OWS ) field-name *( OWS "," [ OWS field-name ] )
	Transfer-Encoding = "Transfer-Encoding:" OWS Transfer-Encoding-v		Transfer-Encoding = "Transfer-Encoding:" OWS Transfer-Encoding-v
	Transfer-Encoding-v = *( "," OWS ) transfer-coding *( OWS "," [ OWS		Transfer-Encoding-v = *( "," OWS ) transfer-coding *( OWS "," [ OWS
	transfer-coding ] )		transfer-coding ] )
	URI = <URI, defined in [RFC3986], Section 3>
	URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>		URI-reference = <URI-reference, defined in [RFC3986], Section 4.1>
	Upgrade = "Upgrade:" OWS Upgrade-v		Upgrade = "Upgrade:" OWS Upgrade-v
	Upgrade-v = *( "," OWS ) product *( OWS "," [ OWS product ] )		Upgrade-v = *( "," OWS ) product *( OWS "," [ OWS product ] )
	Via = "Via:" OWS Via-v		Via = "Via:" OWS Via-v
	Via-v = *( "," OWS ) received-protocol RWS received-by [ RWS comment		Via-v = *( "," OWS ) received-protocol RWS received-by [ RWS comment
	] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]		] *( OWS "," [ OWS received-protocol RWS received-by [ RWS comment ]
	] )		] )
	Warning = <Warning, defined in [Part6], Section 3.6>		Warning = <Warning, defined in [Part6], Section 3.6>
	skipping to change at page 75, line 43		skipping to change at page 75, line 43
	ABNF diagnostics:		ABNF diagnostics:
	; Chunked-Body defined but not used		; Chunked-Body defined but not used
	; Content-Length defined but not used		; Content-Length defined but not used
	; HTTP-message defined but not used		; HTTP-message defined but not used
	; Host defined but not used		; Host defined but not used
	; Request defined but not used		; Request defined but not used
	; Response defined but not used		; Response defined but not used
	; TE defined but not used		; TE defined but not used
	; URI defined but not used
	; URI-reference defined but not used		; URI-reference defined but not used
	; http-URI defined but not used		; http-URI defined but not used
	; https-URI defined but not used		; https-URI defined but not used
	; partial-URI defined but not used		; partial-URI defined but not used
	; special defined but not used		; special defined but not used
	Appendix D. Change Log (to be removed by RFC Editor before publication)		Appendix D. Change Log (to be removed by RFC Editor before publication)
	D.1. Since RFC2616		D.1. Since RFC2616
	skipping to change at page 82, line 32		skipping to change at page 82, line 32
	parsing, treatment of leading and trailing OWS"		parsing, treatment of leading and trailing OWS"
	Partly resolved issues:		Partly resolved issues:
	o <http://tools.ietf.org/wg/httpbis/trac/ticket/60>: "Placement of		o <http://tools.ietf.org/wg/httpbis/trac/ticket/60>: "Placement of
	13.5.1 and 13.5.2"		13.5.1 and 13.5.2"
	o <http://tools.ietf.org/wg/httpbis/trac/ticket/200>: "use of term		o <http://tools.ietf.org/wg/httpbis/trac/ticket/200>: "use of term
	"word" when talking about header structure"		"word" when talking about header structure"
			D.11. Since draft-ietf-httpbis-p1-messaging-09
			None yet.
	Index		Index
	A		A
	application/http Media Type 58		application/http Media Type 58
	C		C
	cache 13		cache 13
	cacheable 14		cacheable 14
	chunked (Coding Format) 32		chunked (Coding Format) 32
	client 10		client 10
	skipping to change at page 83, line 16		skipping to change at page 83, line 19
	Date header 48		Date header 48
	deflate (Coding Format) 35		deflate (Coding Format) 35
	downstream 12		downstream 12
	G		G
	gateway 13		gateway 13
	Grammar		Grammar
	absolute-URI 16		absolute-URI 16
	ALPHA 7		ALPHA 7
	asctime-date 31		asctime-date 31
	attribute 32		attribute 31
	authority 16		authority 16
	BWS 9		BWS 9
	chunk 33		chunk 33
	chunk-data 33		chunk-data 33
	chunk-ext 33		chunk-ext 33
	chunk-ext-name 33		chunk-ext-name 33
	chunk-ext-val 33		chunk-ext-val 33
	chunk-size 33		chunk-size 33
	Chunked-Body 33		Chunked-Body 33
	comment 21		comment 21
	skipping to change at page 83, line 39		skipping to change at page 83, line 42
	Connection-v 46		Connection-v 46
	Content-Length 47		Content-Length 47
	Content-Length-v 47		Content-Length-v 47
	CR 7		CR 7
	CRLF 7		CRLF 7
	ctext 21		ctext 21
	CTL 7		CTL 7
	Date 48		Date 48
	Date-v 48		Date-v 48
	date1 30		date1 30
	date2 32		date2 31
	date3 32		date3 31
	day 30		day 30
	day-name 30		day-name 30
	day-name-l 30		day-name-l 30
	DIGIT 7		DIGIT 7
	DQUOTE 7		DQUOTE 7
	extension-code 29		extension-code 29
	extension-method 25		extension-method 25
	field-content 20		field-content 20
	field-name 20		field-name 20
	field-value 20		field-value 20
	general-header 24		general-header 24
	GMT 30		GMT 30
	header-field 20		header-field 20
	HEXDIG 7		HEXDIG 7
	Host 49		Host 49
	Host-v 49		Host-v 49
	hour 30		hour 30
	HTTP-date 30		HTTP-date 29
	HTTP-message 19		HTTP-message 19
	HTTP-Prot-Name 15		HTTP-Prot-Name 15
	http-URI 16		http-URI 16
	HTTP-Version 15		HTTP-Version 15
	https-URI 18		https-URI 18
	last-chunk 33		last-chunk 33
	LF 7		LF 7
	message-body 22		message-body 22
	Method 25		Method 25
	minute 30		minute 30
	month 30		month 30
	obs-date 31		obs-date 30
	obs-text 10		obs-text 10
	OCTET 7		OCTET 7
	OWS 9		OWS 9
	path-absolute 16		path-absolute 16
	port 16		port 16
	product 35		product 35
	product-version 35		product-version 35
	protocol-name 54		protocol-name 54
	protocol-version 54		protocol-version 54
	pseudonym 54		pseudonym 54
	qdtext 10		qdtext 10
	qdtext-nf 33		qdtext-nf 33
	query 16		query 16
	quoted-cpair 22		quoted-cpair 21
	quoted-pair 10		quoted-pair 10
	quoted-str-nf 33		quoted-str-nf 33
	quoted-string 10		quoted-string 10
	qvalue 36		qvalue 36
	Reason-Phrase 29		Reason-Phrase 29
	received-by 54		received-by 54
	received-protocol 54		received-protocol 54
	Request 25		Request 25
	Request-Line 25		Request-Line 25
	request-target 25		request-target 25
	skipping to change at page 85, line 22		skipping to change at page 85, line 26
	TE-v 50		TE-v 50
	time-of-day 30		time-of-day 30
	token 9		token 9
	Trailer 51		Trailer 51
	trailer-part 33		trailer-part 33
	Trailer-v 51		Trailer-v 51
	transfer-coding 31		transfer-coding 31
	Transfer-Encoding 52		Transfer-Encoding 52
	Transfer-Encoding-v 52		Transfer-Encoding-v 52
	transfer-extension 31		transfer-extension 31
	transfer-parameter 32		transfer-parameter 31
	Upgrade 52		Upgrade 52
	Upgrade-v 52		Upgrade-v 52
	uri-host 16		uri-host 16
	URI-reference 16		URI-reference 16
	value 32		value 31
	VCHAR 7		VCHAR 7
	Via 54		Via 54
	Via-v 54		Via-v 54
	WSP 7		WSP 7
	year 30		year 30
	gzip (Coding Format) 35		gzip (Coding Format) 35
	H		H
	header field 19		header field 19
	header section 19		header section 19
End of changes. 24 change blocks.
	26 lines changed or deleted		29 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/