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 [email protected]
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
--
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
