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

Ilari Liusvaara <ilariliusvaara@welho.com> Tue, 28 February 2023 19:30 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 08D68C151B15 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 Feb 2023 11:30:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 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] 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 PJLDPYTlu0Ps for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 Feb 2023 11:30:18 -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 C95C1C151B0C for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 28 Feb 2023 11:30:18 -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 1pX5fs-004dMK-C1 for ietf-http-wg-dist@listhub.w3.org; Tue, 28 Feb 2023 19:30:08 +0000
Resent-Date: Tue, 28 Feb 2023 19:30:08 +0000
Resent-Message-Id: <E1pX5fs-004dMK-C1@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <ilariliusvaara@welho.com>) id 1pX5fp-004dLC-NU for ietf-http-wg@listhub.w3.org; Tue, 28 Feb 2023 19:30:06 +0000
Received: from welho-filter2b.welho.com ([83.102.41.28] helo=welho-filter2.welho.com) by mimas.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <ilariliusvaara@welho.com>) id 1pX5fm-00EgBO-AR for ietf-http-wg@w3.org; Tue, 28 Feb 2023 19:30:06 +0000
Received: from localhost (localhost [127.0.0.1]) by welho-filter2.welho.com (Postfix) with ESMTP id C25D522935 for <ietf-http-wg@w3.org>; Tue, 28 Feb 2023 21:29:49 +0200 (EET)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter2.welho.com [::ffff:83.102.41.24]) (amavisd-new, port 10024) with ESMTP id NbTQbtfGOSwg for <ietf-http-wg@w3.org>; Tue, 28 Feb 2023 21:29:49 +0200 (EET)
Received: from LK-Perkele-VII2 (87-92-18-205.bb.dnainternet.fi [87.92.18.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id 97F112315 for <ietf-http-wg@w3.org>; Tue, 28 Feb 2023 21:29:48 +0200 (EET)
Date: Tue, 28 Feb 2023 21:29:48 +0200
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: ietf-http-wg@w3.org
Message-ID: <Y/5WLJ1+T0TqUrSe@LK-Perkele-VII2.locald>
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="utf-8"
Content-Disposition: inline
In-Reply-To: <CAD9w2qYW=aV-m+FdY2X1J1933WgiDjDs02uMgq2w1i1NCK4PqA@mail.gmail.com>
Sender: ilariliusvaara@welho.com
Received-SPF: pass client-ip=83.102.41.28; envelope-from=ilariliusvaara@welho.com; helo=welho-filter2.welho.com
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1pX5fm-00EgBO-AR e809370f246adb5e6d619a376055ec77
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/5WLJ1+T0TqUrSe@LK-Perkele-VII2.locald>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/50791
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.
> 
> 
> The proposed parameter will be useful if an active HTTP/2 (or HTTP/3)
> connection to the server already exists when a document with a wss:/ URL is
> loaded. The browser can then choose whether to try opening the WebSocket
> stream over the connection, as the proposed SETTINGS_ENABLE_WEBSOCKETS has
> likely been received by that point.
> 
> However, the proposed parameter won't be useful when a browser tries to
> establish a new connection because the SETTINGS will not be received when a
> decision to use HTTP/2 or HTTP/1 is made.

Some comments:

- Does setting SETTINGS_ENABLE_WEBSOCKETS=1 imply support for necressary
  parts of extended connect, or does server also need to send
  SETTINGS_ENABLE_CONNECT_PROTOCOL=1?

- I don't think the default for SETTINGS_ENABLE_WEBSOCKETS should be 0,
  as I think absence of SETTINGS_ENABLE_WEBSOCKETS is different from
  SETTINGS_ENABLE_WEBSOCKETS=0. Later signals that websockets is not
  supported, the former together with SETTINGS_ENABLE_CONNECT_PROTOCOL=1
  signals that websockets may be supported (as there are currently
  servers that support websockets and behave that way).



-Ilari