<html><head></head><body><div class="ydp81d19b7ayahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr" data-setdir="false">Colleagues</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">"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'.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">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.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">cheers</div><div dir="ltr" data-setdir="false">denis</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">co-chair DB-WG</div><div><br></div>
</div><div id="ydp2204cbbyahoo_quoted_3841025545" class="ydp2204cbbyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, 1 July 2020, 21:55:20 CEST, Job Snijders via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">On Wed, Jul 1, 2020, at 19:06, Cynthia Revström wrote:</font></font><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">> I was not suggesting it, I think it is a bad idea, but I interpreted </font></font><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">> the following as Job suggesting it.</font></font><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">> > 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 </font></font><a shape="rect" href="https://seclists.org/nanog/2020/Jan/650 " rel="nofollow" target="_blank"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">https://seclists.org/nanog/2020/Jan/650 </font></font></a><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">for a fun story about how one person's email error code is another person's BGP autonomous system reference. :-)</font></font><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">Apologies for being not clear.</font></font><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">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.</font></font><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">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.</font></font><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">Kind regards,</font></font><div class="ydp2204cbbyqt2697000108" id="ydp2204cbbyqtfd55034"><br clear="none"><br clear="none"><font style="vertical-align: inherit;"><font style="vertical-align: inherit;">Job</font></font><br clear="none"></div></div></div>
</div>
</div></body></html>