JB wrote Monday, October 23, 2023 5:38 PM CEST:
I am thinking about the usefulness of adding a new field to the RIPE database which is an AS-SET "exclude-member" field, to compliment the "member" field.
Another attempt to have tools do more than defined in the standards and get this implemented just in RIPE DB? ;-) [Just remember the :: notation.] It would be a "give others hints about -in most cases- brokenness of included (sub-*) members in your AS-SET", right? Now you telling others "what is right and what is wrong" for the mem- bers of your AS-SET (and their included members, ...). Not sure if I like that. And you just telling this from your perspective, but without any rea- son (e.g. because of your needs or because you think sub-sub-sub-sub AS-SET Z is "broken"). I feel the pain you have. We all have this. Some (I think) achieve similar by exploding the AS-SETs level by level and dropping e.g. IX-AS-SETs, questionable AS-SETs and Tier-1/certain ASNs. But that's for their own use. Sharing information on "which AS-SET is obviously broken and owner is not willing to cleanup (or explain, why it's not broken)", could be indeed of use - if trustful and transparent. But always have in mind: there are also not-so-nice players out there. Markus