North American Network Operators Group|
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical
Re: Route table growth and hardware limits...talk to the filter
Thus spake "Forrest" <[email protected]>
With the option of filtering on the RIR minimums, I'm not terribly worried about breaking connectivity to the people announcing all /24s instead of their /19. Broken connectivity for them is probably the only way they will ever look at cleaning up their announcements. The organizations that are hurt unnecessarily by filtering on the RIR minimums are the ones multi-homing with smaller PA space
Sucks to be them. If they do not have enough PA space to meet the RIR minima, the community has decided they're not "worthy" of a slot in the DFZ by denying them PI space. OTOH, most providers are happy to give out as much PA space as you need, as long as you pay for it. If you only have a /25 today and you need a /24 for your PA route to be heard, call your upstream's sales droid and request a /24.
or announcing a few more specifics here and there for traffic engineering.
Such folks would lose the effects of their TE, if their TE routes are longer than RIR minima, but not connectivity in general. Also, TE is only useful a few AS hops away, so the filter being discussed could be combined with another solution being proposed to allow longer-than-RIR-minima routes with a short AS PATH.
Stephen Sprunk "God does not play dice." --Albert Einstein
CCIE #3723 "God is an inveterate gambler, and He throws the
K5SSS dice at every possible opportunity." --Stephen Hawking