<html><head></head><body><div class="ydp8e1c723eyahoo-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">My apologies for once again being a conversation killer :( </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Let me try to revive this conversation and see if we have a consensus.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">There seemed to be two main issues:</div><div dir="ltr" data-setdir="false">1/ MNTNER names not having a clear 'tag' indicating a MNTNER object</div><div dir="ltr" data-setdir="false">2/ MNTNER names specifically confused with ASNs</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">For the first part we can add a prefix (MNT-) or suffix (-MNT), or allow both options, and enforce this on all 'new' MNTNER object creations.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">For the second part, if there are specific objects that 'look like' ASNs and not belonging to the organisations holding those ASNs, they can be further investigated, if it is considered necessary. Please also bear in mind that PERSON and ROLE objects can also appear to be ASNs. It is also possible to create MNTNER objects that could be confused as IP ranges to unfamiliar database users. There may be other examples of objects that could be confused as a resource object. So if we go down this route where do we draw the line?</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Final comments please?</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 dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><br></div><div><br></div>
</div><div id="ydp797b1fc2yahoo_quoted_9086568818" class="ydp797b1fc2yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, 2 July 2020, 15:19:53 CEST, ripedenis--- via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydp797b1fc2yiv7591612525"><div><div class="ydp797b1fc2yiv7591612525ydp81d19b7ayahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div dir="ltr">Colleagues</div><div dir="ltr"><br clear="none"></div><div dir="ltr">"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"><br clear="none"></div><div dir="ltr">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"><br clear="none"></div><div dir="ltr">cheers</div><div dir="ltr">denis</div><div dir="ltr"><br clear="none"></div><div dir="ltr">co-chair DB-WG</div><div><br clear="none"></div>
</div><div class="ydp797b1fc2yiv7591612525ydp2204cbbyahoo_quoted" id="ydp797b1fc2yiv7591612525ydp2204cbbyahoo_quoted_3841025545">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div class="ydp797b1fc2yiv7591612525yqt8715970772" id="ydp797b1fc2yiv7591612525yqtfd59043"><div>
On Wednesday, 1 July 2020, 21:55:20 CEST, Job Snijders via db-wg <db-wg@ripe.net> wrote:
</div>
<div><br clear="none"></div>
<div><br clear="none"></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="ydp797b1fc2yiv7591612525ydp2204cbbyqt2697000108" id="ydp797b1fc2yiv7591612525ydp2204cbbyqtfd55034"><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><div class="ydp797b1fc2yiv7591612525yqt8715970772" id="ydp797b1fc2yiv7591612525yqtfd92022">
</div></div></div></div></div>
</div>
</div></body></html>