[db-wg] mntner with misleading primary key

On Tue, Sep 1, 2020 at 3:58 PM ripedenis--- via db-wg <db-wg at ripe.net> wrote:

[...]

> There seemed to be two main issues:
> 1/ MNTNER names not having a clear 'tag' indicating a MNTNER object
> 2/ MNTNER names specifically confused with ASNs
>
> 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.
>
> 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?
>
> Final comments please?

Strong support for reducing the opportunities for confusion from me.

Thanks for the summary.

Regards,

Leo Vegoda