[4874] in North American Network Operators' Group
Re: Best way to deal with bad advertisements?
daemon@ATHENA.MIT.EDU (Avi Freedman)
Mon Sep 30 18:58:01 1996
From: Avi Freedman <freedman@netaxs.com>
To: curtis@ans.net
Date: Mon, 30 Sep 1996 18:53:53 -0400 (EDT)
Cc: freedman@netaxs.com, mpetach@netflight.com, nanog@merit.edu
In-Reply-To: <199609302015.QAA11829@brookfield.ans.net> from "Curtis Villamizar" at Sep 30, 96 04:15:23 pm
> 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
Yes, I overlooked this; ANS and Sprint would both not be affected by
bogus announcements; ANS in any space and Sprint in >= 205/8 space
(or wherever the Sean-filters start).
> 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.
Yes... My thinking was fuzzy, you are of course correct.
> Curtis
Avi
