Carsten Bormann wrote: > Note that RFC 7301 has published: http://tools.ietf.org/html/rfc7301 > ... +1. Anything we can do to move this forward? igrigorik (Ilya Grigorik)
ALPN [1] is a successor [2] to NPN, support for which was added in 2.0.0 [3]. HTTP/2 [4] is using ALPN to negotiate protocol support, and the spec is moving fast -- it'd be great to have ALPN support in one of the upcoming Ruby releas...igrigorik (Ilya Grigorik)
Hey guys, apologies about the wait. @Martin: I don't follow the IANA politics, but for what its worth, I would consider it stable at this point. The support is there in OpenSSL, we have 50% of the browser market share using it to nego...igrigorik (Ilya Grigorik)
@naruse: as Eric pointed out in his original ticket (#5929), I do believe this is a bug, as the current API advertises that it can set and use the dictionary, but that is not the case. I've opened a different / new ticket: http://bug...igrigorik (Ilya Grigorik)
OpenSSL 1.0.1+ added support for Next Protocol Negotiation (NPN) extensions. A couple of relevant links: - Google technical note: https://technotes.googlecode.com/git/nextprotoneg.html - IETF draft: http://tools.ietf.org/html/draft-a...igrigorik (Ilya Grigorik)
What are the odds of having this be backported to 1.9.x? We need custom dictionary support to support SPDY without relying on FFI or other native extensions. ex: https://github.com/igrigorik/spdy/blob/master/lib/spdy/compressor.rbigrigorik (Ilya Grigorik)
=begin Unfortunately can't pinpoint the exact problem, but this issue has been brought up by a number of people under 1.9.1 and 1.9.2 when running "god": https://github.com/mojombo/god/issues#issue/6 - see full thread
igrigorik (Ilya Grigorik)09:42 PM Ruby Feature #9390: Support for the ALPN TLS extension