< draft-ietf-httpbis-h2-websockets-02.txt		draft-ietf-httpbis-h2-websockets-03.txt >
	HTTP P. McManus		HTTP P. McManus
	Internet-Draft Mozilla		Internet-Draft Mozilla
	Updates: 6455 (if approved) May 2, 2018		Updates: 6455 (if approved) May 2, 2018
	Intended status: Standards Track		Intended status: Standards Track
	Expires: November 3, 2018		Expires: November 3, 2018
	Bootstrapping WebSockets with HTTP/2		Bootstrapping WebSockets with HTTP/2
	draft-ietf-httpbis-h2-websockets-02		draft-ietf-httpbis-h2-websockets-03
	Abstract		Abstract
	This document defines a mechanism for running the WebSocket Protocol		This document defines a mechanism for running the WebSocket Protocol
	over a single stream of an HTTP/2 connection.		over a single stream of an HTTP/2 connection.
	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.
	skipping to change at page 5, line 11 ¶		skipping to change at page 5, line 11 ¶
	and response headers in the same way as defined in [RFC6455]. Note		and response headers in the same way as defined in [RFC6455]. Note
	that HTTP/1 header names were case-insensitive and HTTP/2 requires		that HTTP/1 header names were case-insensitive and HTTP/2 requires
	they be encoded as lower case.		they be encoded as lower case.
	After successfully processing the opening handshake, the peers should		After successfully processing the opening handshake, the peers should
	proceed with The WebSocket Protocol [RFC6455] using the HTTP/2 stream		proceed with The WebSocket Protocol [RFC6455] using the HTTP/2 stream
	from the CONNECT transaction as if it were the TCP connection		from the CONNECT transaction as if it were the TCP connection
	referred to in [RFC6455]. The state of the WebSocket connection at		referred to in [RFC6455]. The state of the WebSocket connection at
	this point is OPEN as defined by [RFC6455], Section 4.1.		this point is OPEN as defined by [RFC6455], Section 4.1.
	The HTTP/2 stream closure is also analagous to the TCP connection of		The HTTP/2 stream closure is also analogous to the TCP connection of
	[RFC6455]. Orderly TCP level closures are represented as END_STREAM		[RFC6455]. Orderly TCP level closures are represented as END_STREAM
	([RFC7540] Section 6.1) flags and RST exceptions are represented with		([RFC7540] Section 6.1) flags and RST exceptions are represented with
	the RST_STREAM ([RFC7540] Section 6.4) frame with the CANCEL		the RST_STREAM ([RFC7540] Section 6.4) frame with the CANCEL
	([RFC7540] Secion 7) error code.		([RFC7540] Secion 7) error code.
	5.1. Example		5.1. Example
	[[ From Client ]] [[ From Server ]]		[[ From Client ]] [[ From Server ]]
	SETTINGS		SETTINGS
End of changes. 2 change blocks.
	2 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/