[48436] in North American Network Operators' Group

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

RE: Bogon list

daemon@ATHENA.MIT.EDU (Barry Raveendran Greene)
Tue Jun 4 16:36:30 2002

From: "Barry Raveendran Greene" <bgreene@cisco.com>
To: "Richard A Steenbergen" <ras@e-gerbil.net>,
	"David McGaugh" <david_mcgaugh@eli.net>
Cc: "Joe Abley" <jabley@automagic.org>,
	"Rob Thomas" <robt@cymru.com>, "NANOG" <nanog@merit.edu>
Date: Tue, 4 Jun 2002 13:33:43 -0700
In-Reply-To: <20020604194700.GZ12164@overlord.e-gerbil.net>
Errors-To: owner-nanog-outgoing@merit.edu




> On Tue, Jun 04, 2002 at 11:04:40AM -0700, David McGaugh wrote:
> > I agree with Joe on this. At one time we were filtering 198.32/16 from
> > our peers but ran into things like ep.net (198.32.6.31) breaking. We now
> > only filter on IXP blocks for which we participate.
> >
> > While on the subject of IXP blocks, we also ended up redistributing the
> > IXP blocks and sending them to our BGP customers (who do not receive a
> > default) so that traceroutes and such from Looking Glasses do not break.
> > They can then choose to filter them as they wish.
>
> Exchange point blocks SHOULDN'T be transited by anyone, therefore you
> should not hear them from your peers.

Agreed. But these are the IXP micro allocations - not "bogons." How you
filter the IXP blocks depends on each ISP and the IXP contracts. So that
would be something you would add to Rob's template.


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