[ARIN-Suggestions] Two Suggestions are now closed

[ARIN]

New responses from ARIN have been posted for the following suggestions, and these suggestions are now closed. You may find the original suggestions and the responses from ARIN below.

2025.9: ARIN RPKI Create, Delete and List API End-Point Enhancements
2026.1: Add Support for DNSSEC DS Records to be Automatically Updated

Regards,
American Registry for Internet Numbers (ARIN)

-----------

2025.9: ARIN RPKI Create, Delete and List API End-Point Enhancements
https://www.arin.net/participate/community/acsp/suggestions/2025/2025-09/

Author: Chuck Hauge   

Description:

ARIN RPKI Create, Delete and List API End-Point Enhancements

When creating a ROA, the ROA Handle should include human readable data along with the hash. The IP, CIDR mask, origination ASN and max length should be included:

[hash] ! [IP] ! [CIDR mask] ! [ASN] ! [ML]

Sample: 1234567890abcdefghijklm ! [IP] ! 24 ! 20115 !

With this new enhanced ROA Handle, the list and delete ROA end-points will require the new handle format with the human-readable data. In theory both should be able to co-exist, and will get replaced when renewed.

Also, included in the list end-point output should be the ORGID.

Further, the delete ROA end-point should require the ORGID in URL line for more verification.

Value to Community: The purpose of these enhancements provides a user when removing ROAs a visual inspection of what ROA is being removed, and a higher level of verification that the ORGID intended to have the ROA removed from is accurate. The addition of the ORGID is for organizations that have multiple ORGIDs for easy identification of what ORGID an ROA belongs to.

Status: Closed

ARIN Comment:

Thank you for your suggestion, numbered 2025.9 upon confirmed receipt, requesting ARIN to make enhancements to the RPKI API endpoints for Create, Delete, and List.

Our RPKI development road map includes new features and enhancements to the RPKI services we currently provide to our customers. These changes will include updates to the ARIN Online interface and the Reg RWS API endpoint.

We will review the requested enhancements in this suggestion when the existing roadmap items are added to the development schedule.

Your suggestion has been referred to our internal process for prioritization and implementation planning and is now closed. Thank you for participating in ARIN’s Consultation and Suggestion Process.

-----------------

2026.1: Add Support for DNSSEC DS Records to be Automatically Updated
https://www.arin.net/participate/community/acsp/suggestions/2026/2026-01/

Author: Brandon Applegate   

Description:

Add support for DNSSEC DS records to be automatically updated. This is covered in RFCs 7344/8078/9615. This project tracks orgs that support this already:

https://github.com/oskar456/cds-updates

Value to Community: Enables fully automatic key rollovers, no need to use ARIN Web interface to manually update DS records.

Status: Closed

ARIN Comment:

Thank you for your suggestion, numbered 2026.1 upon confirmed receipt, requesting that ARIN add support for DNSSEC Delegation Signer (DS) records to be automatically updated. 

We agree that this would be a beneficial improvement, noting that it will require development effort to add this capability to our provisioning system. We will add it to our list of service improvements pending prioritization. 

Your suggestion has been referred to our internal process for prioritization and implementation planning and is now closed. Thank you for participating in ARIN’s Consultation and Suggestion Process.