[181732] in North American Network Operators' Group

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

Re: Route leak in Bangladesh

daemon@ATHENA.MIT.EDU (Nick Hilliard)
Wed Jul 1 12:10:17 2015

X-Original-To: nanog@nanog.org
X-Envelope-To: nanog@nanog.org
To: Joe Abley <jabley@hopcount.ca>, Jared Mauch <jared@puck.Nether.net>
From: Nick Hilliard <nick@foobar.org>
Date: Wed, 1 Jul 2015 17:08:01 +0100
In-Reply-To: <7EC6EFE3-2C79-4E7C-899B-FA207975F4FE@hopcount.ca>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 01/07/2015 17:03, Joe Abley wrote:
> The idea of configuring this stuff from the IRR is great in terms of
> distributing the ops cycles in the right places, but it doesn't help with
> verifying that the end result isn't insane, as I think you and Mike have
> described on this list over the past couple of days.

that doesn't invalidate it as being part of a critical mechanism for
filtering ebgp.  Implemented well, it will catch 99% of problems.
maxprefixes with no autorecover catches 75% of the rest.  Between these two
mechanisms, that's pretty good.

Nick


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