IETF Logo Mail Archive

Re: New Version Notification for draft-momoka-httpbis-settings-enable-websockets-00.txt

Glenn Strauss <gs-lists-ietf-http-wg@gluelogic.com> Tue, 28 February 2023 17:03 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C971DC152567 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 Feb 2023 09:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SxW2aIpDXyek for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 Feb 2023 09:03:28 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C568C151AFD for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 28 Feb 2023 09:03:27 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1pX3Nl-004CLF-17 for ietf-http-wg-dist@listhub.w3.org; Tue, 28 Feb 2023 17:03:17 +0000
Resent-Date: Tue, 28 Feb 2023 17:03:17 +0000
Resent-Message-Id: <E1pX3Nl-004CLF-17@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <gs-lists-ietf-http-wg@gluelogic.com>) id 1pX3Nj-004CFj-8g for ietf-http-wg@listhub.w3.org; Tue, 28 Feb 2023 17:03:15 +0000
Received: from smtp1.atof.net ([52.86.233.228]) by titan.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (Exim 4.94.2) (envelope-from <gs-lists-ietf-http-wg@gluelogic.com>) id 1pX3Ng-0045oA-Ee for ietf-http-wg@w3.org; Tue, 28 Feb 2023 17:03:15 +0000
X-Spam-Language: en
X-Spam-Relay-Country:
X-Spam-DCC: B=MGTINTERNET; R=smtp1.atof.net 1170; Body=1 Fuz1=1 Fuz2=1
X-Spam-RBL:
X-Spam-PYZOR: Reported 0 times.
Date: Tue, 28 Feb 2023 12:02:54 -0500
From: Glenn Strauss <gs-lists-ietf-http-wg@gluelogic.com>
To: Momoka Yamamoto <momoka.my6@gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, Ben Schwartz <bemasc@google.com>, ietf-http-wg@w3.org
Message-ID: <Y/4zvq81+pE0UBl7@xps13>
References: <CAHbrMsDSFRHQhciZM6PYNL=qoWAK8N-g+Pd39NngBKxag62wpA@mail.gmail.com> <CALGR9oYmYid=0pMW5tCLpE1GFdz1hgTL0Vy6HDjYBSNZC1WP3A@mail.gmail.com> <CAHbrMsDKrDf7v4DLHnHUnRCK2ABZ_ZMfGy4_2PAz+g=2RhDNHQ@mail.gmail.com> <CALGR9obABt+cL2Cafkt_x9fRvu9BTD+tZmPGF7-SaDeaNYvBhA@mail.gmail.com> <CAHbrMsB2a-9U_f+AFq5L9PmQzquc=wdEWcYoR8UyN4H=LiaBzQ@mail.gmail.com> <CAD9w2qaGEG96hDrGEadMSRE+Kxr-DzuThyMmShBzjzmBarC_Jg@mail.gmail.com> <CAHbrMsBT3DQJe8jvxmpt8TPW4jhttOLkQmco9+_FpZfGUJxCRw@mail.gmail.com> <CALGR9oZfiura=WnVVX47YZx-TFY_6xvK8PckS5cXY325a859AA@mail.gmail.com> <CAD9w2qajqHy+JbSPGKUjfPL0Bh94CaOyNn=iRouBS1PWRUBZkA@mail.gmail.com> <CAD9w2qYW=aV-m+FdY2X1J1933WgiDjDs02uMgq2w1i1NCK4PqA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
In-Reply-To: <CAD9w2qYW=aV-m+FdY2X1J1933WgiDjDs02uMgq2w1i1NCK4PqA@mail.gmail.com>
Received-SPF: pass client-ip=52.86.233.228; envelope-from=gs-lists-ietf-http-wg@gluelogic.com; helo=smtp1.atof.net
X-W3C-Hub-Spam-Status: No, score=-6.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1pX3Ng-0045oA-Ee 4ab7807846eecb8c06de6104308ee4d0
X-Original-To: ietf-http-wg@w3.org
Subject: Re: New Version Notification for draft-momoka-httpbis-settings-enable-websockets-00.txt
Archived-At: <https://www.w3.org/mid/Y/4zvq81+pE0UBl7@xps13>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/50787
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Tue, Feb 28, 2023 at 04:12:21PM +0800, Momoka Yamamoto wrote:
> Hello,
> I have submitted a new revision of this
> draft draft-momoka-httpbis-settings-enable-websockets.
> > URL:
> > https://www.ietf.org/archive/id/draft-momoka-httpbis-settings-enable-websockets-01.txt

Why should SETTINGS_ENABLE_WEBSOCKETS be added to HTTP/2, HTTP/3, HTTP/X
protocols instead of using existing service discovery mechanisms such as
alt-svc or the proposed alt-svcb?
https://martinthomson.github.io/alt-svcb/draft-thomson-httpbis-alt-svcb.html

There is already SETTINGS_ENABLE_CONNECT_PROTOCOL and the proposed
SETTINGS_ENABLE_WEBSOCKETS would be a specific subset of that.
While websockets is important to many apps, is this subset important
enough to add its own setting to multiple HTTP protocol versions and
to be advertised as part of every single HTTP/2 and HTTP/3 request?
Might there be settings created for other protocols that leverage
SETTINGS_ENABLE_CONNECT_PROTOCOL?  Why should a new SETTING be created
for websockets and not for ... ?

Cheers, Glenn

v2.40.4 | Report a Bug | By Email | System Status