- From: Brian Smith <brian@briansmith.org>
- Date: Fri, 31 Oct 2014 16:00:55 -0700
- To: Jason Greene <jason.greene@redhat.com>
- Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Received on Friday, 31 October 2014 23:01:22 UTC
Jason Greene <jason.greene@redhat.com> wrote: > Until the proper TLS APIs exist (I’m not holding my breath), or TLS 1.3 > occurs, this is the best action an implementer can take. Also, this working group decided a long time ago that it is reasonable to require TLS implementations to be changed to support HTTP/2. In fact, this working group actually required *every* TLS implementation to be changed to support ALPN, even though many of them would have worked fine, unmodified, with the NPN support that they already had. So, the argument that changes to TLS implementations may need to be modified has already been decided to be invalid. Cheers, Brian
Received on Friday, 31 October 2014 23:01:22 UTC