On Fri, Jul 22, 2011 at 07:34:49PM +0900, Masataka Ohta wrote: > Dave Cridland wrote: > > >> Where is a proof? > > > > Sorry, I've a habit of using the word "proof" in the English > > > 1) There are no SRV records. > > 2) Therefore browsers do not support them. > > 3) Therefore you'd need to allow for A-lookup as fallback for the > > forseeable future. > > 4) Therefore there's no incentive for browsers to support SRV. > > That's a perfect proof against IPv6 deployment. Infrastructure > won't be updated. Ironic you should mention that, because if more protocols supported SRV, the content providers could have a lot more control over the IPv6 transition. For example: _http._tcp.example.com. SRV 0 99 80 www.example.com. _http._tcp.example.com. SRV 0 1 80 www-ds.example.com. www.example.com. A 198.0.2.1 www-ds.example.com. A 198.0.2.2 www-ds.example.com. AAAA 2001:db8::2 I.e., content providers could control/measure their probability of failure. As www-ds.example.com's success rate improves, its weight can be increased. -- Scott Schmit _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf