[170853] in North American Network Operators' Group
Re: BGPMON Alert Questions
daemon@ATHENA.MIT.EDU (Tony Tauber)
Thu Apr 10 17:26:22 2014
In-Reply-To: <201404101526.54008.mark.tinka@seacom.mu>
Date: Thu, 10 Apr 2014 17:25:51 -0400
From: Tony Tauber <ttauber@1-4-5.net>
To: mark.tinka@seacom.mu
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Apr 10, 2014 at 9:26 AM, Mark Tinka <mark.tinka@seacom.mu> wrote:
> On Thursday, April 10, 2014 12:30:51 PM Randy Bush wrote:
>
> > as folk start to roll out rejection of invalids, we might
> > think about how we report problems with folk registering
> > inadequate roas, covering their customers, covering
> > their deaggs (maybe deaggs get what they deserve), etc.
> > if they are not clued enough to generate prudent roas,
> > they will not be clued enough to generate ghostbusters
> > (and neither ripe's nor apnic's software supports gbrs
> > today).
>
> <snip>
> It would be useful to use BGPmon's free RPKI validation
> feature, which e-mails you, incessantly, about validation
> failures due to un-ROA'd de-aggregates.
>
This seems like good idea and would also be good to know how else to know
"I've broken something.".
There's a BGP Visibility Project http://visibility.it.uc3m.es/
which perhaps could be brought to bear.
Other thoughts out there?
Tony
