[db-wg] mntner with misleading primary key

 Colleagues
"We can't change that anymore" Anything is possible and anything can be changed and any new rules/filters can be implemented. The RIPE NCC can, and has on many occasions in the past, done updates across the whole database to 'fix problems'.
I would suggest that you don't concern yourselves at this stage with 'how' something can be done. Discuss and debate what you think is needed or wanted and justifiable. Bearing in mind that not everyone will agree on either need or want or the justification. If we can reach a consensus on what is needed to be done, then the RIPE NCC can look at the how and the impact.
cheersdenis
co-chair DB-WG
    On Wednesday, 1 July 2020, 21:55:20 CEST, Job Snijders via db-wg <db-wg at ripe.net> wrote:  
 
 On Wed, Jul 1, 2020, at 19:06, Cynthia Revström wrote:
> I was not suggesting it, I think it is a bad idea, but I interpreted 
> the following as Job suggesting it.

> > I think a mandatory "-MNT" or "MNT-" or "-MAINT" is helpful because the maintainers primary key string does pop up from time to time without any context, and this can lead to confusion. See https://seclists.org/nanog/2020/Jan/650 for a fun story about how one person's email error code is another person's BGP autonomous system reference. :-)

Apologies for being not clear.

I can rephrase: it would've been nice if from the start a suffix like "-MAINT" was used to clearly label the object names as the type they are.But that ship clearly has long sailed. We can't change that anymore.

The next best thing we can now do is attempt to rename the ones that actually clash with autnums, which luckily is only a very short list, and prevent future occurrences with a creation filter.

Kind regards,

Job
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/db-wg/attachments/20200702/737ed83a/attachment.html>