[db-wg] Geolocation in the RIPE Database

On 2016-05-25 20:25, Job Snijders wrote:
> Hi wilfried,
> 
> Would you be willing to work with the chairs to formulate a problem statement and follow the NWI process?

Sure :-)

I guess it would be reasonably easy, along the following lines:

- functionality was introduced to "test the waters"

- it never became obvious how to maintain it or which party would actually be
  allowed or mandated to manage the entries

- whatever rudimentary functionality there was/is, it is not helping the "victims",
  ie. the end users

- geo-location is better (but not nearly good![1]) maintained by entities like maxmind

- geo-location is pretty far out from the mandate of the Resource Registry

- there was never a common understanding, how to deal with assignments within
  an LIR with global or at least continental or regional coverage

- we never had any sense of applicable granularity of longitude/latitude or
  national boundaries

- we never got useful feedback on the usefulness or "consumer processes" for
  this particular dataset

- all of that related to the 1st entry in this list :-)

Wilfried

[1] the RIPE Meeting Network here in Copenhagen is still considered to be located
    in Romania, with all the ill-advised side effects...

> Job
> 
>   Original Message  
> From: Wilfried Woeber
> Sent: woensdag 25 mei 2016 20:08
> To: Tim Bruijnzeels; Database WG
> Subject: Re: [db-wg] Geolocation in the RIPE Database
> 
> 
> Hi Tim, DB-WG community!
> 
> On 2016-05-25 19:51, Tim Bruijnzeels wrote:
>> Dear working group,
>>
>> We have an update with regards to the following action point:
>> AP69.3 [RIPE NCC] To examine and report on possible solutions to improving geolocation
>> data in the RIPE DB (Ongoing but if no progress by RIPE 72 then kill it)
>>
>> Following a decision by the RIPE NCC Executive Board not to support resource expenditure
>> in the area of geolocation services, the RIPE NCC has no plans to examine this further.
> 
> I can easily relate to this decision and can easily "accept" it.
> 
> But as a consequence, I'd like to propose to *discontinue* all geo-location
> related functionality in the Resource Registry as soon as possible.
> 
> Regards,
> Wilfried 
> 
>> A write-up is published on our website:
>> https://www.ripe.net/manage-ips-and-asns/db/tools/geolocation-in-the-ripe-database
>>
>> Kind regards,
>>
>> Tim Bruijnzeels
>>
>> Assistant Manager Software Engineering
>> RIPE NCC Database Group
> 
> 
>