Re: More route-table bloat vs. ARIN micro-allocations

• From: Alex Rubenstein
• Date: Sat Feb 19 13:55:26 2000

> If people really started doing there part on cleaning up their announcements
> I bet we could reduce the total routes back down to some nice number........

Hello, John,

What is some 'nice' number? Are your routers suffering from the added
amount of routes?

(that's not rhetorical, but a true question; no disrespect meant).

I think that I'd rather see some additional routes in the BGP tree if it
meant smarter (as smart as smart can be in regards to BGP) routing
information.






> 
> 
> 
> 
> *> 63.84.242.192/26 166.48.176.25                        0 3561 14510 i
> *> 128.88.250.0/27  166.48.176.25                        0 3561 2516 2915 2915 2915 2915 151 i
> *> 128.88.250.32/29 166.48.176.25                        0 3561 2516 2915 2915 2915 2915 151 i
> *> 137.39.250.20/30 166.48.176.25                        0 3561 i
> *> 158.205.225.40/29 166.48.176.25                        0 3561 4694 ?
> *> 166.32.131.160/27 166.48.176.25                        0 3561 i
> *> 166.35.174.160/27 166.48.176.25                        0 3561 i                                    
> *> 206.98.105.48/28 166.48.176.25                        0 3561 4293 i
> *> 206.141.223.224/27 166.48.176.25                        0 3561 6081 7053 7053 7053 7053 i
> *> 206.142.63.0/28  166.48.176.25                        0 3561 i
> *> 206.151.223.0/26 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.64/28 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.80/28 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.96/27 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.128/27 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.160/28 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.180/30 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.184/30 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.188/30 166.48.176.25                        0 3561 4293 i
> *> 206.151.223.192/27 166.48.176.25                        0 3561 4293 i
> *> 206.152.253.0/27 166.48.176.25                        0 3561 4293 i
> *> 206.157.77.40/30 166.48.176.25                        0 3561 i
> *> 206.157.77.56/30 166.48.176.25                        0 3561 i
> *> 206.157.77.96/30 166.48.176.25                        0 3561 i
> *> 206.157.77.108/30 166.48.176.25                        0 3561 i
> *> 206.157.77.152/30 166.48.176.25                        0 3561 i
> *> 206.157.77.200/30 166.48.176.25                        0 3561 i
> *> 206.157.77.208/30 166.48.176.25                        0 3561 i
> *> 206.171.94.0/26  166.48.176.25                        0 3561 3549 13405 i
> *> 206.218.185.192/26 166.48.176.25                        0 3561 3549 i
> *> 207.49.17.192/28 166.48.176.25                        0 3561 4293 i
> *> 207.51.164.128/26 166.48.176.25                        0 3561 11192 i                              
> 
> 

• Follow-Ups:
  • Re: More route-table bloat vs. ARIN micro-allocations Randy Bush
  • Re: More route-table bloat vs. ARIN micro-allocations John M. Brown

• References:
  • More route-table bloat vs. ARIN micro-allocations John M. Brown

• Prev by Date: Re: Divergence Between NSI And Registry Database
• Next by Date: Re: More route-table bloat vs. ARIN micro-allocations
• Date Index
• Thread Index
• Author Index
• Historical