This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ncc-announce] [service] Cleanup Locked Person Objects in the RIPE Database (Implementation on 3rd June)
- Previous message (by thread): [ncc-announce] [meetings] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
eshryane at ripe.net
eshryane at ripe.net
Fri May 29 10:05:09 CEST 2020
Dear colleagues, As previously announced, the RIPE Database Team plan to clean up locked person objects in the RIPE Database. We will select person objects maintained by RIPE-NCC-LOCKED-MNT, which are referenced by inetnum allocations or assignments, and re-assign them to the resource maintainer, so they can be properly maintained, and it is clear who is responsible for them. We now plan to perform this cleanup on Wednesday, 3 June 2020. We have already notified the affected LIRs and resource maintainers by email. You do not need to take any action. For more information on the Locked Person Objects Cleanup, please refer to this RIPE Labs article : https://labs.ripe.net/Members/ed_shryane/cleaning-up-locked-person-objects-in-the-ripe-database Regards, RIPE NCC Database Team
- Previous message (by thread): [ncc-announce] [meetings] Join us for the RIPE NCC Educa::IPv6-only
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]