W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: Our ALPN protocol IDs

From: James Cloos <cloos@jhcloos.com>
Date: Fri, 06 Dec 2013 19:07:59 -0500
To: "Adrien de Croy" <adrien@qbik.com>
Cc: "Martin Thomson" <martin.thomson@gmail.com>, "Carsten Bormann" <cabo@tzi.org>, "Mark Nottingham" <mnot@mnot.net>, "HTTP Working Group" <ietf-http-wg@w3.org>
Message-ID: <m3ppp9o747.fsf@carbon.jhcloos.org>
>>>>> "AdC" == Adrien de Croy <adrien@qbik.com> writes:

AdC> is there no version transmitted anywhere (outside of ALPN)....
AdC> or are we going to rely on ALPN to communicate that?

The rfc 2616 Upgrade (as per the current draft for port 80 use) can
specify versions, too.  As an example, a client could ask for:

  Upgrade: HTTP/2.0, HTTP/2.1
  Connection: Upgrade

The 101 Switching Protocols responce will state which token the server
is upgrading to.

James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6
Received on Saturday, 7 December 2013 00:19:22 UTC

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