[routing-wg] Adding "::" notation to RIPE DB

Jared Mauch wrote on Wednesday, November 9, 2022 11:39 PM
> On Wed, Nov 09, 2022 at 10:31:06PM +0000, Netmaster (exAS286) wrote:
> > 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.

I'm lost. AS20940:GLOBAL wouldn't be a valid AS-SET name. AS20940:AS-GLOBAL?

Well, with the requirement of the AS-SET names like ASx:AS-SET requiring
mnt-by of ASx, less likely "by accident" dups showing up. 

But it doesn't protect *evil* person adding ASx to an "open" RR and adding
a bad ASx:AS-SET there.

<constructive> It's an ugly way, but adding some semantics to the AS-SET
names to point to the right RR, wouldn't break existing tooling and could
be picked up by smarter tools. Like ASx:AS-SET-SOURCE-RIPE only being
valid if source if RIPE. I have said it's ugly, haven't I? And it's not a
proposal to solve the problem (as e.g. if someone would have missed this 
semantical layer and would register whyever AS1:AS-FOOBAR-SOURCE-RIPE
in RADB ...)

Markus