Hi Margaret, On Sat, 2003-03-15 at 14:40, Margaret Wasserman wrote: > > For example, this mechanism would not work properly when a local > > caching resolver is used. In this common configuration, ... > > > >What exactly do you mean by "a local caching resolver"? Do you mean, > >e.g. a BIND DNS caching server running on the same node of the > >resolver? If so, I don't think this is not a so common > >configuration. > > I'll have to ask whoever sent me the text :-). I think it was > Rob Austein.
It's not so unheard of to run a local copy of BIND for caching. I used to do this at home myself when my ISP was having problems with their DNS servers. Some people also routinely use pdnsd with their Linux/FreeBSD boxes: http://home.t-online.de/home/Moestl/ > > and > > applications will have to add a default zone ID to IP addresses > > when one is not provided. > > > >This is not necessarily true, or at least an implementation dependent. > >In fact, implementation in fact supports the ability to set a default > >zone ID in the kernel, so that applications need not be scope-aware. > > Do you set a default zone ID for each scope? So, there would be a > default link and a default site? I can't comment on the KAME implementation, but in general you can just specify a default interface and read the default zone IDs for each scope level from the scope table of that interface. Our implementation actually has a mechanism, whereby we let the stack select the default interface, but we can constrain the set of possible interfaces to any specific zone. So we can say, for instance, pick any interface from this link, or pick any interface from this site. MikaL -------------------------------------------------------------------- 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] --------------------------------------------------------------------
