[36391] in North American Network Operators' Group
Re: AS Leakage
daemon@ATHENA.MIT.EDU (Christian Nielsen)
Wed Apr 4 13:04:29 2001
Date: Wed, 4 Apr 2001 09:59:05 -0700 (PDT)
From: Christian Nielsen <cnielsen@nielsen.net>
To: Travis Pugh <tpugh@shore.net>
Cc: Nanog mailing list <nanog@merit.edu>
In-Reply-To: <Pine.GSO.4.30.0104040746310.11106-100000@stonecoast>
Message-ID: <Pine.GSO.4.33.0104040953290.24185-100000@moench.nielsen.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, 4 Apr 2001, Travis Pugh wrote:
> I take transit from Qwest (209), and had to contact them directly and
> open a ticket several weeks ago to get them to stop leaking private
> ASNs into my tables. They stopped leaking them to me, but apparently
> going the extra step and making sure the leak was filtered everywhere
> was too much to ask.
I have a question. Why do you allow Private ASNs into your network? We saw
this once and put in the filters. Same with RFC1918 IPs and default. We
dont care to listen to these from other networks so we filter. We saw 64/8
in our network, we filtered. We saw leaks from RESERVED-IANA blocks, so we
filtered. We saw providers leaking exchange point blocks, so we filtered.
we dont want to see _701_ from sprint or anyone except _701_, so we
filter. we do this for other large providers.
See a problem, filter.
Maybe I should start a company and publish filters since most companies
seem not to have real filters in their network :(
Christian
