[hybi] SETTINGS ENABLE_WEBSOCKET ?? | Re: proxy & ENABLE_UPGRADE SETTINGS | Re: Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.txt

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Sat, 11 November 2017 19:30 UTC

Return-Path: <hurtta@siilo.fmi.fi>
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 52566124239 for <hybi@ietfa.amsl.com>; Sat, 11 Nov 2017 11:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham 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 qwtwHxSJ8UMF for <hybi@ietfa.amsl.com>; Sat, 11 Nov 2017 11:30:39 -0800 (PST)
Received: from smtpVgate.fmi.fi (smtpvgate.fmi.fi [193.166.223.36]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80034126BF0 for <hybi@ietf.org>; Sat, 11 Nov 2017 11:30:37 -0800 (PST)
Received: from basaari.fmi.fi (basaari.fmi.fi [193.166.211.14]) (envelope-from hurtta@siilo.fmi.fi) by smtpVgate.fmi.fi (8.13.8/8.13.8/smtpgate-20161014/smtpVgate) with ESMTP id vABJUMep026545 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 11 Nov 2017 21:30:22 +0200
Received: from shell.siilo.fmi.fi by basaari.fmi.fi with ESMTP id vABJUMKI014040 ; Sat, 11 Nov 2017 21:30:22 +0200
Received: from shell.siilo.fmi.fi ([127.0.0.1]) by shell.siilo.fmi.fi with ESMTP id vABJUMAT010068 ; Sat, 11 Nov 2017 21:30:22 +0200
Received: by shell.siilo.fmi.fi id vABJUJKu010067; Sat, 11 Nov 2017 21:30:19 +0200
Message-Id: <201711111930.vABJUJKu010067@shell.siilo.fmi.fi>
In-Reply-To: <d5edca63-b782-9c57-f169-478b590ccf35@treenet.co.nz>
References: <e7420a25-7f57-8849-9820-ccc33053bd97@treenet.co.nz> <20171111091949.5F294B51FC@welho-filter2.welho.com> <d5edca63-b782-9c57-f169-478b590ccf35@treenet.co.nz>
To: Amos Jeffries <squid3@treenet.co.nz>
Date: Sat, 11 Nov 2017 21:30:19 +0200 (EET)
Sender: hurtta@siilo.fmi.fi
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP Working Group <ietf-http-wg@w3.org>, HYBI Working Group <hybi@ietf.org>, Patrick McManus <pmcmanus@mozilla.com>
X-Mailer: ELM [version ME+ 2.5 PLalpha46]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
X-Filter: smtpVgate.fmi.fi: 3 received headers rewritten with id 20171111/39802/01
X-Filter: smtpVgate.fmi.fi: ID 39804/01, 1 parts scanned for known viruses
X-Filter: basaari.fmi.fi: ID 165271/01, 1 parts scanned for known viruses
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (smtpVgate.fmi.fi [193.166.223.36]); Sat, 11 Nov 2017 21:30:26 +0200 (EET)
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/DuFu8E0O1_AK9lFN8lQu2M86ano>
Subject: [hybi] SETTINGS ENABLE_WEBSOCKET ?? | Re: proxy & ENABLE_UPGRADE SETTINGS | Re: 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: Sat, 11 Nov 2017 19:30:42 -0000

Amos Jeffries <squid3@treenet.co.nz>;: (Sat Nov 11 16:17:01 2017)
> If ":upgrade" has the same optional nature as Upgrade did there is zero 
> point in creating it. Just use the existing Upgrade header in the 
> HEADERS frame. That does not require any negotiation.
> 
> 
> The whole point of SETTINGS is to promise the recipient of that frame 
> that the things mentioned in it will work. No maybes or guessing.
> 
> This guarantee provided by SETTINGS is one of the ways HTTP/2 improves 
> over HTTP/1.1. No more sending maybe-ignored headers and hoping for 
> success a few RTT later. The client can know up front whether that 
> connection is a usable channel for the negotiable feature or not.
> 

Sidenote:

If you want SETTINGS to tell that websocket can be used
over HTTP/2 then 
	:upgrade =
and SETTINGS ENABLE_UPGRADE is no go. No general tunneling
as Kazuho Oku <kazuhooku@gmail.com>; as suggesting in that thread:

https://lists.w3.org/Archives/Public/ietf-http-wg/2017OctDec/0209.html

> If we adjust the three issues (for example, by allowing any method to
> be specified, and use the existence of :upgrade: pseudo header as a
> signal; use 101 to signal protocol change; use attributes of :upgrade:
> header to specify additional headers required for the upgrade), I
> think the approach would become generic.
> 
> For example, creating a websocket tunnel through HTTP/2 would look like below.

In that case SETTINGS ENABLE_UPGRADE tells nothing what upgrades are available
(or you need to do registry for different 32-bit values of
 ENABLE_UPGRADE to map possible upgrade protocols).

Same to say about SETTINGS  ENABLE_CONNECT_PROTOCOL and
    :protocol = 



You are asking SETTINGS ENABLE_WEBSOCKET then
and that is not proposed on draft-mcmanus-httpbis-h2-websockets-01
either.


/ Kari Hurtta