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 all Top-level Resources

Previous message (by thread): [db-wg] Removing the Legacy Status "remarks" attribute
Next message (by thread): [db-wg] Set Default Maintainer on all Top-level Resources

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

Edward Shryane eshryane at ripe.net
Mon Oct 21 11:51:12 CEST 2019

Dear Colleagues,

as presented during the DB-WG session at RIPE 79, we wish to extend the "Default Maintainer" functionality for LIR organisations.

Firstly, to set the Default Maintainer (with an mnt-by: attribute) on *all* top-level resources (where the org: reference is the LIR itself):

- IPv4 and IPv6 allocations (the current behaviour)
- ASNs
- IPv4 and IPv6 assignments
- IPv4 LEGACY resources

Secondly, to automatically (re-)set the Default Maintainer on a nightly basis, on *all* top-level resources:

- Fix inconsistencies due to manual updates
- Add the default maintainer (with an mnt-by: attribute), and remove other user maintainer(s)

Please let me know of any feedback or questions you may have.

Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] Removing the Legacy Status "remarks" attribute
Next message (by thread): [db-wg] Set Default Maintainer on all Top-level Resources

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

[ db-wg Archives ]