> If the DNS name server is on a muti-sited host > (which I suppose makes sense if it is performing name-to-address > resolution for hosts which are muti-sited), then it needs to be configured > to return different site-local addresses for each given site to which it > is connected.
Distributed applications depend on consistent results from DNS, regardless of where the query came from. > Since Stateless Address Autoconfiguration or (eventually) DHCPv6 may be > used to configure addresses, the DNS name server also needs to understand > the site-local scope zone over which a DNS registration is made, placing > "global" addresses into the "global" pool and "site-local" addresses > associated with the site-local scope zone over which the registration is > received. As if such scope were visible to the DNS server (it isn't), or the DNS server could depend on results only being used in the scope for which they were intended (it can't). > Likewise, the host performing the registration needs to > restrict the site-local addresses which are registered to the site-local > scope zone in which they are valid. except that there's no way for the host to know where those addresses are valid. > There are probably other requirements for this to work as well. The only > point I'm trying to make is it isn't just as simple as connecting to > multiple sites and having this work properly without additional standards > being defined. indeed. and what compelling purpose does all of this complexity serve? none that I can see. Keith -------------------------------------------------------------------- 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] --------------------------------------------------------------------
