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<https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids>, I have thought about a short I-D similar to draft-ietf-rtcweb-alpn<https://tools.ietf.org/html/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?

Regards
Lucas

Received on Wednesday, 23 August 2017 17:33:14 UTC