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

On 10.11.2022 06:44, Netmaster (exAS286) wrote:
> 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.
> 

Well, actually, you're never safe from shooting yourself in the foot.

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

Isn't there only a limited number of "trusted" IRRs? Hence, moving to 
ASx:AS-SET would be a huge step forward.



Arnold

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/routing-wg/attachments/20221110/a74ed65d/attachment.sig>