One of my objects has RIPE-NCC-LOCKED-MNT as the only maintainer. Why is that?
It used to be possible to create unmaintained objects in the RIPE Database, but today that is no longer possible. Any unmaintained objects that were created before this change have had the RIPE-NCC-LOCKED-MNT added to it to prevent any person from making a change and potentially using it for abuse.
The RIPE Database also contains the RIPE-NCC-RPSL-MNT maintainer, that may be used to create objects to represent routing policy in the RIPE Database for number resources not allocated or assigned from the RIPE NCC. This maintainer should not be used as "mnt-by:" on any objects as it has a well-known public password, but in the past a number of users have done this anyway. The usage of the RIPE-NCC-RPSL-MNT maintainer is also restricted now and all objects that had this maintainer have been replaced with RIPE-NCC-LOCKED-MNT.
The locked objects will remain as they are. There is no procedure for unlocking these previously unmaintained or incorrectly maintained objects. If there is an operational need, new objects should be created by the object owners. This solution puts control back into the hands of the object owners. The user can follow the existing process for creating and referencing new objects.
Unreferenced person objects will be deleted from the RIPE Database periodically. See also: Clean-up of unreferenced person objects.