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

Patrick McManus <pmcmanus@mozilla.com> Sun, 15 October 2017 20:39 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6C9B1331DC for <hybi@ietfa.amsl.com>; Sun, 15 Oct 2017 13:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.734
X-Spam-Level:
X-Spam-Status: No, score=-0.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SORBS_SPAM=0.5, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pl_HP6WkJQP7 for <hybi@ietfa.amsl.com>; Sun, 15 Oct 2017 13:39:03 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 53820132F3E for <hybi@ietf.org>; Sun, 15 Oct 2017 13:39:03 -0700 (PDT)
Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by linode64.ducksong.com (Postfix) with ESMTPSA id B864D3A021 for <hybi@ietf.org>; Sun, 15 Oct 2017 16:39:01 -0400 (EDT)
Received: by mail-lf0-f49.google.com with SMTP id k40so14795547lfi.4 for <hybi@ietf.org>; Sun, 15 Oct 2017 13:39:01 -0700 (PDT)
X-Gm-Message-State: AMCzsaXx+zXWdtiSMlfTd0W1WRJUyv15RTZxI80UJWy4GaKhoxFLK1dh bA0QN0F/Ca085+cyvzFXXi5UBAuwVpPVdJdKBXg=
X-Google-Smtp-Source: ABhQp+TiDh5i55PxgfSS4VwzO6gWfYnLeyTBxKuRTuHXqnbCcubHzlPmEkQLgt5jHGZK+lWu+F31bHZAqbn6jYaY1IQ=
X-Received: by 10.46.32.81 with SMTP id g78mr3142658ljg.49.1508099940335; Sun, 15 Oct 2017 13:39:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.21.22 with HTTP; Sun, 15 Oct 2017 13:38:59 -0700 (PDT)
In-Reply-To: <0F93FB58-579D-4F52-8F22-5FEAFBC99165@warmcat.com>
References: <150807649389.12130.9191022211105955718.idtracker@ietfa.amsl.com> <CAOdDvNqhaTJmLcEk3CwBBaAbdOroc4U46z+nJzC7+chd1ErSDA@mail.gmail.com> <FEBB57D4-E841-4F45-9B62-81FFC653FF70@lukasa.co.uk> <0F93FB58-579D-4F52-8F22-5FEAFBC99165@warmcat.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Sun, 15 Oct 2017 16:38:59 -0400
X-Gmail-Original-Message-ID: <CAOdDvNpCVxsaKEzoW3EWsK1hmWSBPOP+GHnK-DcP4QO4om_khQ@mail.gmail.com>
Message-ID: <CAOdDvNpCVxsaKEzoW3EWsK1hmWSBPOP+GHnK-DcP4QO4om_khQ@mail.gmail.com>
To: Andy Green <andy@warmcat.com>
Cc: hybi <hybi@ietf.org>, Cory Benfield <cory@lukasa.co.uk>, Patrick McManus <mcmanus@ducksong.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a1142bd383ac647055b9be101"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/rO7rT0Wtcsxwi46N1Ho1tHeUZdQ>
Subject: Re: [hybi] New Version Notification for draft-mcmanus-httpbis-h2-websockets-00.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hybi/>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Oct 2017 20:39:06 -0000

Hey Andy - it sounds like my 2 mails on this thread mght not have been
posted to hybi? I'll try here with @mozilla.com addr. Thanks for the note.



On Sun, Oct 15, 2017 at 3:24 PM, Andy Green <andy@warmcat.com>; wrote:

>
> 2)
> This simply isn't true,


thanks. I'll rephrase


> 4) The draft should spell out it carries ws payload unchanged in h2
> frames.


   Streams that have been successfully established as protocol tunnels
   proceed to establish and utilize the WebSocket Protocol using the
   procedure defined by [RFC6455
<https://tools.ietf.org/html/rfc6455>] treating the stream as if were
the
   connection in that specification.


Obviously there are approaches that could do far more significant things to
the protocol. This is a shim for bootstrapping 6455, otherwise 6455 remains
in tact.

5) Hybi originally did the ws handshake key dance with hashes to ensure
> there were no inadvertant ws handshakes


see 4.


> 6) If you make the ws key dance roundtrip optional, something to keep h1
> clients happy who don't know they're on h2, then you can PUSH_PROMISE a ws
> upgrade on a specific subprotocol unilaterally, eliminating roundtrips.  If
> you are serving html with a


you can only push safe methods. connect is not safe. Again, I agree you
could remove an rtt (or probably 2) with a different approach at a cost of
higher complexity and changes. That's not the target here.

\

> >Doesn’t the introduction of a new pseudo-header field violate RFC 7540
> >Section 8.1.2.1, which says endpoints MUST NOT generate new
> >pseudo-header fields?
> >
> >Or is the position that that MUST NOT implicitly applies only if there
> >are no negotiated extensions in use?
>
> That is a good point... won't a new Sec-whatever do?  Being able to use
> whatever it is in PUSH_PROMISE to unilaterally offer an unambiguous
> pre-upgraded ws stream would be very nice.
>

I answered this is a message that probably wasn't posted to hybi
https://lists.w3.org/Archives/Public/ietf-http-wg/2017OctDec/0034.html..
tl;dr; an opt-in extension lets you amend 7540 in ways that would be
protocol violations without the opt-in.

pseudo-headers are meant to control protocol level features and are unique
to that version of the protocol - so this helps ensure that the Sec- header
wasn't introduced by some other non h2 application .

-Patrick


> -Andy
>
> >Cory
> >
> >> On 15 Oct 2017, at 07:12, Patrick McManus <mcmanus@ducksong.com>;
> >wrote:
> >>
> >> FYI - also see
> >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>;
> >> 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>;
> >>
> >>
> >>
> >> 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
> >> Status:
> >https://datatracker.ietf.org/doc/draft-mcmanus-httpbis-h2-websockets/
> >> Htmlized:
> >https://tools.ietf.org/html/draft-mcmanus-httpbis-h2-websockets-00
> >> Htmlized:
> >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.
> >>
> >> The IETF Secretariat
> >>
> >>
>
>