[db-wg] mntner with misleading primary key

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
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/db-wg/attachments/20200701/0c0d1ff1/attachment.sig>