Best way to deal with bad advertisements?
Avi Freedman
freedman at netaxs.com
Mon Sep 30 22:53:53 UTC 1996
> In message <199609281903.PAA06201 at 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
More information about the NANOG
mailing list