[163006] in North American Network Operators' Group
Re: The BGP Visibility Scanner
daemon@ATHENA.MIT.EDU (Jason Hellenthal)
Wed May 15 09:01:17 2013
In-Reply-To: <519361D2.8040508@imdea.org>
From: Jason Hellenthal <jhellenthal@dataix.net>
Date: Wed, 15 May 2013 09:00:53 -0400
To: Andra Lutu <andra.lutu@imdea.org>
Cc: Olaf Maennel <O.M.Maennel@lboro.ac.uk>, "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Pretty nice. Thanks!
I don't suppose there is any straight text version of all this info is there=
?
--=20
Jason Hellenthal
IS&T Services Professional
Inbox: jhellenthal@DataIX.net
JJH48-ARIN
On May 15, 2013, at 6:22, Andra Lutu <andra.lutu@imdea.org> wrote:
> Dear all,
>=20
> We have built a tool that checks the visibility of IPv4 prefixes at the in=
terdomain level.
> The tool is available at *http://visibility.it.uc3m.es/* and you can use i=
t to retrieve the Limited Visibility Prefixes (LVPs) (i.e., prefixes that ar=
e not present in all the global routing tables we analyse) injected by a cer=
tain originating AS.
> The query is very simple, it just requires to input the AS number for whic=
h you want to retrieve the originated LVPs, if any.
> After checking the limited-visibility prefixes, we would appreciate any fe=
edback that you can provide on the cause of the limited visibility (we provi=
de a form with a few very short questions which you could fill in and submit=
).
>=20
> Using a dataset from May 2nd 2013, we generated a list with the ASes which=
are originating LVPs: *http://visibility.it.uc3m.es/fullASlist.html*
> We would like to hear from any operator who might find this project intere=
sting, and, in particular, from these large contributors to the LVPs set.
> Please note that advertising prefixes with limited visibility does not mea=
n that the originating AS is necessarily doing something wrong.
> The ASes might be generating the LVPs knowingly (e.g., scoped advertisemen=
ts). However, there might be cases where the origin AS might be unaware that=
some prefixes are not globally visible (when they should) or that others ar=
e leaking as a consequence of mis-configurations/slips.
>=20
> Our purpose is to spread awareness about these latter phenomena, help elim=
inate the cause of unintended/accidental LVPs and upgrade this tool to an an=
omaly detection mechanism.
> For more information on the definition and characteristics of a Limited Vi=
sibility prefix, please check the Frequently Asked Questions section of the w=
ebpage, available here: *http://visibility.it.uc3m.es/Q_and_A_latest.html*
>=20
> The tool works with publicly available BGP routing data, retrieved from th=
e RIPE NCC RIS and RouteViews Projects. The results are updated on a daily b=
asis.
> For more information on the methodology we refer you to the slides of the N=
ANOG57 presentation about the BGP Visibility Scanner:
> http://www.nanog.org/meetings/nanog57/presentations/Wednesday/wed.general.=
Lutu.BGP_visibility_scanner.19.pdf
> Also, you can check the RIPE labs article about the BGP Visibility Scanner=
, available here: https://labs.ripe.net/Members/andra_lutu/the-bgp-visibilit=
y-scanner
>=20
> We are looking forward to your feedback!
>=20
> Thank you, best regards,
> Andra
