I oppose wholesale filtering by allocation size policy as an acceptable metric for reducing your RIB. <br><br>There are legitimate reasons to announce only /24s within a /21 or /22 PI allocation, for example. Perhaps an org has diverse networks in multiple cities and doesn't want to be beholden to upstream PA space. One may argue, "build a proper network, noob," but there may not be a business case for sufficient interconnect between sites to have a consistent origin AS.
<br><br>If one could filter in such a way that one only aggregated prefixes
back to their allocated size when the AS path (or even origin AS) is
the same, then you won't be breaking anyone, and will put the kibosh on
the noobs who deagg for no good reason (but no vendor is giving us a
'filter-stupid' knob yet).<br><br>Filtering/aggregating outside your local RIR seems like a better plan to me (for some networks, anyway). You're a whole lot less likely to have a bad/missing path, and you still have sufficient knobs to engineer most outbound flows.
<br><br>-Kevin Blackham<br> (recently moved from provider to end network using non-XL PFC)<br><br><div><span class="gmail_quote">On 9/10/07, <b class="gmail_sendername">Stephen Sprunk</b> <<a href="mailto:email@example.com">
firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Thus spake "Kevin Loch" <<a href="mailto:email@example.com">
firstname.lastname@example.org</a>><br>> Stephen Sprunk wrote:<br>>> Sucks to be them. If they do not have enough PA space to meet<br>>> the RIR minima, the community has decided they're not "worthy"<br>>> of a slot in the DFZ by denying them PI space.
<br>><br>> Not true, there is an ARIN policy that allows you to get a /24 from<br>> one of your providers even if you only need 1 IP address:<br>><br>> NPRM <a href="http://184.108.40.206">220.127.116.11</a><br>><br>> "This policy allows a downstream customer's multihoming
<br>> requirement to serve as justification for a /24 reassignment from<br>> their upstream ISP, regardless of host requirements."<br>><br>> <a href="http://www.arin.net/policy/nrpm.html">http://www.arin.net/policy/nrpm.html
</a><br><br>If the PA /24 is under 199/8 or 204-207/8, then the filters being discussed<br>would allow their advertisement through, because ARIN's minimum allocation<br>for those blocks is /24. In ARIN's 22 other /8s, the filters would not
<br>because the minimum is /20 (or /22, for 208/8).<br><br>Let's also keep in mind that if other folks block a PA more-specific, the<br>site doesn't lose connectivity unless they lose their upstream connection to<br>
the LIR that assigned them the block. I suspect that many of them already<br>see that behavior today, at least partially; we're really discussing making<br>it a near-complete outage versus a semi-outage. That's life if you don't
<br>qualify for a real routing slot via PI.<br><br>S<br><br>Stephen Sprunk "God does not play dice." --Albert Einstein<br>CCIE #3723 "God is an inveterate gambler, and He throws the<br>K5SSS dice at every possible opportunity." --Stephen Hawking