RE: WebSocket ALPN identifier

My initial reaction is “yes” to both questions.  😊

So the idea is that HTTP clients make a request to an endpoint that might be a WebSocket endpoint, but it instead directs them to make a request elsewhere using HTTP/1.1 which will upgrade to WebSockets?  Why wouldn’t it just Alt-Svc the HTTP resource that the client already expects to support WebSocket upgrades?

Or are you actually talking about HTTP-over-WebSockets?

From: Lucas Pardue []
Sent: Wednesday, August 23, 2017 10:33 AM
To: HTTP Working Group <>
Subject: WebSocket ALPN identifier

Bare with me,

Imagine a hypothetical system that wants to use Alt-Svc to direct clients to a particular WebSocket endpoint that can deliver appropriately framed HTTP resources.

To support this, I’m thinking of using the ALPN identifier(s) “ws” and “wss”. Since they don’t already exist in the IANA registry<>, I have thought about a short I-D similar to draft-ietf-rtcweb-alpn<>.

I do not intend for the proposed identifiers to be used for actual TLS ALPN during handshake. However, I don’t want to preclude that if there’s a desire to do so.

Is this idea too far in the realm of absurdity? Is HTTPbis the appropriate WG to pursue this in?


Received on Wednesday, 23 August 2017 17:46:18 UTC