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/[email protected]/
[routing-wg] Adding "::" notation to RIPE DB
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jared Mauch
jared at puck.nether.net
Wed Nov 9 23:39:06 CET 2022
On Wed, Nov 09, 2022 at 10:31:06PM +0000, Netmaster (exAS286) wrote: > Jared Mauch wrote on Wednesday, November 9, 2022 10:08 PM: > > I would look at the precedent of things like RIPE-NONAUTH for time > > and duration. > > I wouldn't. RIPE-NOAUTH was more of a DB cleanup and likely not > broke any tools. I'm saying use the time window of that migration, so announce and then over that time be able to do it. I'm not saying everyone will upgrade or listen, but also not everyone will until something is actually broken either. > Introducing '::' however might/will break tools following RFC2280/RFC2622 > being read as (and mostly implemented/enforced like this) "a single colon > between set names and AS numbers" (hmmm, it states 'separated by colons ":"', > but examples kind of imply the "single between"). The nice thing is moving to the ASN removes the possibility of being unique, I recently moved from AS-NETHER to AS267 to reduce the chance of conflict. We should also likely move from AS-AKAMAI to AS20940:GLOBAL or something else. Moving forward shouldn't scare people if we have a good notification regime. - Jared -- Jared Mauch | pgp key available via finger from jared at puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
- Previous message (by thread): [routing-wg] Adding "::" notation to RIPE DB
- Next message (by thread): [routing-wg] Adding "::" notation to RIPE DB
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]