Re: Our ALPN protocol IDs

------ Original Message ------
From: "Martin Thomson" <>

>Yes, HTTP/2.0 explicitly doesn't allow version negotiation "within"
>the protocol. We have ALPN and intend to use it ...and nothing else.

well.. this presumes we're only going to work inside a TLS framework.

Roll out the mandatory TLS argument again.

I don't think we can rely on only ALPN.

>>  Maybe it is worth adding a section that explains the protocol 
>>evolution model of HTTP/2.0.
>Like this?
>   Any new, incompatible version of HTTP will use a different
>identifier string. For instance, a hypothetical HTTP/2.1 might be
>identified by the string "DUCK".

Received on Thursday, 5 December 2013 21:19:50 UTC