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/db-wg@ripe.net/

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

Edward Shryane eshryane at ripe.net
Fri Feb 10 10:45:32 CET 2023

Hi Nick,

> On 9 Feb 2023, at 14:38, Nick Hilliard <nick at foobar.org> wrote:
> 
>> ...
> 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

Correct, this is what the RIPE NCC is doing by default now, on request.

Regards
Ed Shryane
RIPE NCC

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