[ARIN-consult] Reminder on ARIN’s Consultation of Enforcing Hierarchical Naming for AS-SETs

[ARIN]

ARIN would like to remind the community about the ongoing consultation focused on a potential improvement to ARIN’s Internet Routing Registry (IRR) that would enforce hierarchical naming for new AS-SETs. This consultation is scheduled to close on Friday, 23 May. Please submit your comments to the arin-consult mailing list before then. 

This consultation is based on a community suggestion that ARIN consider updating its IRR rules to prohibit the creation of non-unique AS-SET names in our authoritative IRR database. It is important to note that this proposed change will not impact existing AS-SETs, nor apply to AS-SET objects stored in third-party IRR databases, and retroactive enforcement is not under consideration.

To implement the proposed change, ARIN would need to update the rules for naming AS-SET objects. This would require modifications to both the web user interface and our RESTful API end point.

Read the full text of the consultation at:  https://www.arin.net/participate/community/acsp/consultations/2025/2025-1/ 

As of 13 May, we have received few comments from the community regarding this consultation. Specifically, we are looking for input from the community on the following questions:

- Do you have automation that would be impacted by enforcement of this proposed change?
- Are you negatively impacted by the current AS-SET naming conventions?
- Should this work be prioritized ahead of other work on ARIN’s development roadmap?

If you have comments you’d like to share with ARIN, please provide it to the arin-consult mailing list via arin-consult at arin.net. ARIN seeks clear direction through community input, so your feedback is important.

Thank you for your participation in this community consultation.

Regards,

John Curran
President and CEO
American Registry for Internet Numbers (ARIN)