From info at arin.net Tue Mar 3 11:58:06 2026 From: info at arin.net (ARIN) Date: Tue, 03 Mar 2026 11:58:06 -0500 Subject: [ARIN-Suggestions] One New Suggestion Received Message-ID: <1260E59C-FD53-406E-B549-4C254B26C507@arin.net> One new suggestion has been received (2026.4). You may find the new suggestion and link in full below. Regards, American Registry for Internet Numbers (ARIN) ----- ACSP Suggestion 2026.4: Fix API permission checks on NET https://www.arin.net/participate/community/acsp/suggestions/2026/2026-04/ Author: Richard Laager If there are multiple ways to do the same thing, they should require the same permissions. They should not be inconsistent. Steps to reproduce: 1. Perform a Detailed Reassignment out of one of your NETs to another ORG. 2. Try to GET that NET by handle using your API key. Expected results: The GET succeeds. Actual results: The GET is rejected for lack of permission. Only an API key of the ?another ORG? can GET the NET. Additional discussion: - I created the NET in the first place. If I created it, surely I should be able to GET it (assuming nothing else has changed in the state of the world). - I can DELETE the NET. If I can DELETE something, surely I should be able to GET it. - I can GET the NET if I ask using the start and end IP address (via a mostSpecificNet call), but I cannot GET it by its handle. - Anyone, without authentication, can view the same information using the WHOIS protocol, by handle or by IP address. This is equivalent to a GET. - Accordingly, the correct permission check for a GET on a NET is ?return True?. - Similarly, if I can DELETE and then recreate something, I should be able to modify it using a PUT. So the PUT permission check should also allow those with access to the parent NET to PUT a (direct) child NET (since they could otherwise DELETE and recreate it with the same effect). Value to Community: The NRPM requires documenting reassignments. ARIN discontinued the email interface in favor of the API. Having a correctly working API is useful. Status: Confirmed From info at arin.net Thu Mar 5 13:13:58 2026 From: info at arin.net (ARIN) Date: Thu, 05 Mar 2026 13:13:58 -0500 Subject: [ARIN-Suggestions] Suggestion 2025.8 is now closed Message-ID: <63978CDF-1239-4C5D-95B3-CF8779B708C3@arin.net> A new response from ARIN has been posted for ACSP Suggestion 2025.8: Make Commit Messages to the NRPM Gitlab More Informative and this suggestion is now closed. You may find the original suggestion and the response from ARIN below. Regards, American Registry for Internet Numbers (ARIN) ----- ACSP Suggestion 2025.8: Make Commit Messages to the NRPM Gitlab More Informative https://www.arin.net/participate/community/acsp/suggestions/2025/2025-08/ Author: Adair Thaxton Submitted On: 30 October 2025 Description: Make commit messages to the NRPM Gitlab more informative Value to Community: I have been pointed to the NRPM in Gitlab as a way to track historical changes to the NRPM. However, the commit messages (https://bitbucket.org/arin-rir/number-resource-policy-manual/commits/branch/master) do not tell me what changes are actually being made, only what version is current. If we intend for the Gitlab to be able to provide historical context, it?s currently not really easy to find that information. For example, during discussion of Draft Policy ARIN-2025-6, I went to the Gitlab to see the history of the phrase ?provider assignment unit? in section 6.5.2.1. I checked the commit messages to see if I could tell when this section was added or updated, but the sections that have been changed in each commit are not listed. Please consider the community?s ability to track changes to specific policies when committing changes to NRPM. Adding specific policies that are being reflected in commits would help too, but specifying policy changes would be very helpful. Status: Closed ----- ARIN Response: Thank you for your suggestion, numbered 2025.8 upon confirmed receipt, asking that ARIN make the commit messages to the Number Resource Policy Manual (NRPM) in GitLab more informative. We made several improvements to our publication process for Number Resource Policy Manual (NRPM) version 2026.1. Changes included: - Adding an individual commit for each policy included in a new NRPM version that is clearly labeled with the policy name. - Adding detail to the Changelog on the website to clarify which policy effected a change on each updated section of the NRPM. Additionally, we plan to add direct links to the web version of new policies to each commit when publishing future NRPM versions. Because the implemented and planned improvements satisfy your request, we are closing this suggestion. Thank you for participating in ARIN?s Consultation and Suggestion process. From info at arin.net Mon Mar 30 15:54:25 2026 From: info at arin.net (ARIN) Date: Mon, 30 Mar 2026 15:54:25 -0400 Subject: [ARIN-Suggestions] Suggestion 2026.4 is now closed Message-ID: <79ED06D9-969C-4E2C-891D-40D2462D2EF8@arin.net> A new response from ARIN has been posted for ACSP Suggestion 2026.4: Fix API permission checks on NET and this suggestion is now closed. You may find the original suggestion and the response from ARIN below. Regards, American Registry for Internet Numbers (ARIN) ----- ACSP Suggestion 2026.4: Fix API permission checks on NET https://www.arin.net/participate/community/acsp/suggestions/2026/2026-04/ Author: Richard Laager Submitted On: 03 March 2026 Description: If there are multiple ways to do the same thing, they should require the same permissions. They should not be inconsistent. Steps to reproduce: 1. Perform a Detailed Reassignment out of one of your NETs to another ORG. 2. Try to GET that NET by handle using your API key. Expected results: The GET succeeds. Actual results: The GET is rejected for lack of permission. Only an API key of the ?another ORG? can GET the NET. Additional discussion: - I created the NET in the first place. If I created it, surely I should be able to GET it (assuming nothing else has changed in the state of the world). - I can DELETE the NET. If I can DELETE something, surely I should be able to GET it. - I can GET the NET if I ask using the start and end IP address (via a mostSpecificNet call), but I cannot GET it by its handle. - Anyone, without authentication, can view the same information using the WHOIS protocol, by handle or by IP address. This is equivalent to a GET. - Accordingly, the correct permission check for a GET on a NET is ?return True?. - Similarly, if I can DELETE and then recreate something, I should be able to modify it using a PUT. So the PUT permission check should also allow those with access to the parent NET to PUT a (direct) child NET (since they could otherwise DELETE and recreate it with the same effect). Value to Community: The NRPM requires documenting reassignments. ARIN discontinued the email interface in favor of the API. Having a correctly working API is useful. Status: Closed ----- ARIN Response: Thank you for your suggestion, numbered 2026.4 upon confirmed receipt, requesting that ARIN change the API permissions checks for NETs. After discussing other methods for retrieving this information with other existing tools, as well as future development plants, it was concluded that changes to the current API permissions are unnecessary at this time. With the submitter?s agreement, this suggestion is now closed. Thank you for participating in ARIN?s Consultation and Suggestion Process. Regards, ARIN