[inet-ops] Prefix Pollution

[Joe Provo]

On Tue, Dec 14, 2004 at 06:45:57AM -0800, Randy Bush wrote:
[snip]
>     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

Part of 'what action should i take' also falls under 'what 
is least effort'.   MD pointed on that other list to the 
CAIDA Atoms work [http://www.caida.org/projects/routing/atoms/]
which is very cool, but requires one of
- non-realtime offline processing [boo]
- vendors to incorporate their own proprietary and buggy code
  to do the same thing [in a glacial epoch]
- people to junk vendors and solder their own interface boards
  in the garage [didn't we do that before?]

...so many times the analysis comes back to "accept everything 
and only react to outside-influence-of-the-moment" or "follow
allocation guidelines for a baseline filter and adjust as 
business needs dictate". 

Does either approach nescessarily lead to better stability and 
goodput? I have my opinions based on my experiences, but am not 
so full of hubris to think mine is the only point of view that 
counts.  A HUGE portion of my poking-the-stick into this nest 
isa to see if there are hornets in it ["yes this is still 'an 
issue' and somehow we were collectively asleep at the wheel of 
the DFZ"] or not ["no, the general consensus is that if you 
haven't upgraded in the last X years, and can't budget for 
unpredicatble growth, then get out of the game"].

Joe, setting religion on the shelf for a bit to get data

-- 
             RSUC / GweepNet / Spunk / FnB / Usenix / SAGE