Hi,
On Tue, May 13, 2025 at 08:31:00PM +0100, Nick Hilliard wrote:
> The 2,000 AS-SETs lacking members highlight a significant data quality
> issue. While technically compliant with RFC 2622, these empty AS-SETs
> serve no practical purpose and may lead to routing policy management
> challenges.
There may be valid operational reasons why an operator would want their
as-set to be empty, e.g. they might want a placeholder as-set in someone
else's routing policy which they can update as required. Or they might
want to use specific constructions like AS-NULL in their routing policy
for some reason.
Agreeing with Nick here.
Especially since 1350 (current dump of as-sets ftp export) are not
hierarchical as-sets which could be used to just "reserve" the as-set
name.
Also, I heard some consider AS65000:AS-FOO to implicitly include
"AS65000" as member in filter scenarios, assuming human error in the
setup. (Even though strictly speaking, it's still an empty set.)
--
Inrin
-----
To unsubscribe from this mailing list or change your subscription options,
please visit: https://mailman.ripe.net/mailman3/lists/db-wg.ripe.net/
As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings.
More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
