2011/7/22 Bruce Atherton <bruce(_at_)callenish(_dot_)com>:
You are right that it would be impossible to require all environments that
wanted to add Websockets support, whether client or server, to change their
DNS to have NAPTR and SRV records. After all, Websockets is intended to
integrate easily into the already existing HTTP infrastructure.
What is being proposed, though, is to require clients to resolve the
hostname portion of ws: and wss: URLs by _first_ looking for NAPTR and SRV
records (unless, of course, the hostname is already an IP address). If a
NAPTR record is found, use it to look up an SRV record (otherwise use a
default). If an SRV record is found, use it to look up the A or AAAA record.
If no SRV record is found, look up the record exactly the same as if you
were looking up an HTTP host, by using the host name from the URL.
Well, in SIP there are NAPTR records because SIP can work over
different transports (UDP, TCP, TLS-TCP. SCTP, TLS-SCTP). In case of
WebSocket, it just defined for TCP so NAPTR records don't make sense.
So just SRV is required:
a) _ws._tcp.DOMAIN.COM for WS URI
b) _wss._tcp.DOMAIN.COM for WSS URI
Regards.
--
Iñaki Baz Castillo
<ibc(_at_)aliax(_dot_)net>
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf