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

Previous message (by thread): [db-wg] Set Default Maintainer on all Top-level Resources
Next message (by thread): [db-wg] [swe-database] Implementation -K Flag Request

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

Edward Shryane eshryane at ripe.net
Tue Oct 22 16:31:27 CEST 2019

Hi Jacob,

> On 21 Oct 2019, at 16:57, Jacob Slater <jacob at rezero.org> wrote:
> 
> If the goal is to ensure consistency between the LIR Portal and the RIPE database, why not simply make all mntner attributes on top-level resources managed by the NCC? If changes are made in the LIR portal, any changes could go live immediately. After an initial cleanup, there would be no need to constantly reset it. 
> 
> Jacob Slater
> 

Yes, we could make the "mnt-by" attribute on top-level resources managed by the RIPE NCC (where a default maintainer is set), as an alternative to the nightly job.

Should we allow additional user maintainers on top-level resources, where a default maintainer is also set? 

Regards
Ed Shryane
RIPE NCC

Previous message (by thread): [db-wg] Set Default Maintainer on all Top-level Resources
Next message (by thread): [db-wg] [swe-database] Implementation -K Flag Request

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

[ db-wg Archives ]