In message <537c47f9.4040...@necom830.hpcl.titech.ac.jp>, Masataka Ohta writes: > Mark Andrews wrote: > > >> What's wrong with: > >> > >> _http._tcp.example.net. SRV ... www.example.net. > > > > Nothing. > > So, without (C/E)NAME changes, the possibility of the following > configuration: > > _http._tcp.example.net. SRV ... example.net.hoster.net. > example.net.hoster.net CNAME serverX.hoster.net > serverX.hoster.net A > serverX.hoster.net AAAA > > will motivate the hoster deploy SRV. Right?
Yes, but the hoster doesn't have a say in it. If they did it would already be done because that is a lot simpler and cleaner than all the other hacks being done. You need to get the browser and proxy vendors to update their code. Giving them a spec to work to is the first step. Mark > Masataka Ohta -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
