2011/7/27 Willy Tarreau <w@xxxxxx>: > That's where I think you're mistaken. As long as you think of it as mandatory > this will not be possible. Hi Willy, as I've explained several times in these threads, if a WS client is not mandated to perform SRV given a WS URI domain, then the service provider cannot rely on SRV records. This is, let's assume that a WS service provider offers a WS URI like "ws://mydomain.org", with these records (simplifying): - SRV: 1.1.1.1:80, 1.1.1.2:80, 1.1.1.3:90 - A: 1.1.1.1 So assuming that SRV is optional for clients, the provider does not know how many clients would use SRV or just A. Imagine the service provider expects millons of concurrent users. He must be ready to receive all those users in 1.1.1.1 (if they don't use SRV). So the service provider must build a complex/expensive balancer system in server side (BGP and all that stuf) just for the case in which most of the clients would not perform SRV procedures. So 1.1.1.1 would be in fact a balancer with N hosts providing the WS service behind it. At the same time, if clients use SRV then load-balancing and failover would be automatically provided by the SRV capabilities. No need for like-BGS solutions in server side. So the question is: which service provider would spend resources, time and efforts building two different load-balancing/failover systems?. If a provider can build the "BGP" solution then it will not need SRV. And another provider which cannot build a "BGP" solution could not entirely rely on SRV capabilities as maybe most of the clients would not use it. In the other side, if service providers must be ready to accept all the traffic in the IP resolved via single DNS A query, then nobody would need SRV and webbrowsers would just remove it (the Mozilla developer has already said in these threads that he won't implement it "due to latency reasons"). Also the fact that DNS is not mandated by HTTP neither WS makes things even worse. In contrast, in XMPP and SIP protocols DNS is mandatory and also SRV procedures. If you are a SIP provider hosting the service with domain "mydomain.org" you don't ever need to have a working A record for mydomain.org, but just SRV (and optionally NAPTR). Or you could just have A record and not use SRV at all. SIP client procedures for locating servers (RFC 3263) mandate first trying SRV and then A/AAAA, so things would work in any case. So correct me if I'm wrong, but making SRV optional for clients (in *any* protocol) is not something I consider feasible or useful. Regards. -- Iñaki Baz Castillo <ibc@xxxxxxxxx> _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf