From info at arin.net Fri Sep 16 14:02:26 2022 From: info at arin.net (ARIN) Date: Fri, 16 Sep 2022 14:02:26 -0400 Subject: [ARIN-Suggestions] Response to ACSP Suggestion 2022.18 Message-ID: <1232D971-9FFD-4A50-B5B0-FFFC08123BFB@arin.net> A response from ARIN has been posted for the 2022.18 suggestion. Find the original suggestion and our response below: ----------- ACSP Suggestion 2022.18: Remove Section 7 from LRSA https://www.arin.net/participate/community/acsp/suggestions/2022/2022-18/ Description: It is estimated that around 35% of all IPv4 addresses make up the legacy IP space; private legacy address holders wish to exercise ownership and control of IP addresses assigned decades ago. Section 7 ?No property rights? of a current Registration Services Agreement (RSA: Version 12.0 / LRSA: Version 4.0 (16 Aug 2016) discourage legacy holders to enter the LRSA. Removal of Section 7 from LRSA: Version 4.0 would strengthen legacy holders? property rights in order to keep them from abandoning contractual governance regime of ARIN. This would be a distinct change from a current RSA/LRSA version, which forces the holders of legacy resources who wish to register them with ARIN to waive their legacy status. Value to Community: Value to the community is the accuracy of ARIN records, which is paramount with increasing digital privacy and security concerns. No records of legacy holders makes cybercrime investigations much more difficult and runs contrary to the stated mission of RIR to create robust registry for Internet resources. Timeframe: Not specified ----------- Response from ARIN: Thank you for your suggestion, numbered 2022.18 upon confirmed receipt, asking that ARIN consider removing Section 7 from the Registration Services Agreement (RSA/LRSA) as the ?No Property Rights? language discourages legacy IPv4 address holders from signing the agreement. Following review by ARIN?s General Counsel and discussion with the Board of Trustees, ARIN updated and announced a new RSA/LRSA on 12 September 2022. The updated RSA removes significant representations from Section 7 and renames the section (previously titled ?No Property Rights?) to ?Acknowledged Rights To Included Number Resources.? We are hopeful with the release of this updated RSA that organizations will more easily be able to utilize ARIN?s full suite of services. Because this work is completed, we are closing this suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Thu Sep 29 13:49:52 2022 From: info at arin.net (ARIN) Date: Thu, 29 Sep 2022 13:49:52 -0400 Subject: [ARIN-Suggestions] Two New ACSP Suggestions (2022.22 and 2022.23) Message-ID: Two new suggestions have been recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Both are currently in review and pending response. ---------- ACSP Suggestion 2022.22: Create Beta Test Environment for ASPA and BGPsec Router Keys https://www.arin.net/participate/community/acsp/suggestions/2022/2022-22/ Author: Rich Compton Description: Create a beta test environment for ASPA and BGPsec router keys. Value to Community: ASPA will provide protection against route leaks. BGPsec is an existing RFC that will allow path validation. ARIN members would be able to experiment with these new security controls and get more familiar with them and their use before deploying them into production. Timeframe: Not specified Status: Confirmed ---------- ACSP Suggestion 2022.23: Add Field for Multiple Prefixes on ROA Creation Page https://www.arin.net/participate/community/acsp/suggestions/2022/2022-23/ Author: Anonymous Description: Field to add multiple prefixes at one time for the browser signed ROA creation page. Value to Community: When multiple prefixes needed to be added to the Create ROA via browser signed method it takes a very long time to input them. It would be super helpful if the user can upload a CSV text file, e.g., prefix,CIDR, maxLength Or a text field where a user can paste the list of prefixes. I know there?s a signed method and API calls but for the non-coder those are not easy tasks. Timeframe: Not specified Status: Confirmed ---------- Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Fri Sep 30 13:23:04 2022 From: info at arin.net (ARIN) Date: Fri, 30 Sep 2022 13:23:04 -0400 Subject: [ARIN-Suggestions] New Responses to Multiple ACSP Suggestions Message-ID: <7E2EF11A-8BAC-4B23-BEC9-A535A702D171@arin.net> A response from ARIN has been posted for the following suggestions. You may find the original suggestions and latest responses from ARIN at the links below. 2022.22: Create Beta Test Environment for ASPA and BGPsec Router Keys (Open) https://www.arin.net/participate/community/acsp/suggestions/2022/2022-22/ 2021.26: Amend Bylaws to Require NomCom to Provide Nomination Data (Closed) https://www.arin.net/participate/community/acsp/suggestions/2021/2021-26/ 2021.25: Delay Opening Statements of Support Site Until Final ARIN Candidate Slate Announced (Closed) https://www.arin.net/participate/community/acsp/suggestions/2021/2021-25/ 2021.23: Reporting Framework for Application Feedback for Nominees (Closed) https://www.arin.net/participate/community/acsp/suggestions/2021/2021-23/ 2021.22: ARIN Election Transparency Improvements (Closed) https://www.arin.net/participate/community/acsp/suggestions/2021/2021-22/ 2021.21: Allow Petitioning Board of Trustees and Advisory Council Candidates to Receive Statements of Support (Closed) https://www.arin.net/participate/community/acsp/suggestions/2021/2021-21/ Thanks to all of our submitters for their participation in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN)