> -----Original Message----- > From: Markku Savela [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 11, 2002 10:17 AM > To: [EMAIL PROTECTED] > Subject: Re: IPv6 Scoped Addresses and Routing Protocols > > Well, I've not yet fully gotten into issue of getting site local > addresses from the name server, but... > > ... I assume when a resolver gets an address as a reply from the DNS, > it will supply the scope id from the interface which the DNS reply > came in. And, this applies to all scope levels (consider, multicast > groups could be in DNS too, with any of the 15 or so scope levels).
Correct. > Now, for this to truly work, the DNS server does need some extra code > to deal with non-global scopes. The database must include the scope in > some form (for example interface name), and it must not return replies > of non-local addresses to other than indicated interface. Or just implement Erik Nordmark's draft on the host and the DNS server doesn't need to do anything. This is the approach we prefer (not to say we have any objection to modifying the DNS server too, just that it can work without it). > However, this seems to be a local implementation issue, which does not > change the protocol on the wire. > > I think similar considerations apply to routing protocols: the zone > ids are always available from the interface which the packet is > using. Of course, some system admin must configure them to the > interface first. Correct. -Dave -------------------------------------------------------------------- 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] --------------------------------------------------------------------
