On Wed, 16 Oct 2002, Margaret Wasserman wrote: > >Options a) - c) should be sufficient to describe how the routing system > >will get the information. > > The three points you mention all indicate that you would "run a > routing protocol" to inject routes into the routing system.
Yep. Routing protocol has to be run anyway (static routes can be considered as a poor man's routing protocol and it works just as well) in the network to propagate information so this is natural. > Are > you just assuming that the routing protocol would be manual > configured with the routing information needed for packets to > the well-known addresses to reach the DNS servers? Yes. a) like 'ipv6 route fec0:000:0000:ffff::1 3ffe:ffff:ffff::1' on the first hop router(s). b) run a routing protocol, no biggie (e.g. BGP is ok and you can restrict the advertisement so even if the node is compromised, it can't jeopardize the whole routing system). c) run basically b) embedded in the process, or an equivalent (e.g. check the DNS server functionality periodically and kill the routing process if DNS server is dead) -- 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] --------------------------------------------------------------------
