Re: [hybi] New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt

Lucas Pardue <> Mon, 16 October 2017 15:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BFCA6133049 for <>; Mon, 16 Oct 2017 08:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZQ_Tz2C9Op62 for <>; Mon, 16 Oct 2017 08:33:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4BB32133055 for <>; Mon, 16 Oct 2017 08:33:04 -0700 (PDT)
Received: from ( []) by (8.15.2/8.15.2) with ESMTP id v9GFX01A003788; Mon, 16 Oct 2017 16:33:00 +0100 (BST)
Received: from ([]) by ([]) with mapi id 14.03.0319.002; Mon, 16 Oct 2017 16:33:00 +0100
From: Lucas Pardue <>
To: Patrick McManus <>, HTTP Working Group <>, hybi <>
Thread-Topic: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
Thread-Index: AQHTRcA2rKps2szY4U+GtuV6F2532KLmlgGb
Date: Mon, 16 Oct 2017 15:33:00 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BA6F15A@bgb01xud1012>
References: <>, <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-GB
x-originating-ip: []
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-
x-tm-as-result: No--14.463700-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A3BA6F15Abgb01xud1012_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [hybi] New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 16 Oct 2017 15:33:08 -0000

Hi Patrick,

Interesting, thanks.

Some comments:

1) In section 3:

A sender MUST NOT send a ENABLE_CONNECT_PROTOCOL parameter with the
value of 0 after previously sending a value of 1.

What should the client do in such a situation? It seems overzealous to call this a protocol error, maybe we could

just say that since the initial/default is 0, a change to 1 is sticky and therefore the client MUST ignore any

ENABLE_CONNECT_PROTOCOL with a value of 0. A different way to look at this is that as the document stands,

sending ENABLE_CONNECT_PROTOCOL with a value of 0 is meaningless.

1) In section 7:

The use of a pseudo-header is something that is connection
specific and HTTP/2 does not ever allow to be created outside of
the protocol stack.

I think I understand the intent of this paragraph but I'm not sure its qualified by anything. Is there something that RFC 7540 says on the matter, or is this based on your observation of H2 implementation stacks?

2) In section 8 the error code 0x8 is reserved, however the HTTP/2 Settings registry indicates 0x7 is free. Is this skip over intended?


From: Patrick McManus []
Sent: 15 October 2017 15:12
To: HTTP Working Group; hybi
Subject: Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt

FYI - also see

Comments, expressions of interest, etc are very welcome.

---------- Forwarded message ----------
From: <<>>
Date: Sun, Oct 15, 2017 at 10:08 AM
Subject: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
To: Patrick McManus <<>>

A new version of I-D, draft-mcmanus-httpbis-h2-websockets-00.txt
has been successfully submitted by Patrick McManus and posted to the
IETF repository.

Name:           draft-mcmanus-httpbis-h2-websockets
Revision:       00
Title:          Bootstrapping WebSockets with HTTP/2
Document date:  2017-10-15
Group:          Individual Submission
Pages:          7

   This document defines a mechanism for running the WebSocket Protocol
   [RFC6455] over a single stream of an HTTP/2 connection.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at<>.

The IETF Secretariat