[ncc-services-wg] Improving the Management of RIPE Database Objects with Joint Responsibility

Dear colleagues,

As announced to the RIPE NCC Services Working Group on 22 April, we have been working on simplifying information management in the RIPE Database.

Some objects in the RIPE Database have joint responsibility: allocations for IP resources and the ORGANISATION object. The result is that some attributes can only be changed by the RIPE NCC, and others could only be changed through the so-called LIR Portal Object Editors.

Today we have deployed business rules in the RIPE Database to determine which attributes you can change and which ones can only be changed by the RIPE NCC. In addition, we have made improvements to the LIR Portal, making the Object Editors obsolete.

What this means for you:

1. In the LIR Portal, users will have to go through a one-time operation of selecting a "default" maintainer, which is placed on all existing and new objects that have joint responsibility
2. Changes such as selecting another technical or administrative contact for an allocation for IP resources should be done in the RIPE Database from now on

Please note that it is not required to take action immediately. It is only when you want to change information in one of your allocations for IP resources and the ORGANISATION object that you will first have to select the "default" maintainer on this page:
https://my.ripe.net/#/account-details

You can read more on this functionality in this article on RIPE Labs:
https://labs.ripe.net/Members/AlexBand/improving-the-management-of-ripe-database-objects-with-joint-responsibility

Kind regards,

Alex Band
Product Manager
RIPE NCC