RE: WebSocket2

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Thu, 13 October 2016 10:21 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 699B212952E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 13 Oct 2016 03:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.916
X-Spam-Level:
X-Spam-Status: No, score=-9.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=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 ycMUQKQu60SB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 13 Oct 2016 03:21:18 -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 C47981294ED for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 13 Oct 2016 03:21:18 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bud4r-0004Hb-4U for ietf-http-wg-dist@listhub.w3.org; Thu, 13 Oct 2016 10:17:29 +0000
Resent-Date: Thu, 13 Oct 2016 10:17:29 +0000
Resent-Message-Id: <E1bud4r-0004Hb-4U@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <Lucas.Pardue@bbc.co.uk>) id 1bud4m-0004Cr-CK for ietf-http-wg@listhub.w3.org; Thu, 13 Oct 2016 10:17:24 +0000
Received: from mailout0.telhc.bbc.co.uk ([132.185.161.179]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <Lucas.Pardue@bbc.co.uk>) id 1bud4Z-0006X9-DU for ietf-http-wg@w3.org; Thu, 13 Oct 2016 10:17:20 +0000
Received: from BGB01XI1001.national.core.bbc.co.uk ([10.184.50.51]) by mailout0.telhc.bbc.co.uk (8.15.2/8.14.3) with ESMTP id u9DAGPkq026991; Thu, 13 Oct 2016 11:16:25 +0100 (BST)
Received: from BGB01XI1015.national.core.bbc.co.uk (10.161.14.78) by BGB01XI1001.national.core.bbc.co.uk (10.184.50.51) with Microsoft SMTP Server (TLS) id 14.3.195.1; Thu, 13 Oct 2016 11:16:25 +0100
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1015.national.core.bbc.co.uk ([10.161.14.78]) with mapi id 14.03.0195.001; Thu, 13 Oct 2016 11:16:25 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Van Catha <vans554@gmail.com>, Takeshi Yoshino <tyoshino@google.com>
CC: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, Ilari Liusvaara <ilariliusvaara@welho.com>, HTTP working group mailing list <ietf-http-wg@w3.org>
Thread-Topic: WebSocket2
Thread-Index: AQHSG2C2tqTe4VYRKE2iHfxnWXEX8KCS/oyAgADa8wCAAAeCAIAACMCAgADUz4CAACXOAIAAD0sAgAAaDQCAAA/DgIAAPSmAgAC+QoCAAMkIAIABNu2AgABFNACAAO0CgIAAuJmAgAw4w9A=
Date: Thu, 13 Oct 2016 10:16:24 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3766E4A0@bgb01xud1012>
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> <201610030440.u934e3kL031002@shell.siilo.fmi.fi> <CAG-EYCgEs1oSdLeLVwd12ECaL=+3pzytuy89xFWvvKCEY8fi4g@mail.gmail.com> <CAH9hSJaMsKaoTK+kr2X_GP_T7=jcDQtFLSusYrV+nDWCadcyxg@mail.gmail.com> <201610041520.u94FK6vV008976@shell.siilo.fmi.fi> <CAH9hSJY40AnYE1JTuc1aYFzRtaT-+PwX8M7YeVj2cbosCfD0TQ@mail.gmail.com> <CAG-EYCiCkC2XWuhbOtwKusW28=p-sYLArDR6MfN1Zc41+9f2-A@mail.gmail.com>
In-Reply-To: <CAG-EYCiCkC2XWuhbOtwKusW28=p-sYLArDR6MfN1Zc41+9f2-A@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.213]
X-TM-AS-Product-Ver: SMEX-11.0.0.4179-8.000.1202-22634.006
X-TM-AS-Result: No--20.238400-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A3766E4A0bgb01xud1012_"
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: c91d45b2-6e10-4209-9543-d9970fac71b7
X-EXCLAIMER-MD-CONFIG: 1cd3ac1c-62e5-43f2-8404-6b688271c769
Received-SPF: pass client-ip=132.185.161.179; envelope-from=Lucas.Pardue@bbc.co.uk; helo=mailout0.telhc.bbc.co.uk
X-W3C-Hub-Spam-Status: No, score=-5.1
X-W3C-Hub-Spam-Report: AWL=-1.030, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.362, SPF_PASS=-0.001, W3C_NW=0.5
X-W3C-Scan-Sig: lisa.w3.org 1bud4Z-0006X9-DU 88acc0686f7220c20ae0ec79bd11494c
X-Original-To: ietf-http-wg@w3.org
Subject: RE: WebSocket2
Archived-At: <http://www.w3.org/mid/7CF7F94CB496BF4FAB1676F375F9666A3766E4A0@bgb01xud1012>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32575
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>

On 05 October 2016, Van Catha wrote: 17:29

Standardized protocol or not is irrelevant.  I was simply considering the options
and what would work.  QUIC uses different negotiation and transport frames then HTTP/2
does (also QUIC does not have HTTP/2 SETTINGS frames). I was proposing ideas at
tackling the problem to make WebSocket2 work across different transport layers.

The current QUIC-H2 mapping document (https://tools.ietf.org/html/draft-shade-quic-http2-mapping-00) discusses the use of HTTP/2 SETTINGS frames in section 3. Some settings are superseded by QUIC transport parameters but I would think that extension negotiation would work fine in QUIC. The charter explicitly calls out accommodation for H2 extension mechanisms.

Lucas




----------------------------

http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.

---------------------