[db-wg] Set Default Maintainer on all Top-level Resources

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