[atlas] Atlas Anchor contact role accidentally cleaned (Was: Clean-up of unreferenced objects in the RIPE Database)

Hi Colin,

This PERSON object was locked because it was unmaintained.

We cannot, as a matter of principle, unlock unmaintained person objects: this can introduce a risk that we are liable for hijack of these objects by people other than their original owner - who can then change details while people referencing this object are unaware.

To get around this please just create a new PERSON object instead, and ask people referencing CJ570-RIPE to update their reference. Once all references are removed the old object will be cleaned up automatically (after 90 days).

If the maintainers of objects are unwilling to remove their references to CJ570-RIPE, then we do have a process in place that you can use to ask us to delete the object for you: https://www.ripe.net/manage-ips-and-asns/db/support/documentation/removal-of-personal-data

I am sorry that this is somewhat formal, but considering the liabilities that can follow from not doing this properly, I see no other option than to ask you to go through this.

Kind regards,

Tim Bruijnzeels



> On 03 Nov 2016, at 16:05, Colin Johnston <colinj at mx5.org.uk> wrote:
> 
> Hi Tim, on the subject of ripe contact role object info update
> How do I update update my role object for the phone number when a locked object ?
> 	• nic-hdl:         CJ570-RIPE
> 	• created:         2006-09-18T14:37:05Z
> 	• last-modified:   2016-04-07T07:05:31Z
> 	• mnt-by:          RIPE-NCC-LOCKED-MNT
> 	• source:          RIPE
> 
> 
> Colin
> 
>> On 3 Nov 2016, at 14:42, Tim Bruijnzeels <tim at ripe.net> wrote:
>> 
>> Hi Ondřej
>> 
>> To be fair we did not consider this use case in our implementation. However, as a quick fix: you can recreate your objects and they will not be deleted for the next 90 days.
>> 
>> In the meantime I want to take the opportunity to review the process for preventing deletion of objects. There (still) is an official process for this, but as you can see it's somewhat more complicated than it needs to be - at least imho:
>> https://www.ripe.net/manage-ips-and-asns/db/support/documentation/white-pages/view
>> 
>> So, I would suggest that you actually don't try to follow that procedure for the time being, and I can keep you posted on the developments. I am confident that we can work something out with 90 days - but although I have an alternative in mind I will need to discuss it with various parties - including probably the db-wg before we can implement.
>> 
>> I hope this helps. Kind regards,
>> 
>> Tim Bruijnzeels
>> 
>> 
>> 
>> 
>> 
>> 
>>> On 02 Nov 2016, at 15:18, Ondřej Caletka <Ondrej.Caletka at cesnet.cz> wrote:
>>> 
>>> Dne 6.9.2016 v 15:32 Tim Bruijnzeels napsal(a):
>>>> Dear colleagues,
>>>> 
>>>> In compliance with data protection rules and the desire to maintain a “clean” database, we plan to remove unreferenced objects from the RIPE Database. We have recently been working on an improved implementation, and we are now ready to re-start the process.
>>>> 
>>>> In order to be eligible for deletion, objects must have no incoming references (or be a person-maintainer or role-maintainer pair) and must have had no incoming references from any aut-num, domain, inet(6)num, route(6), as-set, filter-set, inet-rtr, peering-set, route-set, rtr-set, as-block, key-cert or irt object during the last 90 days.
>>> 
>>> Hello Tim, hello RIPE Atlas team,
>>> 
>>> I just found out that my RIPE Atlas Anchor contact role object CAAO-RIPE
>>> has been cleaned from the RIPE database. This object is registered as a
>>> RIPE Atlas Anchor contact in the RIPE Atlas systems.
>>> 
>>> Could you perhaps somehow undelete such role object? Would it be
>>> possible to prevent such clean up in the future?
>>> 
>>> Best regards,
>>> Ondřej Caletka
>>> CESNET
>>> 
>>> 
>> 
>> 
>