> > When a multi-sited implementation gets site-local addresses from > > the DNS (assuming that it runs two-faced DNS and returns site-locals), > > how will the multi-sited host know which site the addresses are in? > > My guess, and tentative implementation is that the resolver library > completes the scope id to the address using the interface from which > the DNS reply came in.
You may also need to send the DNS query into each site-local scope zone in order to obtain all necessary results, or even to obtain any results, if a given host name only resolves to site-local addresses in one of the site-local scope zones. 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. 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. 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. 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. Roy -------------------------------------------------------------------- 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] --------------------------------------------------------------------
