Re: ALPN ID for HTTP/2 interop

Dang,  wish I had read the WG this morning before work.... have just
updated jetty-9.3.S to support protocol aliases, so our current impl is
recognised as both h2-14 and h2-15.  Our client only sends h2-14

Oh well, the alias mechanism will probably be handy when we go from h2-16
to h2

cheers


On 14 November 2014 23:27, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
wrote:

>
>
> On Fri, Nov 14, 2014 at 12:14 PM, Mark Nottingham <mnot@mnot.net> wrote:
>
>> Note that we have *not* nominated -15 as an implementation / interop
>> draft.
>>
>> People who are advertising it are doing so at their own risk...
>>
>>
>
> So the rule is clear: in order to join the current global interop,​
> implementations must negotiate h2-14 since it is the last draft designated
> as implementation.
>
> This clears my immediate concern about interop issue.
>
> Best regards,
> Tatsuhiro Tsujikawa
>
>
>> Regards,
>>
>>
>> > On 13 Nov 2014, at 2:59 am, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > We've been doing interop using h2-14 ALPN ID for a while.
>> > Some client/server now only advertise h2-15, others do both h2-14 and
>> h2-15.
>> > Since draft-15 is binary compatible to h2-14, for code simplicity and
>> interop, it would be better to stick to h2-14, unless we introduce binary
>> incompatible changes in the future draft.
>> >
>> > Thoughts?
>> >
>> > Current status of ALPN ID usage:
>> > Firefox nightly: h2-14, h2-15
>> > Chrome canary: h2-15
>> > Google server: h2-15
>> > Twitter: h2-14
>> > nghttp2: h2-14
>> >
>> > Best regards,
>> > Tatsuhiro Tsujikawa
>> >
>>
>> --
>> Mark Nottingham   http://www.mnot.net/
>>
>>
>>
>>
>


-- 
Greg Wilkins <gregw@intalio.com>  @  Webtide - *an Intalio subsidiary*
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.