Re: alpn identifiers (not again!)

On 11 June 2015 at 16:59, Amos Jeffries <> wrote:
> I've been thinking in the last few days that the problem may be that
> there was never an "https" ALPN token minted to match it. At the time it
> seemed okay since there was also never a HTTPS protocol name and nobody
> hit problems. Now not so much.

RFC 7301 defines "http/1.1", which (I believe) refers to HTTP/1.1 over TLS.

> RFC 7301 did not specify non-TLS usage for these tokens. The initial
> seeded registrations just got a reference to the protocol being used
> over-TLS irregardless of whether it existed *only* over TLS or not.

> RFC 7230 defines two usages for over-TCP and over-TLS. Making RFC 7301
> imply by omission that there is one ALPN token for both.

Or that it only applies to "x" over TLS.  My interpretation.

Received on Friday, 12 June 2015 00:24:37 UTC