Re: IS-IS reference

I think the right plan of action should be: a) design numbering plan allowing aggregation on per-location basis; b) design a dynamically-routed redundant backbone and c) attach tree-like access networks to the backbobne. The backbone should not take _any_ routing information from the leaf networks. It would also help to keep strict access controls, and separate backbone routers from leaf access routers, so only the authorized backbone engineers can change things in those. Leaf networks should do static routing, and no proxy ARP. This way any damage from badly behaving hosts or apps is limited to the segment they're on. And don't do multicasting. May be we should start defensive networking classes? :) --vadim