Could riswhois generate statistics of "parent routes" for given route?
[ parent, not ancestor]
My goal is achieve better coverage of IP->AS mappings based on riswhois
provided data. Unanimous AS reports (after ignoring default route) give very
good starting point I would like to extend.
For 65.54.160.0/19 I would like to know how many of 58 rispeers reporting
the route reports also 65.52.0.0/14 route as belonging to AS8070.
e.g.
route: 65.54.160.0/19
origin: AS12076
[...]
num-rispeers: 58
numrp-parent: 58 65.54.160.0/19 AS8070
P.S. As security precaution riwhois may limit number of parent routes
reported to e.g. <10
----------------------------------------------------------
$whois -h riswhois.ripe.net -- 65.54.162.200
[leading comments and default route entry skipped]
route: 65.52.0.0/14
origin: AS8070
descr: MICROSOFT-CORP---MSN-AS-BLOCK - Microsoft Corp
lastupd-frst: 2005-07-21 08:28Z 202.12.28.190@rrc00
lastupd-last: 2005-09-05 07:49Z 193.111.172.55@rrc03
seen-at:
rrc00,rrc01,rrc03,rrc04,rrc05,rrc06,rrc07,rrc10,rrc11,rrc12,rrc13,rrc14
num-rispeers: 58
source: RISWHOIS
route: 65.54.160.0/19
origin: AS12076
descr: HOTMAIL-AS - Hotmail Corporation
lastupd-frst: 2005-06-29 08:05Z 195.66.224.151@rrc01
lastupd-last: 2005-09-05 07:49Z 193.111.172.55@rrc03
seen-at:
rrc00,rrc01,rrc03,rrc04,rrc05,rrc06,rrc07,rrc10,rrc11,rrc12,rrc13,rrc14
num-rispeers: 58
source: RISWHOIS
----------------------------------------------------------
--
Andrzej [en:Andrew] Adam Filip anfi(a)priv.onet.pl anfi(a)xl.wp.pl
All that is necessary for the triumph of evil is that good men do nothing
-- Edmund Burke (1729-1797)
>> I would like to create "simple" tool for IP->AS mapping based on riswhois
>> data.
> i do not believe whois data have anything about as numbers
RISwhois is a whois interface to the RIS data, intended to provide
a quick look at the collected BGP data. Format is compatible with routing
registries so folk who have tools build on whois queries to IRR, can switch
to RIS transparently. Useful for IP->AS mappings, but also for a first peek at
BGP tables before diving deeper with other RIS tools (looking glass, prefix
query etc.)
See http://www.ripe.net/ripe/meetings/ripe-47/presentations/ripe47-eof-riswhois…
As for the question:
>> Are there any good reasons to keep riswhois reporting default routes?
I think riswhois server should not do any filtering on the RIS data
If someone feeds RIS a default route, it should pop up in the
RRC looking glass, the RIS database and RISwhois. It's up to the
application to use it or ignore it.
If you don't want the currently present default route to appear
in ever riswhois query, use the -M flag:
whois -h riswhois.ripe.net -M <ip-number>
will only return you the longest matching prefix.
-- Rene
IMHO ris databases (or at least riswhois server) should simply ignore
default route (0.0.0.0/0).
Are there any good reasons to keep riswhois reporting default routes?
<quote>
% This is RIPE NCC's Routing Information Service
% whois gateway to collected BGP Routing Tables
% IPv4 or IPv6 address to origin prefix match
%
% For more information visit http://www.ripe.net/ris/riswhois.html
route: 0.0.0.0/0
origin: AS9009
descr: REALROUTE-AS RealROUTE International Network
lastupd-frst: 2005-08-13 23:34Z 195.69.144.63@rrc03
lastupd-last: 2005-08-13 23:34Z 195.69.144.63@rrc03
seen-at: rrc03
num-rispeers: 1
source: RISWHOIS
</quote>
--
Andrzej [en:Andrew] Adam Filip anfi(a)priv.onet.pl anfi(a)xl.wp.pl
All that is necessary for the triumph of evil is that good men do nothing
-- Edmund Burke (1729-1797)
