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: Wed, 24 Sep 2014 11:08:12 +0200
Message-ID: <CAFWmRJ1fyQjhJTxUoVFc5-5+adBd254=x1HXrK8Nb71vPU6X9Q@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: Roland Zink <roland@zinks.de>, HTTP Working Group <ietf-http-wg@w3.org>

On Wed, Sep 24, 2014 at 10:54 AM, Eric Rescorla <ekr@rtfm.com> wrote:
> Wait, how does this happen? When we introduce X we label it as acceptable
> for h2. Old clients won't offer X because they won't have it and when they
> do have it they should know it's acceptable for h2.

Old h2 clients that are dynamically linked to a new TLS implementation
will have X but not know that is acceptable.

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 Wednesday, 24 September 2014 09:08:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:10 UTC