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 ]
Netmaster (exAS286)
netmaster at as286.net
Wed Nov 9 23:31:06 CET 2022
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. 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"). Markus
- 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 ]