On Aug 5, 2008, at 3:26 PM, Tim Sanderson wrote:
Ya sure, like any of us would admit to 50% clue-ness.
With all the posts here about bogons I would really be surprised
that any nanog readers didn't know about keeping bogons updated.
I'd be shocked it there were no people who read NANOG and
misunderstood or blatantly ignored some of it.
Unfortunately, that means they would ignore / misunderstand the OP's
request. But there is probably a small percentage clueless enough to
have stale bogon filters, but just clueful enough to realize what the
OP said might apply to them. A very small percentage....
Switching topics only slightly: Nick, do you have any data on what
parts of the 'Net you can and cannot reach? Perhaps take a dump of
route-views and ping some IPs in each ASN? Shouldn't be hard to
script, and might yield useful data - both to you and the rest of us.
--
TTFN,
patrick
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 05, 2008 2:15 PM
To: Nick Downey
Cc: nanog@nanog.org
Subject: Re: Out of Date Bogon Prefix
On Tue, 05 Aug 2008 12:16:53 CDT, Nick Downey said:
This is an heads-up from the Mediacom Network Operations Center
about an
issue we are seeing. We
were recently given an IP scope from ARIN (American Registry for
Internet
Numbers) that still
exists on older Bogon lists many web providers are currently using.
Out of curiosity - what percentage of connectivity providers are
both clued enough to be represented on NANOG and yet unclued enough
to not understand the need to keep bogon filters up to date (even if
you just get a BGP feed from Team Cymru)?
(By the way, Nick - if what you sent NANOG was a form letter
template, I'd lose a lot of the RFC references and point at Team
Cymru's stuff instead)...
