Re: WebSocket2

Kari Hurtta <hurtta-ietf@elmme-mailer.org> Mon, 03 October 2016 04:44 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 0775A12B12F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 2 Oct 2016 21:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.917
X-Spam-Level:
X-Spam-Status: No, score=-9.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-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 j4Mf8kFtmcBn for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 2 Oct 2016 21:44:50 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A60E512B12A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 2 Oct 2016 21:44:50 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bqv3T-0004x4-5M for ietf-http-wg-dist@listhub.w3.org; Mon, 03 Oct 2016 04:40:43 +0000
Resent-Date: Mon, 03 Oct 2016 04:40:43 +0000
Resent-Message-Id: <E1bqv3T-0004x4-5M@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <hurtta@siilo.fmi.fi>) id 1bqv3R-0004wG-9k for ietf-http-wg@listhub.w3.org; Mon, 03 Oct 2016 04:40:41 +0000
Received: from smtpvgate.fmi.fi ([193.166.223.36]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <hurtta@siilo.fmi.fi>) id 1bqv3J-0008PF-VT for ietf-http-wg@w3.org; Mon, 03 Oct 2016 04:40:39 +0000
Received: from virkku.fmi.fi (virkku.fmi.fi [193.166.211.54]) (envelope-from hurtta@siilo.fmi.fi) by smtpVgate.fmi.fi (8.13.8/8.13.8/smtpgate-20160114/smtpVgate) with ESMTP id u934e4ov010795 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 3 Oct 2016 07:40:04 +0300
Received: from shell.siilo.fmi.fi by virkku.fmi.fi with ESMTP id u934e4Za019481 ; Mon, 3 Oct 2016 07:40:04 +0300
Received: from shell.siilo.fmi.fi ([127.0.0.1]) by shell.siilo.fmi.fi with ESMTP id u934e4XT031003 ; Mon, 3 Oct 2016 07:40:04 +0300
Received: by shell.siilo.fmi.fi id u934e3kL031002; Mon, 3 Oct 2016 07:40:03 +0300
Message-Id: <201610030440.u934e3kL031002@shell.siilo.fmi.fi>
In-Reply-To: <20161002171905.GA10108@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CAG-EYChPJpAzoEuNwY3cNz503d0FRbNnDx_9AsNsZyfb5nmN0g@mail.gmail.com> <20161002080030.5F328160CC@welho-filter4.welho.com> <20161002101548.GA9450@LK-Perkele-V2.elisa-laajakaista.fi> <201610021110.u92BAWpi019029@shell.siilo.fmi.fi> <20161002124346.GB9450@LK-Perkele-V2.elisa-laajakaista.fi> <201610021340.u92DeBBL029907@shell.siilo.fmi.fi> <20161002171905.GA10108@LK-Perkele-V2.elisa-laajakaista.fi>
To: Ilari Liusvaara <ilariliusvaara@welho.com>
Date: Mon, 3 Oct 2016 07:40:03 +0300 (EEST)
Sender: hurtta@siilo.fmi.fi
From: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Van Catha <vans554@gmail.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
X-Mailer: ELM [version ME+ 2.5 PLalpha41]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="UTF-8"
X-Filter: smtpVgate.fmi.fi: 3 received headers rewritten with id 20161003/05307/01
X-Filter: smtpVgate.fmi.fi: ID 5307/01, 1 parts scanned for known viruses
X-Filter: virkku.fmi.fi: ID 2846/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]); Mon, 03 Oct 2016 07:40:05 +0300 (EEST)
Received-SPF: none client-ip=193.166.223.36; envelope-from=hurtta@siilo.fmi.fi; helo=smtpVgate.fmi.fi
X-W3C-Hub-Spam-Status: No, score=-6.6
X-W3C-Hub-Spam-Report: AWL=-0.060, BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-2.641, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1bqv3J-0008PF-VT 56b059671d3f0623a6549e549a1b3d42
X-Original-To: ietf-http-wg@w3.org
Subject: Re: WebSocket2
Archived-At: <http://www.w3.org/mid/201610030440.u934e3kL031002@shell.siilo.fmi.fi>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32452
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: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Ilari Liusvaara <ilariliusvaara@welho.com>om>: (Sun Oct  2 20:19:05 2016)
> > > Well, I think the following would work and avoid SETTINGS:
> > > 
> > > -> :method ws2
> > > -> :scheme wss
> > > -> :authority foo.example
> > > -> :path /bar
> > > -> <optional extra parameters, e.g. compression support>
> > > <- :status 200
> > > <- sec-ws2-ack 1
> > > <- <optional negotiated extras>
> > 
> > If we can also assume that proxy does not ignore
> >    :method = ws2
> >    :scheme = ws
> > then this may work.
> 
> Oh yeah, that only works against dodgily implemented origins, not WS2-
> unsupporting proxies (that do something else than just realtime
> forwarding of unknown methods).
> 
> 
> If one is worried about the latter, one would need the SETTING then
> (one only needs to have server end signal support, since it is a
> capability server has that client may or may not use)..
> 

If forward proxy (= proxy configured on browser) supports both http and ftp, 
then it is checking :scheme. If it supports only http (and tunneling with 
CONNECT), then it can be lazy.

Reverse proxies (which DNS gives from :authority) are more likely
to be lazy.  These are either http/2 ⇒ http/1.1 or http/2 ⇒ http/2.
 
Reverse proxies may be also TLS termination point. So wss is not tunneled.

"Transparent" proxies; then perhaps SETTINGS does not work either.

> -Ilari

/ Kari Hurtta