ACSP Suggestion 2022.8: Atomic Update option for RPKI API

Suggestion

Author: Anonymous   
Submitted On: 07 March 2022

Description:

The ARIN API encourages serial updates which, in bulk, are not atomic.

There are situations where this is sub-optimal - such as RFC6382.

For multiple CRUD operations RPKI ROA and RPSL API Transactions should have the option to be committed atomically.

Value to Community: It would be more robust to be able to pre-stage all the database updates before committing them.

Timeframe: Not specified

Status: Closed   Updated: 22 August 2023

Tracking Information

ARIN Comment

22 August 2023

Thank you for your suggestion, numbered 2022.8 on confirmed receipt, requesting that we provide an option to commit atomic changes to the RPKI ROA and RPSL API. Development of this functionality was released on 13 May 2023.

Because this work is completed, we are closing this suggestion.

Thank you for participating in the ARIN Consultation and Suggestion Process.

15 March 2022

Thank you for your suggestion, numbered 2022.8 on confirmed receipt, requesting that we provide an option to commit atomic changes to the RPKI ROA and RPSL API. In cases where a customer needs to make multiple changes, having the ability to save changes in bulk rather than individually would make the process less cumbersome. We rely on customer input to help identify improvements and enhancements to ARIN services and agree this would be a useful feature added to the RPKI API. Our development calendar is fully booked for 2022, but we will include your suggestion on the list of features for consideration in our 2023 prioritization process.

Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented.