[db-wg] Geolocation data prototype in the RIPE Database

Hi.

I was one of the persons really against this at the RIPE 62 and I still
am.

How can I as a LIR avoid being forced by my customers to modify this
data? How can the end user easily modify this themselves without the LIR
being involved at all?
What if the country says UK in the inetnum but the geoloc data is
somewhere in France? 
What if Geoloc data providers used by content providers starts using the
geoloc data in the inetnum. Can it not be manipulated then to allow
content to be seen outside laws and regulation?

I certainly don't want to be pressured from content providers to remove
manipulated geoloc data. 

I just don't think RIPE dB is the place to solve the issues for content
providers etc.

Rgds

Patrick Arkley
Verizon Europe

-----Original Message-----
From: db-wg-bounces at ripe.net [mailto:db-wg-bounces at ripe.net] On Behalf
Of Denis Walker
Sent: den 5 oktober 2011 15:29
To: Database WG
Subject: [db-wg] Geolocation data prototype in the RIPE Database

Dear colleagues,

At the RIPE 62 Meeting in Amsterdam the RIPE NCC Database Group was
asked to investigate handling geolocation data in the RIPE Database. We
now have a proof of concept prototype for discussion by the community.

Based on input from a number of community sources and the subsequent
presentation at RIPE 62, this prototype has two new optional attributes
for storing geolocation data and language details.

We have written an article about the design approach on RIPE Labs
https://labs.ripe.net/Members/denis/geolocation-prototype-for-ripe-datab
ase

This prototype references a sand-boxed TEST Database and does not have
any pre-loaded geolocation or language data. But you can create your own
data to see how easy it is to manage this new, optional information. We
also have a prototype Geolocation Finder tool to search for this data.

Another article on RIPE Labs shows how to create the new optional
attributes and use the Geolocation Finder tool to search for this data.
No changes in this sand-boxed TEST Database will affect the production
RIPE or TEST Database services.

The article is available at:
https://labs.ripe.net/Members/denis/example-usage-of-ripe-database-geolo
cation-prototype

We invite comments or feedback on this design and suggestions for how to
move forward if it is seen as a useful addition to the RIPE Database by
the community.

Regards

Denis Walker
Business Analyst
RIPE NCC Database Group





Verizon Sweden AB  - registrerat i Sverige med organisationsnummer 556489-1009- huvudkontorets adress: Armegatan 38, Box 4127, 171 04 Solna, Sverige