ACSP Suggestion 2025.9: ARIN RPKI Create, Delete and List API End-Point Enhancements
Suggestion
Author: Chuck Hauge
Submitted On: 24 November 2025
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.
Timeframe: Not specified
Status: Confirmed Updated: 05 December 2025