From info at arin.net Mon Oct 9 15:53:16 2023 From: info at arin.net (ARIN) Date: Mon, 09 Oct 2023 15:53:16 -0400 Subject: [ARIN-Suggestions] Two Suggestions are now closed; one Suggestion has a new response Message-ID: A new response from ARIN has been posted for suggestion 2022.12: Publish RSA/LRSA Status in Whois/RDAP and 2022.24: Notifications When ROAs Are Deleted or Modified. These suggestions are now closed. A new response from ARIN has also been posted for suggestion 2023.13: REST API Method to Determine a Specific NET Object for a Range, and this suggestion is now open. You may find the original suggestions and the responses from ARIN below. Regards, American Registry for Internet Numbers (ARIN) ---------- 2022.12: Publish RSA/LRSA Status in Whois/RDAP https://www.arin.net/participate/community/acsp/suggestions/2022/2022-12/ Author: Anonymous Submitted On: 20 April 2022 Description: ARIN should include the registration services contract status of each number resource block in the public registry (visible via Whois/RDAP) - No agreement, RSA, or LRSA (i.e. entered into an LRSA/RSA as a legacy number resource) Value to Community: There is an increasing amount of effort in securing Internet routing that has dependency on ARIN services (e.g. RPKI), and consistent data analysis of the progress and barriers to deployment is not possible without this information being publicly available. (It is acceptable for ARIN to redact this information from publication if necessary due to legal circumstances, for example disputes or litigation.) Timeframe: Not specified Status: Closed ARIN Comment: Thank you for your suggestion, numbered 2022.12 on confirmed receipt, asking that ARIN include the registration services contract status of each number resource block in the public registry via Whois/RDAP. As noted in our original response on 30 June 2022, due to privacy concerns related to including this information in Whois, we agreed to publish a daily report that would list the network and the type of service it receives from ARIN, Full Registry services vs Basic Legacy services. The functionality to support this report was deployed on 9 October 2023, and it is accessible at https://arin.net/reference/research/statistics/resources/, or directly via FTP here: ftp://ftp.arin.net/pub/resource_registry_service/. Because this work is completed, we are closing this suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. ------ 2022.24: Notifications When ROAs Are Deleted or Modified https://www.arin.net/participate/community/acsp/suggestions/2022/2022-24/ Author: Pradeep Kumar Submitted On: 04 October 2022 Description: ROA deletion/modification Notification Value to Community: When RPKI becomes strict we should have proper ROA for all prefixes advertised on internet. When any prefix missing ROA there is high possibilities to getting rejected in external BGP tables. So we need to be notified when ROA get deleted when ROA was deleted through a reroll following a transfer of net resources from your OrgID. Timeframe: Not specified Status: Closed ARIN Comment: Thank you for your suggestion, numbered 2022.24 on confirmed receipt, requesting that ARIN notify customers when ROAs get deleted through a reroll following a transfer of net resources from their Org ID. Development of this functionality was released on 9 October 2023. Because this work is completed, we are closing this suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. ------ 2023.13: REST API Method to Determine a Specific NET Object for a Range https://www.arin.net/participate/community/acsp/suggestions/2023/2023-13/ Author: Anonymous Submitted On: 05 September 2023 Description: REST API method to determine the most specific NET object for a range. Value to Community: The NET portion of the REST API requires a user to know the Net Handle to perform any modifications, but given a subrange of a NET (or NETs) there is no way in the API to determine what NET this corresponds to. There is a method, mostSpecificNet/, but it only works if provide it with the exact start and finish to the block. My point is that there is no way in the current API to bootstrap functionality based on knowing a problematic IP, and then learning more about it (delegation, POCs, etc). Instead I need to integrate to whois, which seems silly when ARIN clearly has the data available programmatically, but not exposed via the API. Timeframe: Not specified Status: Open ARIN Comment: Thank you for your suggestion, numbered 2023.13 upon confirmed receipt, asking ARIN to develop a REST API method to determine the most specific NET object for a range. We are evaluating the work needed to develop this functionality and plan to conduct a consultation to determine the value of this feature to the ARIN customer community. Your suggestion will remain open pending the outcome of the community consultation. Thank you for participating in the ARIN Consultation and Suggestion Process. From info at arin.net Fri Oct 27 11:30:07 2023 From: info at arin.net (ARIN) Date: Fri, 27 Oct 2023 11:30:07 -0400 Subject: [ARIN-Suggestions] Four New ACSP Suggestions and One Response Message-ID: Four new suggestions have been received (2023.15, 2023.16, 2023.17, and 2023.18), and a response from ARIN has been posted for 2023.15. You may find the new suggestions and latest response from ARIN in full below. Regards, American Registry for Internet Numbers (ARIN) ------- ACSP Suggestion 2023.15: Allow Specified Description of API Keys https://www.arin.net/participate/community/acsp/suggestions/2023/2023-15/ Author: Marcus Jackson Submitted On: 25 October 2023 Description: Please allow users to specify a description of API keys. Value to Community: In the absence of fine grained permissions, and named service roles (already a suggestion) a way to specify the intended use of a key would be extremely helpful for key management. It would be even more useful to specify exactly what functionality is allowed by that key, as it would allow us to create applications with a smaller blast radius. Timeframe: Not specified | Status: Open ARIN Comment: Thank you for your suggestion, numbered 2023.15 upon confirmed receipt, asking that ARIN provide the ability to allow users to specify a description of an API key to make it easier to track the functionality of each key. ARIN agrees that this would be a useful for customers who have multiple API keys. We will add this to our deployment schedule and prioritize it along with other development initiatives. Your suggestion will remain open until implemented. Thank you for participating in the ARIN Consultation and Suggestion Process. ------- ACSP Suggestion 2023.16: Give Voting Rights to Qualified Facilitators https://www.arin.net/participate/community/acsp/suggestions/2023/2023-16/ Author: Mike Burns Submitted On: 26 October 2023 Description: Give Qualified Facilitators voting rights Value to Community: Qualified Facilitators have greater exposure to ARIN people and policies than most resource holders and their votes would be presumably well-informed. Timeframe: Not specified | Status: Confirmed ------- ACSP Suggestion 2023.17: Allow Third-Party ROA Creation by Block https://www.arin.net/participate/community/acsp/suggestions/2023/2023-17/ Author: Mike Burns Submitted On: 26 October 2023 Description: Allow third-party ROA creation by block, not by Organization. Currently an organization can allow a third-party to create ROAs, but that authority extends to all the organization?s blocks. Some organizations may wish to enable this capability but only for a subset of their resources. Value to Community: The community sees the good in RPKI growth, and this is an impediment in circumstances where a portion of an organization?s resources are leased-out and a lease manager seeks to automate ROA actions, which can only happen if blanket authority is granted to the lease manager to create ROAs for all the registrant organization?s resources. Timeframe: Not specified | Status: Confirmed ------- ACSP Suggestion 2023.18: Expand Fraud Reporting to Include Leasing of 4.10 Space https://www.arin.net/participate/community/acsp/suggestions/2023/2023-18/ Author: Anonymous Submitted On: 27 October 2023 Description: Widen scope of ARIN fraud reporting tool to include NRPM 4.10 leasing or offer a similar submission mechanism for this purpose. Value to Community: NRPM 4.10 space is extremely valuable for new startups. We might not exist without it. There are numerous organizations who acquire NRPM 4.10 prefixes and then lease them out in the leasing market fur purposes other than IPv6 transition. The current fraud reporting tool seems geared towards outright theft by way of illegal transfers or the creation of organizations fake documentation. There needs to be a way to report NRPM 4.10 prefixes that are being leased out. Timeframe: Not specified | Status: Confirmed From info at arin.net Tue Oct 31 15:41:14 2023 From: info at arin.net (ARIN) Date: Tue, 31 Oct 2023 15:41:14 -0400 Subject: [ARIN-Suggestions] Two Suggestions are now closed; One new response from ARIN Message-ID: <06BAAEBF-FA2E-403A-BD67-752E9764B118@arin.net> A new response from ARIN has been posted for the following three suggestions: 2023.16: Give Voting Rights to Qualified Facilitators 2023.17: Allow Third-Party ROA Creation by Block 2023.18: Expand Fraud Reporting to Include Leasing of 4.10 Space The 2023.16 and 2023.17 suggestions are now closed. The 2023.18 suggestion is now open. You may find the original suggestions and the responses from ARIN below. Regards, American Registry for Internet Numbers (ARIN) ------- ACSP Suggestion 2023.16: Give Voting Rights to Qualified Facilitators https://www.arin.net/participate/community/acsp/suggestions/2023/2023-16/ Author: Mike Burns Description: Give Qualified Facilitators voting rights Value to Community: Qualified Facilitators have greater exposure to ARIN people and policies than most resource holders and their votes would be presumably well-informed. Status: Closed Updated: 31 October 2023 ARIN Comment: Thank you for your suggestion, numbered 2023.16 upon confirmed receipt, asking that ARIN give voting rights to Qualified Facilitators. Given ARIN Elections are governed by the Bylaws which are subject to the approval of the ARIN Board of Trustees, this suggestion will be referred 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. ------- ACSP Suggestion 2023.17: Allow Third-Party ROA Creation by Block https://www.arin.net/participate/community/acsp/suggestions/2023/2023-17/ Author: Mike Burns Description: Allow third-party ROA creation by block, not by Organization. Currently an organization can allow a third-party to create ROAs, but that authority extends to all the organization?s blocks. Some organizations may wish to enable this capability but only for a subset of their resources. Value to Community: The community sees the good in RPKI growth, and this is an impediment in circumstances where a portion of an organization?s resources are leased-out and a lease manager seeks to automate ROA actions, which can only happen if blanket authority is granted to the lease manager to create ROAs for all the registrant organization?s resources. Status: Closed Updated: 31 October 2023 ARIN Comment: Thank you for your suggestion, numbered 2023.17 upon confirmed receipt, asking that ARIN allow third-party ROA creation by block, rather than be organization. We are investigating the options and implications for adding this functionality and will be presenting our recommendations to the community for consultation. We are closing your suggestion as referred to community consultation. Thank you for participating in the ARIN Consultation and Suggestion Process. ------- ACSP Suggestion 2023.18: Expand Fraud Reporting to Include Leasing of 4.10 Space https://www.arin.net/participate/community/acsp/suggestions/2023/2023-18/ Author: Anonymous Description: Widen scope of ARIN fraud reporting tool to include NRPM 4.10 leasing or offer a similar submission mechanism for this purpose. Value to Community: NRPM 4.10 space is extremely valuable for new startups. We might not exist without it. There are numerous organizations who acquire NRPM 4.10 prefixes and then lease them out in the leasing market fur purposes other than IPv6 transition. The current fraud reporting tool seems geared towards outright theft by way of illegal transfers or the creation of organizations fake documentation. There needs to be a way to report NRPM 4.10 prefixes that are being leased out. Status: Open Updated: 31 October 2023 ARIN Comment: Thank you for your suggestion, numbered 2023.18 upon confirmed receipt, asking that ARIN widen the scope of our fraud reporting tool to include misuse of IPv4 address space acquired using NRPM 4.10. Dedicated IPv4 Block to Facilitate IPv6 Deployment. We are in the process of evaluating and updating ARIN Fraud Reporting process and procedures, and your feedback will be taken into consideration during this effort. Your suggestion will remain open pending the outcome of the Fraud Process review. Thank you for participating in the ARIN Consultation and Suggestion Process.