Re: How to handle HTTP/2 negotiation failure WRT TLS

It's not clear to me what "this wasn't an issue" means. I'm guessing
that means that what we have in the spec is OK and it's not necessary
to discuss how to handle negotiation failure and just let
implementations figure it out. That's fine by me.

I observe that as per
http://dxr.mozilla.org/mozilla-central/source/netwerk/protocol/http/Http2Session.cpp,
Firefox appears to hard fail. And my inclination is to enforce the
same policy in Chromium. This will affect other implementations that
wish to interoperate with these browsers.

As for the meta-procedural commentary, I disagree that all thoughts
must be fully baked before discussing in the open. But I've no
interest in debating that decision, so if the working group does not
want me/Chromium to share half-baked thoughts on stuff, that's fine
and I will stop sharing them. Sorry for the noise.

Cheers.

On Sat, Feb 1, 2014 at 1:17 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> On 1 February 2014 09:20, William Chan (陈智昌) <willchan@chromium.org> wrote:
>> Are you seriously
>> saying that if we have potential concerns without analysis we should
>> not voice them because it equates to scaremongering?
>
> It was a poor choice of words, I'll concede.  But I don't think that
> hand-waving is constructive when it comes to identifying issues.  It
> didn't take me long to conclude that this wasn't an issue.  I don't
> want to discourage you from sharing input (I hope that could encourage
> your colleagues to share as well; nameless others are hard to conduct
> conversations with), but it would be nice if some more time was spent
> on identifying problems more concretely.

Received on Saturday, 1 February 2014 21:42:53 UTC