I agree that DNS SRV is a matter outside the scope of websockets, which (for better or for worse) use a connection that is established via a HTTP request. Thus I do not think that the establishment of a HTTP connection for websockets should differ in any way from the name resolution handling of other HTTP connections made by a user-agent. If the advocates of DNS SRV wish for websocket to use it, then they need to convince HTTPbis (I think that is the right WG?) to adopt it for all of HTTP and then websockets will inherit that feature. If in future, there is a proposal to directly establish websocket connections without a HTTP upgrade (as David Endicott has alluded to), then I think DNS SRV should definitely be supported. regards _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf