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

Re: HTTP/2, "h2t" and protocol identifiers in general

From: Yutaka Hirano <yhirano@google.com>
Date: Mon, 17 Mar 2014 16:14:29 +0900
Message-ID: <CABihn6EwO9+DV8xnMGyiXcFTKgbqFmNyKPJ-TxuZQc45n5rCVw@mail.gmail.com>
To: William Chan (陈智昌) <willchan@chromium.org>
Cc: Mark Nottingham <mnot@mnot.net>, Roberto Peon <grmocg@gmail.com>, Martin Thomson <martin.thomson@gmail.com>, Matthew Kerwin <matthew@kerwin.net.au>, Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
On Wed, Mar 5, 2014 at 3:29 AM, William Chan (陈智昌) <willchan@chromium.org>
 wrote:
>
> I just want to point out that both of these approaches requires an extra
> roundtrip in the TLS-ALPN HTTP/2 establishment case. Which is unfortunate
> and might lead clients to race more connections.
>
Yes, that's why we are proposing ALPN identifiers for WebSocket over
HTTP2 used in ALPN in addition to SETTINGS (or ALTSVC).

Thanks,


On Wed, Mar 5, 2014 at 3:29 AM, William Chan (陈智昌) <willchan@chromium.org>wrote:

> On Tue, Mar 4, 2014 at 9:07 AM, Mark Nottingham <mnot@mnot.net> wrote:
>
>>
>> On 4 Mar 2014, at 11:25 am, Roberto Peon <grmocg@gmail.com> wrote:
>>
>> > How does one determine WS usnig HTTP2/TLS/TCP as compared to WS over
>> TLS/TCP?
>>
>> We haven’t discussed much yet, but there are two (not necessarily
>> exclusive) proposals:
>>
>> - You try; if the other end doesn’t support WS, it refuses with an error
>> code.
>>
>> - You discover what schemes the server supports using a SETTINGS.
>>
>
> I just want to point out that both of these approaches requires an extra
> roundtrip in the TLS-ALPN HTTP/2 establishment case. Which is unfortunate
> and might lead clients to race more connections.
>
>
>> This assumes you already have an HTTP/2 connection open to the server; if
>> you don’t, you have to figure out what to do, but I *think* that’s a WS/1
>> problem, not ours.
>>
>> Cheers,
>>
>>
>> --
>> Mark Nottingham   http://www.mnot.net/
>>
>>
>>
>>
>>
>
Received on Monday, 17 March 2014 07:14:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC