[tor-bugs] #26585 [Metrics/Onionoo]: improve AS number and name coverage (switch maxmind to RIPE Stat)

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Jul 1 15:04:20 UTC 2018


#26585: improve AS number and name coverage (switch maxmind to RIPE Stat)
-----------------------------+------------------------------
 Reporter:  nusenu           |          Owner:  metrics-team
     Type:  enhancement      |         Status:  new
 Priority:  Medium           |      Milestone:
Component:  Metrics/Onionoo  |        Version:
 Severity:  Normal           |     Resolution:
 Keywords:                   |  Actual Points:
Parent ID:                   |         Points:
 Reviewer:                   |        Sponsor:
-----------------------------+------------------------------
Changes (by cypherpunks):

 * keywords:  metrics-geoip =>


Comment:

 Replying to [comment:1 irl]:
 > For country codes

 This ticket is about AS data (number and name).

 (RIPEstat uses maxmind itself, so it does not make much sense to use
 RIPEstat for geolocation
 to replace maxmind?)
 https://stat.ripe.net/docs/data_api#Geoloc


 > 2 relays for which RIPEstat did not return an AS number

 when posting numbers, please include specific APIs used and with what
 parameters (as some RIPEstat APIs filter prefixes with low visibility by
 default)


 > It is not clear to me what our threshold on agreement should be. As the
 MaxMind database is distributed to users and can be used, for example, to
 disable/prefer the use of exit relays in specific countries,

 onionoo data is not directly used by tor client daemons in any way (or to
 disable specific exits)


 > We should conduct an analysis of the different databases and feeds
 available to us, to determine which best fits our requirements.

 what are the specific onionoo requirements?


 > As for querying RIPEstat, I have [[https://github.com/britram/canid|a
 tool]] which I have used in the above analysis

 Note, that canid does not use the specific APIs listed in the first post
 of this ticket according to their README on github.


 > I don't believe we should consider outright replacing MaxMind with
 RIPEstat for the reason that we distribute this to end clients

 what is a 'end client' in the onionoo context? is RS an end client?


 > to make it clear to users where the information has come from if that is
 important to them.

 transparency is always positive

 This ticket is the preparation to add BGP ROA enums in the future.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26585#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list