In RFC-2461 "6.3.5 Timing out Prefixes adn Default Routers" it says:
Whenever the Lifetime of an entry in the Default Router List expires, that entry is discarded. When removing a router from the Default Router list, the node MUST update the Destination Cache in such a way that all entries using the router perform next-hop determination again rather than continue sending traffic to the (deleted) router. My problem with this is: if RA has lifetime=0, it only means it stops being a default router, router is *NOT* "(deleted)". It can still act as a router for other more specific prefixes (for example, from draft-ietf-ipv6-router-selection-01.txt). It not a big deal to delete destination cache entries, they will just get reinserted, when needed. But I just wanted to hear if anyone else has opinions about this? - if router is advertising "More Specific routes" every 15s, but does not want to be a default router, the side effect is that destination cache entries for that router are flushed on every RA, even for "specific routes" - if we have a special non-default router, which gets its "clients" only through "redirects", those entries are cleared also on RA from this router. [The reason I noticed, once again TAHI test failed, because *I* only removed those destinations that actually are related to the default route. I didn't remove redirections, for example... I suppose I have to fix this feature to be RFC compliant? :-] -------------------------------------------------------------------- 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] --------------------------------------------------------------------
