[db-wg] Set default maintainer on locked inetnum resources

Seems like a reasonable thing to do.

However with anything that changes after such a long time I think you
should notify all relevant admin contacts and maintainers a week or two in
advance. This is just so they have a chance to object if it would be the
wrong maintainer or whatever. Also make sure to notify those parties once
the update has gone through.

Are these legacy resources just those who are under some kind of direct or
indirect agreement with the RIPE NCC? I assume so but I just want to make
sure.

-Cynthia


On Thu, 9 Feb 2023, 14:32 Edward Shryane via db-wg, <db-wg at ripe.net> wrote:

> Dear colleagues,
>
> From time to time, the RIPE NCC gets requests from LIRs to unlock their PA
> assignments that have RIPE-NCC-LOCKED-MNT as mnt-by.
>
> These inetnums are locked due to the deprecation of the NONE
> authentication scheme in 2004:
>
> https://www.ripe.net/publications/news/announcements/deprecation-of-the-none-authentication-scheme
>
> A total of 438 ASSIGNED PA AND 13 LEGACY inetnums have both this
> maintainer, and a responsible LIR organisation referenced in a
> less-specific inetnum.
>
> The DB team wishes to update these inetnums with the responsible LIR's
> default maintainer, so they can be maintained by the LIR without needing to
> contact the RIPE NCC. We will inform the affected maintainers.
>
> Please let me know your comments. If there are no objections, I'd like to
> implement this in the coming weeks.
>
> Regards
> Ed Shryane
> RIPE NCC
>
>
> --
>
> To unsubscribe from this mailing list, get a password reminder, or change
> your subscription options, please visit:
> https://mailman.ripe.net/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20230209/bd90dcaf/attachment.html>