[176591] in North American Network Operators' Group
Re: determine relationship between the operators based on import and
daemon@ATHENA.MIT.EDU (Martin T)
Fri Dec 5 02:32:49 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <20141125.165805.515784595415975214.ww@styx.org>
Date: Fri, 5 Dec 2014 09:32:41 +0200
From: Martin T <m4rtntns@gmail.com>
To: ww@styx.org
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
Hi,
thanks! I guess one of the most exhaustive and freely-available
route-views data to analyze is from RIPE Routing Information Service
project? For example if I would like to analyze a certain prefix
announced by a certain AS for time period from 1.11.2014 to
30.11.2014, then I should download route-views data for this
period(for rrc_id in {00..14}; do for d in {01..30}; do wget
http://data.ris.ripe.net/rrc"$rrc_id"/2014.11/bview.201411"$d".0800.gz;
done; done) and anayze this with bgpdump(bgpdump -m bview* | grep -w
65133)? Other option would be to use one of the tools like RIPEstat
BGPlay?
thanks,
Martin
On 11/25/14, William Waites <ww@styx.org> wrote:
> On Tue, 25 Nov 2014 17:36:47 +0200, Martin T <m4rtntns@gmail.com> said:
>
> > Last but not least, maybe there is altogether a more reliable
> > way to understand the relationship between the operators than
> > aut-num objects(often not updated) in RIR database?
>
> The first thing to do is look and see if the policy of, e.g. AS65133
> is consistent with what you see there. I suspect you'll find a lot of
> mismatches but I don't know if that has been studied systematically,
> but it should be simple to do.
>
> Next, much more data intensive, is trawl through the route views data
> and see to what extent the actual updates seen are consistent with the
> RIR objects, and also see what (topological, not financial as Valdis
> points out) relationships they imply that are not present in the RIR
> database.
>
> -w
>
