ACSP Suggestion 2022.12: Publish RSA/LRSA Status in Whois/RDAP
Suggestion
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 Updated: 09 October 2023
Tracking Information
ARIN Comment
9 October 2023
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.
30 June 2022
Thank you for your suggestion, numbered 2022.12 upon confirmed receipt, asking that ARIN include the registration services contract status of each number resource block in the public registry via Whois/RDAP. There are privacy concerns regarding listing the contract status per network managed under ARIN to Whois/RDAP records. However, we agree that it is operationally relevant to see what ARIN services are provided per network on a bulk basis. To fulfill this need, ARIN will create a daily report that will list the network and the type of service it receives from ARIN, Full Registry services vs Basic Legacy services.
This suggestion will remain open until we complete the work to make this report available and announce it to the community. Thank you for participating in the ARIN Consultation and Suggestion Process.
Regards,
American Registry for Internet Numbers (ARIN)