[c-nsp] Growing BGP tables

[Brian Feeny]

There are alot of tools like that that would be interesting to have  
built in.
Or one that says "If this /24 has the same next-hop as a larger  
aggregate, drop the /24",
something like that would need to be buffered and pruned during the  
actual inbound route
updates.......It would be interesting to see how much memory could be  
conserved.  You would
not just be reducing BGP RIB, but RIB and FIB as well.

Brian


On Nov 22, 2004, at 1:44 PM, David J. Hughes wrote:

>
> Hi
>
> On 22/11/2004, at 10:36 PM, Gert Doering wrote:
>
>>
>> I agree with your reasoning.  Still, it might make sense today to  
>> change
>> from what was "the right thing" 10 years ago.
>
>
> Perhaps it's time we start pushing vendors to give us some tools to  
> solve this problem.  If we could have a test in a route-map that did  
> something like
>
> 	"Match this prefix if it's a /24 and we have an
> 	aggregate for it that's better than a /22"
>
> then we could sensibly drop the /24 pollution from those network  
> operators that just de-aggregate for the hell of it.  It would also  
> ensure that people who are using /24's properly would not be taken out  
> as collateral damage.
>
>
> David
> ...
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
------------------------------------------------------------------------ 
------
Brian Feeny, CCIE #8036, CISSP    	e: signal at shreve.net
Network Engineer           			p: 318.213.4709
ShreveNet Inc.             			f: 318.221.6612