[43434] in North American Network Operators' Group

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

RE: Filtering Best Practices, et al (Was Verio Peering, Gordon's

daemon@ATHENA.MIT.EDU (Hallgren, Michael)
Wed Oct 10 05:20:20 2001

Message-ID: <C5546A0E21D1D411867300902789DFA101F1BDCB@uklhxms01.Teleglobe.CA>
From: "Hallgren, Michael" <michael.hallgren@Teleglobe.com>
To: Stephane Bortzmeyer <bortzmeyer@gitoyen.net>
Cc: nanog@merit.edu
Date: Wed, 10 Oct 2001 10:22:09 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Errors-To: owner-nanog-outgoing@merit.edu


Hi,


we - Teleglobe, that is - filter our customers wrt. as-path and =
prefix...
also in the RIPE area. If a customer isn't up-to-date with IRR, we
advice/help him to become so. (The idea is, keeping filters on our =
customers
is also of benefit to our peers, etc, etc.)

mh

> -----Message d'origine-----
> De : Stephane Bortzmeyer [mailto:bortzmeyer@gitoyen.net]
> Envoy=E9 : mercredi 10 octobre 2001 10:54
> =C0 : Grant A. Kirkwood
> Cc : nanog@merit.edu
> Objet : Re: Filtering Best Practices, et al (Was Verio=20
> Peering, Gordon's
> Knot)
>=20
>=20
>=20
> On Tue, Oct 09, 2001 at 07:58:19AM -0700,
>  Grant A. Kirkwood <grant@virtical.net> wrote=20
>  a message of 18 lines which said:
>=20
> > I'm currently in the process of setting up a new border=20
> router, and the
> > recent debate on the above topic got me wondering what the=20
> best practice
> > filtering policy is? Is there one?
>=20
> I'm interested to see if people filter route anouncements on the =
basis
> of registered routes in an Internet Routing Registry. In our area
> (Europe), the RIPE database typically contains less than half of the
> routes which are actually announced. I assume it is not better in
> ARINland.
>=20
> On the basis of inetnum objects (network addresses, not routes), it =
is
> a bit better in coverage but you cannot use inetnum directly in a
> comparison, you have to check that a BGP announce *includes* at least
> one registered inetnum.
>=20
> To summary, I dropped the idea. Does anyone implemented it?
> =20
>=20
>=20

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