[ARIN-Suggestions] Two Suggestions are now closed; one Suggestion has a new response

[ARIN]

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.