W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: 9.2.2 Cipher fallback and FF<->Jetty interop problem

From: Simone Bordet <simone.bordet@gmail.com>
Date: Thu, 18 Sep 2014 18:33:49 +0200
Message-ID: <CAFWmRJ1ZEwKP9HaWJODjU6CZ8mbw9sticm7LJ8bL_iLy7qc6Bw@mail.gmail.com>
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: Greg Wilkins <gregw@intalio.com>, HTTP Working Group <ietf-http-wg@w3.org>

On Thu, Sep 18, 2014 at 5:41 PM, Roy T. Fielding <fielding@gbiv.com> wrote:
> I still don't believe that any of these requirements belong in h2,
> and I won't implement them even if they end up in the RFC.

As much as I would like to have 9.2.2 reworded to delegate to the TLS
spec, not implementing it on servers while all major browsers
implements it will result in a closed connection, no fallback and an
empty white page.
Not really good for HTTP/2, but alas.

Unfortunately there seems to be no way to make the editors change
their mind, so I am curious what kind of ripple effects do you foresee
by not implementing 9.2.2 as it currently stands.
We can weigh these effects and perhaps decide to not implement 9.2.2
in Jetty as well.

Thanks !

Simone Bordet
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz
Received on Thursday, 18 September 2014 16:34:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:38 UTC