[84707] in North American Network Operators' Group

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

Re: [afnog] ARIN to allocate from 74/8 & 75/8

daemon@ATHENA.MIT.EDU (Alexander Koch)
Wed Sep 21 01:40:43 2005

Date: Wed, 21 Sep 2005 07:37:40 +0200
From: Alexander Koch <koch@tiscali.net>
To: Todd Underwood <todd@renesys.com>
Cc: Randy Bush <randy@psg.com>, Leslie Nobile <leslien@arin.net>,
	nanog@merit.edu, inet-ops@puck.nether.net, uknof@ukif.org.uk,
	afnog@afnog.org, nznog@list.waikato.ac.nz, eof-list@ripe.net,
	sanog@sanog.org
Reply-To: nanog@merit.edu
In-Reply-To: <20050920204920.GH5285@renesys.com>
Errors-To: owner-nanog@merit.edu


Todd,

On Tue, 20 September 2005 16:49:20 -0400, Todd Underwood wrote:
[..]
> look in the routing tables of routeviews/ripe/cymru/renesys peers?

Speaking of experience there is a difference potentially
between rfc1918/bogus/unallocated filters on an interface
that likely do reference a prefix list (no le/ge on
Junipers) - and a policy that handles BGP announcements.

It surely can happen (and did happen) that the BGP
announcements itself made it just fine while the filters on
the customer/ peer links where not at all updated yet (if
they filter BGP announcements for unallocated at all, etc).

Much less people filter BGP that hard, if at all, for
unallocated/ bogus, but rather keep the firewall policies
clean.

Alexander


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