IETF Logo Mail Archive

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

Patrick McManus <pmcmanus@mozilla.com> Thu, 02 November 2017 11:27 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 3A4C013F6F9 for <hybi@ietfa.amsl.com>; Thu, 2 Nov 2017 04:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.666
X-Spam-Level:
X-Spam-Status: No, score=0.666 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 eZgwLYiMyDNl for <hybi@ietfa.amsl.com>; Thu, 2 Nov 2017 04:27:08 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id 53C0313F6C9 for <hybi@ietf.org>; Thu, 2 Nov 2017 04:27:08 -0700 (PDT)
Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) by linode64.ducksong.com (Postfix) with ESMTPSA id 7FC403AB8A for <hybi@ietf.org>; Thu, 2 Nov 2017 07:27:06 -0400 (EDT)
Received: by mail-lf0-f46.google.com with SMTP id 90so6031465lfs.13 for <hybi@ietf.org>; Thu, 02 Nov 2017 04:27:06 -0700 (PDT)
X-Gm-Message-State: AMCzsaU0pwHKMFltZhBelIASBGOh2q8hWNWgtLMWD1YFnKGfq5JI0dzH A1uqlDRknWQNZqpArci3ASlzunvQ+2DODFybkyA=
X-Google-Smtp-Source: ABhQp+SQoZVFbkpCesALQzCp9tTid38Amuy/6ygUh8/noOERn15YoBcTpsp9qKBNoNTVxmAIirefqplNehh7U2sJJsk=
X-Received: by 10.25.21.233 with SMTP id 102mr1105757lfv.252.1509622025258; Thu, 02 Nov 2017 04:27:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.21.22 with HTTP; Thu, 2 Nov 2017 04:27:04 -0700 (PDT)
In-Reply-To: <CAOdDvNp1dKV8-t_r8KFMkJdRgUh_5VtNJ3unORgEpg5EeOAGZg@mail.gmail.com>
References: <150903901882.24232.14013636670744151147.idtracker@ietfa.amsl.com> <CAOdDvNrC1PgribOiDc93hfCDFSJbjodnU8=yeNWgzkq4Cm-2Cg@mail.gmail.com> <CACAJL3nEB5jGFXpqPZ2ErdkezCHpZE1CnqXy0yomBP-v7jcGRA@mail.gmail.com> <bf6aabaf-227b-fc3d-8142-57712a2e8935@warmcat.com> <CAOdDvNp1dKV8-t_r8KFMkJdRgUh_5VtNJ3unORgEpg5EeOAGZg@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 02 Nov 2017 12:27:04 +0100
X-Gmail-Original-Message-ID: <CAOdDvNpWBw2Q36=XqkHwa4tc4wCrV6mumeah9w-ATkGJmUaZ9Q@mail.gmail.com>
Message-ID: <CAOdDvNpWBw2Q36=XqkHwa4tc4wCrV6mumeah9w-ATkGJmUaZ9Q@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: Andy Green <andy@warmcat.com>, John Fallows <john.fallows@kaazing.com>, hybi <hybi@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a114081268f8db8055cfe4426"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/52qtl-lt8XNbMZqYSBmzW_gBtqs>
Subject: Re: [hybi] Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.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: Thu, 02 Nov 2017 11:27:10 -0000

Here are my plans for -02

* websockets parameters (sub-protocol, etc..) into h2 HEADERS

* define the websockets target URI scheme for CONNECT as being http/https
when using 6455. I actually think this is a change from 6455 but I can live
with it if its defined. Mostly the concern is around legacy pac.

* stick with CONNECT as the method for the moment.. my thinking here is
that CONNECT is already a strange beast with special code doing almost what
we want here anyhow.. replicating that is not great. I would rather have a
pseudo header be the version specific thing (which is expected of pseudo
headers) than adding a new method which is typically not.

v2.23.0 | Report a Bug | By Email