- From: Carsten Bormann <cabo@tzi.org>
- Date: Thu, 5 Dec 2013 18:49:44 +0100
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
> For HTTP/2.x, the negotiation between HTTP/2.0 and a hypothetical > HTTP/2.1 would use ALPN and "h2" and maybe "h2.1". Any unique string > would suffice. Works for me. (Thinking about how the new identifiers will look like still doesn�t hurt.) > 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�. Well, is HTTP/2.1 going to be �incompatible� with HTTP/2.0? (Mark seems to think there is some form of compatibility as long as we don�t change the major version. That�s why I�d like to see something written up about the evolution model, even if it is by nature going to be tentative.) Gr��e, Carsten
Received on Thursday, 5 December 2013 17:50:15 UTC