[db-wg] mntner with misleading primary key

Tom Hill via db-wg wrote on 01/07/2020 15:56:
> I'm unable to construct a query to the RIPEDB that looks for mntner
> objects beginning with 'as', in order to gauge how common this is. I
> suspect that's because the phrase is too short, but if it is possible
> please do enlighten me! :)

No direct way to query via the standard interface, but you can do it 
this way:

> crumpet% wget ftp://ftp.ripe.net/ripe/dbase/split/ripe.db.mntner.gz
> [...]
> crumpet% gzcat ripe.db.mntner.gz | egrep -i '^mntner:[[:space:]]+as[0-9]+$'
> mntner:         AS327833
> mntner:         AS58224
> mntner:         AS42910
> mntner:         AS37527
> mntner:         AS8362
> mntner:         AS202723
> mntner:         as2856
> mntner:         AS12400
> mntner:         AS427313
> mntner:         AS397268
> mntner:         AS12655
> mntner:         AS30956
> mntner:         AS49717
> crumpet%

Otherwise:

> Should it be possible to create mntners (or other objects) that infer a
> relationship and/or authority to a given aut-num (or organisation?)

Yes, this is a problem with any DB which returns text-based output based 
on searches of arbitrary input tokens.

In an IRR, some object primary keys have restrictions on what you can 
call them.  For example, an as-set must start with "AS-".

What you're really asking in the context of this style of database is 
that each primary key must assume a specific format which cannot be 
replicated on any other object type.  This would be difficult to retrofit.

Nick