- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Sat, 19 Oct 2013 15:49:41 +1300
- To: ietf-http-wg@w3.org
On 19/10/2013 7:12 a.m., Andrei Popov wrote: > > Hi Mark, > > SPDY and HTTP/1.1 protocol IDs are defined in the ALPN draft so that > ALPN can be immediately used to negotiate the same protocols as NPN. > We had originally defined an HTTP/2 protocol ID as well, but removed > it from the latest versions of the draft so that the HTTPbis WG can > specify the appropriate protocol ID(s). > > ALPN protocol IDs are defined as opaque non-empty octet strings, which > allows for a compact representation of a large number of IDs. This > does not prevent the HTTPbis WG from defining US-ASCII or UTF-8 > protocol IDs for use on the Web. Do you have concerns about the > representation of protocol IDs in ALPN? > In addition to the worry about ALPN draft defining any there is the issue of case-sensitivity for the ones it does list. When I last read the draf it most definitely did NOT specify SPDY and HTTP/1.1 - it did specify some non-existent spdy/* and http/1.1 tokens. Has that been corrected? Amos
Received on Saturday, 19 October 2013 02:50:11 UTC