[db-wg] mntner with misleading primary key

On 7/1/2020 3:05 PM, Gert Doering via db-wg wrote:
> Hi,
>
> On Wed, Jul 01, 2020 at 09:00:44PM +0200, Job Snijders wrote:
>> On Wed, Jul 1, 2020, at 20:52, Gert Doering wrote:
>>> On Wed, Jul 01, 2020 at 07:36:53PM +0200, Cynthia Revström via db-wg wrote:
>>>> I am not sure how feasible the mandatory "-mnt" would be at this point tbh.
> [..]
>> As I understand the conversation, the one option on the table to discuss is how to deal with primary keys that clash with other scopes of context, specifically autnums. Of those only 26 exist
>>
>> SPACENET-P does not look like an AS number so isn't an issue and doesn't need to change.
> This is true, but I was responding to Cynthia's suggestion of having a
> mandatory "-mnt".  Which would affect us - as I said, doable, but it needs
> to make sense.
>
> Of course if it's only about "looks like an ASN" mntners, I'll go back in
> my lurking corner and watch with interest :-)
>
> Gert Doering
>          -- NetMaster
I would be a fan of the mandatory -mnt.  This can cause other problems 
like I mentioned here a few weeks ago... RDAP will not work with 
KR4422-RIPE, because this is both a mntner and a person.