W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

ALPN OpenSSL implementation

From: Brian Raymor (MS OPEN TECH) <Brian.Raymor@microsoft.com>
Date: Fri, 15 Mar 2013 15:25:02 +0000
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-ID: <9813635c2ede4c028aed7d2baf8a5743@BL2PR03MB605.namprd03.prod.outlook.com>
As clarified in the HTTPBIS meeting this morning, there is an OpenSSL implementation of ALPN available. This was announced earlier on the TLS mailing list. Details below.

Please let me know if there are questions or feedback.


-----Original Message-----
From: tls-bounces@ietf.org [mailto:tls-bounces@ietf.org] On Behalf Of Brian Raymor (MS OPEN TECH)
Sent: Thursday, February 28, 2013 12:30 AM
To: Stephan Friedl (sfriedl; tls@ietf.org
Subject: Re: [TLS] Revision draft-friedl-tls-applayerprotoneg-02 Posted

Our HTML5 Labs HTTP/2.0 prototype has been updated to reflect the changes in the applayerprotoneg-02 internet draft. This prototype now leverages OpenSSL and Apache on the backend. 


The associated server patch is available as open source - http://html5labs.interopbridges.com/media/167447/alpn_patches.zip

Feedback on the code and the internet draft would be appreciated.

Brian Raymor
Microsoft Open Technologies, Inc. 
A subsidiary of Microsoft Corporation

> From: tls-bounces@ietf.org [mailto:tls-bounces@ietf.org] On Behalf Of Stephan Friedl (sfriedl)
> Sent: Friday, February 22, 2013 8:43 AM
> To: tls@ietf.org
> Subject: [TLS] Revision draft-friedl-tls-applayerprotoneg-02 Posted

> A revision of draft-friedl-tls-applayerprotoneg has been posted.  The following changes have been introduced into the draft in response to feedback from the working group:
> 1.       Section 3.1 "Application Layer Protocol Negotiation Extension" defines ProtocolNameList and ProtocolName as variable-length arrays, as typically done in TLS. This increases payload size by 2 bytes, but allows the use of the normal TLS parsers.
> 2.       Section 3.2 "Protocol Selection" defines a new fatal alert no_application_protocol, to be used with ALPN extension only, instead of using a generic handshake_failure alert. This is done to help distinguish application protocol negotiation issues from other handshake failures.
> We would greatly appreciate any comments and feedback on the draft.
> Best Wishes,
> Stephan Friedl, Andrei Popov

TLS mailing list
Received on Friday, 15 March 2013 15:27:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:10 UTC