[4867] in North American Network Operators' Group
Re: Best way to deal with bad advertisements?
daemon@ATHENA.MIT.EDU (Curtis Villamizar)
Mon Sep 30 16:28:56 1996
To: Avi Freedman <freedman@netaxs.com>
cc: mpetach@netflight.com (Matthew Petach), nanog@merit.edu
Reply-To: curtis@ans.net
In-reply-to: Your message of "Sat, 28 Sep 1996 15:03:31 EDT."
<199609281903.PAA06201@netaxs.com>
Date: Mon, 30 Sep 1996 16:15:23 -0400
From: Curtis Villamizar <curtis@ans.net>
In message <199609281903.PAA06201@netaxs.com>, Avi Freedman writes:
> >
> > > 1) Announce *your own* routes more specifically.
> > > This may lose you ANS connectivity, though.
>
> I meant ANS connectivity because of RADB issues, but yes,
> anyone who filters small announcements in your space won't
> see you.
Avi,
If there is a route object in the RADB for the /24 we will set policy
according to the origin AS of the RO. If you can't get rid of a bogus
RADB RO, ask us we can create exceptions for AS based policy on a per
prefix basis. If there is no RO, we won't listen to the /24 so we
won't hear the bogon, just the /16. This is temporarily moot since we
have 2 routers in AS1673 that can't handle the policy filters.
The bottom line is the IRR helps keep connectivity in the face of this
sort of problem where you are claiming it hurts.
Curtis
