[c-nsp] Growing BGP tables

[Rodney Dunn]

I'm not sure I can get this through.

For the record there were only two people
that attached cases to:

CSCsa45474
Externally found enhancement defect: New (N)
Ability to block overlapping BGP prefixes from being installed in RIB

What about if we just had a per neighbor filter that
would filter out more specific prefixes as they come in.
Once the more specific is filtered then it's gone until
you do a soft clear to get it back.
Something along these lines:

 router bgp 100
  address-family ipv4 unicast
  neighbor x.x.x.x leaked-specifics deny [inbound|outbound]


A lot of the fancy options are just not feasible currently.

Rodney


On Wed, Dec 01, 2004 at 05:51:17PM -0800, Randy Bush wrote:
> i proposed to rodney today, there are three types of prefix
> pollution.
>   o pure crap, such as that we see on top of the weekly
>     report
>   o someone traffic engineering
>   o legitimate holes (someone moving from at&t's 12/8)
> 
> a hardcore <bleep> such as i might just filter them all
> 
> a friendlier type might just dump longer prefixes if they
> had the same origin asn (the new part of the suggestion)
> 
> a southern californian might only dump a longer prefix
> if it has the same next hop as the covering prefix
> 
> randy
> 
> _______________________________________________
> 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/