This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/

[db-wg] mntner with misleading primary key

Previous message (by thread): [db-wg] mntner with misleading primary key
Next message (by thread): [db-wg] mntner with misleading primary key

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Tom Hill tom at ninjabadger.net
Wed Jul 1 22:39:01 CEST 2020

On 01/07/2020 20:54, Job Snijders via db-wg wrote:
> 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.

As I don't think we have seen this exploited (yet) I'd settle for the
latter; to prevent future occurrences. It wouldn't hurt to ask those
nicely to rename their mntners, but I'd wager most of those mntners
identified will be in use by the aut-num of the same AS number. A random
selection from Matthias' list that I've just checked quickly are exactly
like that; aut-num AS49717, mnt-by AS49717.

Regards,

-- 
Tom

Previous message (by thread): [db-wg] mntner with misleading primary key
Next message (by thread): [db-wg] mntner with misleading primary key

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]