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] Set default maintainer on locked inetnum resources

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

Nick Hilliard nick at foobar.org
Thu Feb 9 14:38:45 CET 2023

Edward Shryane via db-wg wrote on 09/02/2023 13:31:
> 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.
if the LIR / end-user contacts the RIPE NCC, is this what you guys do by 
default?  If so, then doing this by default for all affected objects 
seems reasonable enough.

Nick

Previous message (by thread): [db-wg] Set default maintainer on locked inetnum resources
Next message (by thread): [db-wg] Set default maintainer on locked inetnum resources

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

[ db-wg Archives ]