Hi, I realize it has only been a few days since we originally posted this patch for Application Layer Protocol Negotiation (ALPN) support. I just wanted to expand on why we think this is an important patch for OpenSSL. The latest HTTP/2.0 draft specifies support for a TLS extension called ALPN to negotiate HTTP/2.0 within the TLS handshake: http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-01
As I wrote in the original message [ http://www.mail-archive.com/openssl-dev@openssl.org/msg32630.html ] - More background is available at http://tools.ietf.org/html/draft-ietf-httpbis-http2-03#section-2.3, but for your convenience here goes the relevant snippet: 2.3. Starting HTTP/2.0 for "https:" URIs A client that makes a request to an "https:" URI without prior knowledge about support for HTTP/2.0 uses TLS [RFC5246] with the application layer protocol negotiation extension [TLSALPN]. Once TLS negotiation is complete, both the client and the server send a connection header (Section 3.2). The good news is we've already implemented it. We really want to work with you to get this patch into OpenSSL to help developers of HTTP/2.0 draft implementations. We welcome your assistance to review this patch. -- Parashuram ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
