[ncc-services-wg] Personal Data and Database Proxy services

On Thu, Jan 03, 2013 at 01:53:27PM +0200, Andrey Semenchuk wrote:
>"Person" object intended to identify employer of the organisation 
>that holds objects in the RIPE database (aut-num, domain, inet-num, 
>etc). In this case the phone int person object is not the personal 
>phone but the phone provided by employer. It's the service phone that 
>should not indentify the person. If someone puts there his/her 
>private phone - it's not the RIPE database problem - maybe this 
>person consider it's private life (or part ot it) as an public 
>information. In any case this phone publication - is the decision of 
>the person and RIPE (even if this information is public and has none 
>limitations of access) provides access to the data in compliance with 
>the person's intentions,

Individuals hold IP space and other resources. Actually, in that case,
even the organisation: object must be considered personal data as it
usually even contains physical address information. 

>If the person wished to provide free access to his/her personal data 
>- RIPE should provide this access without any limitation. All data 
>protection RIPE should provide - is a storage protection. If the 
>person wishes to provide this information to RIPE only - no personal 
>data should be displayed to any other third party. It's so simple! 

That leaves the issue of masking this data from whois - no idea whether
this is technically even possible.

Regards,
Sascha Luck