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 -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/routing-wg
