RE: [openssl.org #3073] [Patch] ALPN Implementation for OpenSSL
We believe our latest patch has addressed all feedback we have received so far. As far as we can tell this is ready for inclusion in the main trunk of the project. Naturally, if this is not the case and we still need to make changes we are happy to work with the community. Assuming no further changes are needed please let us know how we can ensure this gets applied to trunk - Parashuram __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
RE: [Patch] ALPN Implementation for OpenSSL
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
RE: [Patch] ALPN Implementation for OpenSSL
Hi, Attached the Patch for the OpenSSL with ALPN implementation. -Original Message- From: Parashuram Narasimhan (MS OPEN TECH) Sent: Thursday, June 13, 2013 5:57 AM To: 'openssl-dev@openssl.org' Subject: [Patch] ALPN Implementation for OpenSSL Hi, I work for Microsoft Open Technologies, a wholly owned subsidiary of Microsoft Corp. My team is currently working on the standardization process for HTTP/2.0: as I believe many of you may have heard, the latest working draft @ IETF requires using ALPN as the mechanism for secure negotiation, and we have been working on a patch to OpenSSL to allow for early testing and interoperability. 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). We will be submitting a patch request to openssl-b...@openssl.org as advised by https://github.com/openssl/openssl/blob/master/README#L178, and we will be following discussions the mailing lists. Please feel free to give us your feedback and, in case you would be interested in a formal contribution, advice on the steps we need to take. Thanks Parashuram Microsoft Open Technologies Inc openssl-alpn.patch Description: openssl-alpn.patch
[Patch] ALPN Implementation for OpenSSL
Hi, I work for Microsoft Open Technologies, a wholly owned subsidiary of Microsoft Corp. My team is currently working on the standardization process for HTTP/2.0: as I believe many of you may have heard, the latest working draft @ IETF requires using ALPN as the mechanism for secure negotiation, and we have been working on a patch to OpenSSL to allow for early testing and interoperability. 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). We will be submitting a patch request to openssl-b...@openssl.org as advised by https://github.com/openssl/openssl/blob/master/README#L178, and we will be following discussions the mailing lists. Please feel free to give us your feedback and, in case you would be interested in a formal contribution, advice on the steps we need to take. Thanks Parashuram Microsoft Open Technologies Inc __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
