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]/

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

Previous message (by thread): [db-wg] Set default maintainer on locked inetnum resources
Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Edward Shryane eshryane at ripe.net
Thu Feb 23 14:28:53 CET 2023

Dear Colleagues,

> On 10 Feb 2023, at 10:49, Edward Shryane via db-wg <db-wg at ripe.net> wrote:
> ...
> 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.
> 

We now plan to notify the resource contacts and LIR default maintainers by email on Monday 27th February, and will update the affected objects on the following Monday 6th March.

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

We have performed due diligence checks on the 13 LEGACY resources and have confirmed the relationship with the associated LIR.

We will also include the 438 ASSIGNED PA resources, as already mentioned.

Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] Set default maintainer on locked inetnum resources
Next message (by thread): [db-wg] country codes in the RIPE Database (was: ORGANISATION country code)

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]