From: ilya@igvita.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:66573] [ruby-trunk - Feature #9390] Support for the ALPN TLS extension
Date: Sat, 29 Nov 2014 21:42:09 +0000 [thread overview]
Message-ID: <redmine.journal-50188.20141129214209.056750235eeb5b6d@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-9390.20140110163059@ruby-lang.org
Issue #9390 has been updated by Ilya Grigorik.
Carsten Bormann wrote:
> Note that RFC 7301 has published: http://tools.ietf.org/html/rfc7301
>
> HTTP/2 is nearing completion and requires ALPN, so if Ruby wants to play in this space, ALPN needs to be done with high priority now.
+1. Anything we can do to move this forward?
----------------------------------------
Feature #9390: Support for the ALPN TLS extension
https://bugs.ruby-lang.org/issues/9390#change-50188
* Author: Ilya Grigorik
* Status: Assigned
* Priority: Normal
* Assignee: Martin Bosslet
* Category: ext/openssl
* Target version:
----------------------------------------
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 releases. Current status of ALPN support in various TLS libraries and languages: https://github.com/http2/http2-spec/wiki/ALPN-Status.
As a side note, for anyone interested, I have an implementation of draft-06 http/2 spec: https://github.com/igrigorik/http-2
[1] http://tools.ietf.org/html/draft-friedl-tls-applayerprotoneg-02
[2] https://www.imperialviolet.org/2013/03/20/alpn.html
[3] https://bugs.ruby-lang.org/issues/6503
[4] http://tools.ietf.org/html/draft-ietf-httpbis-http2-00
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2014-11-29 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-9390.20140110163059@ruby-lang.org>
2014-01-10 16:31 ` [ruby-core:59682] [ruby-trunk - Feature #9390] (Open) Support for the ALPN TLS extension Ilya, Grigorik
2014-12-24 22:46 ` [ruby-core:67111] " Eric Wong
2014-01-14 1:16 ` [ruby-core:59747] [ruby-trunk - Feature #9390] [Assigned] " Eric, Hodel
2014-08-04 22:28 ` [ruby-core:64193] [ruby-trunk - Feature #9390] " cabo
2014-11-29 21:42 ` ilya [this message]
2014-11-29 22:08 ` [ruby-core:66574] " Eric Wong
2014-11-29 22:08 ` [ruby-core:66575] " normalperson
2014-12-24 22:48 ` [ruby-core:67112] " normalperson
2015-02-07 2:03 ` [ruby-core:68052] [Ruby trunk " 34test45test
2015-07-15 2:07 ` [ruby-core:69974] " tenderlove
2015-07-15 3:03 ` [ruby-core:69975] " Eric Wong
2015-07-15 14:31 ` [ruby-core:69978] " tenderlove
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-50188.20141129214209.056750235eeb5b6d@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).