At Mon, 29 Apr 2002 18:14:59 +0200, Hesham Soliman wrote: > > How does anycast have this problem? Specifically, how does the DNS > discovery draft have this problem?
Server location via anycast means that one is using the routing system to keep track of the location of the DNS server. That is, the location of the DNS server is (somehow) injected into the routing system, and the routing system is now responsible for handing out that information to any client that wants to know. If the server goes down, moves, whatever, the DNS server becomes unreachable until the routing system converges on a new useful answer, and how exactly does the routing system know that the DNS server is gone, anyway? Does the DNS server now have to speak OSPFv3, or is there some human sitting at a 24x7 desk somewhere waiting to push a button on failure, or what? One could certainly build a system this way, but I'm not convinced that it's more robust than the other options we've been discussing. -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
