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

Hi Cynthia,

> On 9 Feb 2023, at 14:49, Cynthia Revström <me at cynthia.re> wrote:
> 
> 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.
> 

This is a good idea, we will email admin contacts in addition to maintainers, far enough in advance to give them a reasonable amount of time to respond.

> 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.
> 

Correct, there are 460 LEGACY inetnums in total that are locked, but only 13 of these are covered by an agreement with the RIPE NCC.

For each of these 13, we will perform due diligence on the parent LIR to confirm the relationship with the LEGACY resource.

Regards
Ed Shryane
RIPE NCC