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 ]
Job Snijders
job at instituut.net
Wed Jul 1 21:54:35 CEST 2020
On Wed, Jul 1, 2020, at 19:06, Cynthia Revström wrote: > I was not suggesting it, I think it is a bad idea, but I interpreted > the following as Job suggesting it. > > I think a mandatory "-MNT" or "MNT-" or "-MAINT" is helpful because the maintainers primary key string does pop up from time to time without any context, and this can lead to confusion. See https://seclists.org/nanog/2020/Jan/650 for a fun story about how one person's email error code is another person's BGP autonomous system reference. :-) Apologies for being not clear. I can rephrase: it would've been nice if from the start a suffix like "-MAINT" was used to clearly label the object names as the type they are. But that ship clearly has long sailed. We can't change that anymore. 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. Kind regards, Job
- 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 ]