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

On 10/07/11 07:01, Dennis Yusupoff wrote:
> 06.10.2011 13:20, Hendrik T. Voelker пишет:
>> There are other aspects as well. There are for sure lots of people out
>> there who do NOT want their IP address geolocated. And then there are
>> different privacy regulation in every country which have to be observed.
>>
>> Also depending on the internal routing of the IP address possessor,
>> the real location can vary heavily and the whole network is not
>> necessarily used completely at the same location. In the end you'd
>> have to attach a current location to every single address ...
>>
>> If anybody should submit the current location it is the end user alone.
> It's all true only in case of publishing precise location - up to meters
> (in form of coordinates, of cause). But no one insist on such accuracy -
> you can give a rough coordinates with only accuracy up to street or even
> city.

We have a lot of Allocations that are split up and used in different countries 
and in that country in different cities. So beside that administrative 
nightmare this will cause it also will require a LOT of additional entries in 
the RIPE db. So the best accuracy of location we can give them is EMEA. And 
that is already implied with the addresses being allocated from the RIPE ...

And I didn't even mention mobile (smart)phones yet ...

The RIPE db is the wrong place for this kind of information.

Cheers

Hendrik

-- 
Hendrik Voelker      Server & Services Management     EMEA Server Operations
Verizon Deutschland GmbH      Sebrathweg 20     D-44149 Dortmund     GERMANY
http://www.verizonbusiness.com/de/ tel +49-231-972-1565 fax +49-231-972-2587
PubKey   1024D/92479A5D   EC1B 76F2 D69D 11C6 2611  5CD1 5269 9351 9247 9A5D


Verizon Deutschland GmbH - Sebrathweg 20, 44149 Dortmund, Germany - Amtsgericht Dortmund, HRB 14952 - Geschäftsführer: Detlef Eppig - Vorsitzender des Aufsichtsrats: Dominique Gaillard