[106572] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Out of Date Bogon Prefix

daemon@ATHENA.MIT.EDU (Tim Sanderson)
Tue Aug 5 15:27:13 2008

From: Tim Sanderson <tims@donet.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Tue, 5 Aug 2008 15:26:57 -0400
In-Reply-To: <20009.1217960096@turing-police.cc.vt.edu>
Errors-To: nanog-bounces@nanog.org

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 n=
anog readers didn't know about keeping bogons updated.

--
Tim Sanderson, network administrator
tims@donet.com

-----Original Message-----
From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]
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)..=
.


home help back first fref pref prev next nref lref last post