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

Hey Patrick,

Catching up after travel...

The only thing that I don't like about this is covered in your FAQ:

> # Instead of overloading CONNECT, why not a new TUNNEL method?
>
> Methods are generally end to end and, more importantly, HTTP version independent. CONNECT is already a special snowflake in this regard. Note that the only method 7540 defines is CONNECT - because all the others are inherited from the semantic layer of 723x. Extending it is fairly natural as its defined specifically for HTTP/2 while a new method would not be well known as a version specific mechanism.

But 7540 didn't *define* CONNECT, it just adapted how it's used on the wire; the semantics are still "Hey proxy, give me a tunnel to THAT host."

Importantly, CONNECT here isn't being used to talk to a proxy, it's for an origin. And, given how much extra machinery is being defined, I don't see the downside of defining a new method with the specific semantics you're looking for, rather than muddying those of an existing method (which might have bad interactions with current configurations, tools, etc.).

Cheers,


> On 16 Oct 2017, at 1:12 am, Patrick McManus <mcmanus@ducksong.com> wrote:
> 
> FYI - also see https://github.com/mcmanus/draft-h2ws/blob/master/README.md <https://github.com/mcmanus/draft-h2ws/blob/master/README.md>
> 
> Comments, expressions of interest, etc are very welcome.
> 
> 
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Sun, Oct 15, 2017 at 10:08 AM
> Subject: New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
> To: Patrick McManus <mcmanus@ducksong.com <mailto:mcmanus@ducksong.com>>
> 
> 
> 
> 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
> URL:            https://www.ietf.org/internet-drafts/draft-mcmanus-httpbis-h2-websockets-00.txt <https://www.ietf.org/internet-drafts/draft-mcmanus-httpbis-h2-websockets-00.txt>
> Status:         https://datatracker.ietf.org/doc/draft-mcmanus-httpbis-h2-websockets/ <https://datatracker.ietf.org/doc/draft-mcmanus-httpbis-h2-websockets/>
> Htmlized:       https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-00 <https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-00>
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-mcmanus-httpbis-h2-websockets-00 <https://datatracker.ietf.org/doc/html/draft-mcmanus-httpbis-h2-websockets-00>
> 
> 
> Abstract:
>    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 tools.ietf.org <http://tools.ietf.org/>.
> 
> The IETF Secretariat
> 
> 

--
Mark Nottingham   https://www.mnot.net/