On Fri, 11 Oct 2002, Bob Hinden wrote: I must chime in to say I dislike this approach a bit, but it could be salvageable. (Though, I must admit I like an option in RA's more..)
Most of all, I dislike using *3* well known site local addresses. One should suffice just fine. Remember that this mechanism, at least in my eyes, is intended for *bootstrapping* only. After there is something that works, one could use some other mechanism (e.g. a DNS lookup :-) to discover *real* DNS server addresses and ignore the site local. It seems to me that _3_ addresses just triples delays (5-10 seconds each, per DNS lookup?) if none of those have been configured in the site. In addition, I greatly dislike section 5.2, that is DNS forwarding between sites. If we have to implement site-border router behaviour, let's *NOT* require it in every cheapo 50$ DSL router. btw, in introduction: s/usefull/useful/, s/moble/mobile/; in section 3: s/as DNS resolver/as DNS resolvers/. -- Pekka Savola "Tell me of difficulties surmounted, Netcore Oy not those you stumble over and fall" Systems. Networks. Security. -- Robert Jordan: A Crown of Swords -------------------------------------------------------------------- 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] --------------------------------------------------------------------
