- From: Jason Greene <jason.greene@redhat.com>
- Date: Fri, 31 Oct 2014 22:51:44 -0500
- To: Brian Smith <brian@briansmith.org>
- Cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
> On Oct 31, 2014, at 6:00 PM, Brian Smith <brian@briansmith.org> wrote: > > 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. I don’t think that situation is comparable because ALPN was discussed and favored by the TLS WG. -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Saturday, 1 November 2014 03:52:14 UTC