From job at sobornost.net Mon May 12 12:29:11 2025 From: job at sobornost.net (Job Snijders) Date: Mon, 12 May 2025 16:29:11 +0000 Subject: [ARIN-consult] Consultation on Enforcing Hierarchical Naming for AS-SETs In-Reply-To: <460D6273-5A3A-400D-A1FB-FCF36715620D@arin.net> Message-ID: Dear ARIN, > ARIN is seeking feedback from the community on a potential improvement > to ARIN?s Internet Routing Registry (IRR) that would enforce > hierarchical naming for new AS-SETs. Thank you for providing this opportunity to give feedback on ARIN's IRR. > A community member suggested that ARIN consider updating its IRR rules > to prohibit the creation of non-unique AS-SET names in our > authoritative IRR database. Hierarchical AS-SET naming reduces the potential for accidents, which in turn helps everyone driving the Internet routing system highways :-) An decent elaboration on the problem being addressed is available here: https://manrs.org/2022/12/why-network-operators-should-use-hierarchical-as-sets/ > 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. I think the above described approach will help avoid disruption for legacy configurations, thanks for being considerate! > 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. > > Questions for the Community: > > - Do you have automation that would be impacted by enforcement of this > proposed change? No. > - Are you negatively impacted by the current AS-SET naming conventions? Nope, quite the contrary. I consider this a positive change to the ARIN IRR service. > - Should this work be prioritized ahead of other work on ARIN?s > development roadmap? No specific input, I'd just like it to be somewhere on the roadmap. Kind regards, Job From info at arin.net Tue May 13 10:35:13 2025 From: info at arin.net (ARIN) Date: Tue, 13 May 2025 10:35:13 -0400 Subject: [ARIN-consult] =?utf-8?q?Reminder_on_ARIN=E2=80=99s_Consultation?= =?utf-8?q?_of_Enforcing_Hierarchical_Naming_for_AS-SETs?= Message-ID: 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) From charles.lists at camonson.com Thu May 15 10:45:26 2025 From: charles.lists at camonson.com (Charles Monson) Date: Thu, 15 May 2025 09:45:26 -0500 Subject: [ARIN-consult] Consultation on Enforcing Hierarchical Naming for AS-SETs In-Reply-To: <460D6273-5A3A-400D-A1FB-FCF36715620D@arin.net> References: <460D6273-5A3A-400D-A1FB-FCF36715620D@arin.net> Message-ID: > Questions for the Community: > > - Do you have automation that would be impacted by enforcement of this proposed change? Not currently. However, any impact here would be positive from my perspective. This is a great idea. > - Are you negatively impacted by the current AS-SET naming conventions? Not currently but AS-SET name conflicts have been identified as a potential issue as we are relying more on automation. Anything that ensures uniqueness will be a net positive. > - Should this work be prioritized ahead of other work on ARIN?s development roadmap? I will just be happy to see it on the roadmap. I have already been telling customers to create AS-SETs using the hierarchical naming convention. ARIN enforcing that will make it much easier. Charles From info at arin.net Fri May 30 13:41:38 2025 From: info at arin.net (ARIN) Date: Fri, 30 May 2025 13:41:38 -0400 Subject: [ARIN-consult] =?utf-8?q?NOW_CLOSED_=E2=80=93_Consultation_on_En?= =?utf-8?q?forcing_Hierarchical_Naming_for_AS-SETs?= Message-ID: <9499F7ED-5047-4052-9CB8-5C0C36EABA45@arin.net> >From 23 April to 23 May, ARIN held a consultation seeking feedback from the community on a potential improvement to ARIN?s Internet Routing Registry (IRR) that would enforce hierarchical naming for new AS-SETs. After reviewing and discussing the comments received during the consultation, ARIN plans to add this improvement to our list of features for future prioritization. ARIN thanks those who provided valuable feedback on this consultation. We rely on this input from our members and community to help steer the organization as we continue our mission in support of the operation and growth of the Internet. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN)