W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2023

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

From: Glenn Strauss <gs-lists-ietf-http-wg@gluelogic.com>
Date: Tue, 28 Feb 2023 12:02:54 -0500
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>
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
Received on Tuesday, 28 February 2023 17:03:15 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 28 February 2023 17:03:16 UTC