Send ARIN-consult mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."
Today's Topics:
1. Re: Consultation on Enforcing Hierarchical Naming for AS-SETs
(Job Snijders)
2. Reminder on ARIN?s Consultation of Enforcing Hierarchical
Naming for AS-SETs (ARIN)
----------------------------------------------------------------------
Message: 1
Date: Mon, 12 May 2025 16:29:11 +0000
From: Job Snijders <[email protected]>
To: [email protected]
Subject: Re: [ARIN-consult] Consultation on Enforcing Hierarchical
Naming for AS-SETs
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
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
------------------------------
Message: 2
Date: Tue, 13 May 2025 10:35:13 -0400
From: ARIN <[email protected]>
To: <[email protected]>
Subject: [ARIN-consult] Reminder on ARIN?s Consultation of Enforcing
Hierarchical Naming for AS-SETs
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
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)
------------------------------
Subject: Digest Footer
_______________________________________________
ARIN-consult mailing list
[email protected]
https://lists.arin.net/mailman/listinfo/arin-consult
------------------------------
End of ARIN-consult Digest, Vol 115, Issue 1
********************************************
