From info at arin.net Fri Jul 8 09:53:10 2022 From: info at arin.net (ARIN) Date: Fri, 08 Jul 2022 09:53:10 -0400 Subject: [ARIN-Suggestions] New Response for ACSP Suggestion 2022.4 Message-ID: A new response from ARIN has been posted for the 2022.4 suggestion. Find the original suggestion and our response below: ------------ ACSP Suggestion 2022.4: ARIN Online - Display RSA/LRSA Status https://www.arin.net/participate/community/acsp/suggestions/2022/2022-04/ Description: Give ARIN Orgs the ability to see if their IP resources are covered by an L/RSA via the user dashboard. Value to Community: ARIN requires IP resources to be covered an L/RSA to use RPKI services and the ARIN authenticated IRR. Giving resource holders the ability to identify which, if any, need an L/RSA before signing up for RPKI and IRR services, and should limit the calls to the ARIN help desk requesting this information. Timeframe: Not specified ------------ Response from ARIN: Thank you for your suggestion, numbered 2022.4 on confirmed receipt, requesting that we display RSA/LRSA status on resources in ARIN Online so customers can check their resources to see if they are eligible to use ARIN?s authenticated Internet Routing Registry (IRR) and Resource Public Key Infrastructure (RPKI) services. Development of this functionality was completed and deployed on 10 May 2022. Now customers who are logged in to their ARIN Online account will see a notes field on the Dashboard if any linked organization?s resources are not covered by an RSA or LRSA. There are also links provided to get more detailed information, including an explanation of the RSA/LRSA contract and how to get coverage if necessary. 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 Fri Jul 15 15:57:29 2022 From: info at arin.net (ARIN) Date: Fri, 15 Jul 2022 15:57:29 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion (2022.18) and Response Message-ID: One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Find the original suggestion and ARIN's 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. We are providing this suggestion to our General Counsel for review and evaluation. This suggestion will remain open until ARIN provides its position on this matter. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Tue Jul 19 16:59:02 2022 From: info at arin.net (ARIN) Date: Tue, 19 Jul 2022 16:59:02 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion (2022.20) and Response Message-ID: <6D5CF9F3-F333-471F-AA9B-98BDB4BFB3FC@arin.net> One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Find the original suggestion and ARIN's response below. ---------------- ACSP Suggestion 2022.20: Relocate ARIN Staff and Offices Outside of Washington, DC Area https://www.arin.net/participate/community/acsp/suggestions/2022/2022-20/ Description: Move ARIN Staff and Offices Outside of the Influence of the DC Beltway. Value to Community: A more neutral location like the Federal Government did with divisions of the Department of Agriculture. Also after the initial move costs, a location like Kansas City would be less expensive for ARIN as an Organization and it?s employees cost of living would be a fraction of DC. Better utilization of member provided funding. Better shepherding. Less influence of the DC Beltway bureaucracy in the Midwest. Less politics and the English language used inside the DC Beltway. Timeframe: Not specified ------------ Response from ARIN: Thank you for your suggestion, numbered 2022.20 upon confirmed receipt, requesting that ARIN relocate its offices and staff outside the influence of the DC Beltway to a more neutral location in the Midwest. Given that such a change would fall under the strategic guidance and fiscal oversight of the ARIN Board of Trustees, this suggestion will be provided to the ARIN Board Chair for future consideration. Thank you for your participation in the ARIN Consultation and Suggestion Process. This suggestion is now closed. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Thu Jul 28 15:13:08 2022 From: info at arin.net (ARIN) Date: Thu, 28 Jul 2022 15:13:08 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion (2022.21) Message-ID: <1214E5A7-160A-4A16-9E0B-EA813B54A07A@arin.net> One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). It is in review and pending response. ---------- ACSP Suggestion 2022.21: Allow Multiple RPKI Certificate Authorities to Publish to each Org-ID https://www.arin.net/participate/community/acsp/suggestions/2022/2022-21/ Author: Rich Compton Description: Allow multiple RPKI CAs to publish to each Org-ID. In our use case, we want to run the hybrid RPKI model where we use krill as the CA and then use ARIN?s publication server and repository. We want to create child CAs in krill and assign prefixes to various business units. This would require these child CAs to be able to publish to ARN. Right now only one CA can publish to each Org-ID. Value to Community: This will allow organizations to delegate the generation/administration of ROAs to child CAs. Timeframe: Not specified Status: Confirmed Regards, The American Registry for Internet Numbers (ARIN)