You just base it on statistics.

As you take in routes, you scan them against all previously taken in routes, and if an aggregate exists that shares the same next hop, you drop the current route.

Sure, if you took in routes from largest to smallest, you would be screwed and out of memory, but they will come in at different sizes, so you will hold a /24, and maybe 4000 routes later you will see that /24 is part of a /16 that is learned, so you drop the /24. You don't take the entire table in and then process it, you scan each route as it comes in against what has already come in.

Brian

On Nov 22, 2004, at 3:59 PM, Rodney Dunn wrote:

------------------------------------------------------------------------