[ARIN-Suggestions] New Responses for ACSP Suggestions 2022.7 and 2022.8

[ARIN]

Two responses from ARIN have been posted for the 2022.7 and 2022.8 suggestions. Find the original suggestions and our responses below:

---------

ACSP Suggestion 2022.7: IRR Transaction Log for RESTful API
https://www.arin.net/participate/community/acsp/suggestions/2022/2022-07/

Description: Although IRR email changes are slow, a validation and confirmation email was sent after the change was committed - so there was a record of the change. When using the API to make RPSL changes, the change is silent except for the updated record itself.

A transaction log is required of user’s org RPSL and RPKI object changes made via REST API or from within the associated account’s web interface.

If this feature exists currently within the REST API it is not documented in https://www.arin.net/resources/manage/irr/irr-restful/ and it’s not available in the web UI in the Downloads & Services section.

Value to Community: Logging of changes is good practice.

Timeframe: Not specified

Response from ARIN: Thank you for your suggestion, numbered 2022.7 on confirmed receipt, requesting that we make a transaction log available for RPSL changes made to the IRR using the REST API, which can be accessed via the API or within the associated account’s web interface. We agree this would be a helpful change and benefit customers using the IRR API. We rely on customer input to help identify improvements and enhancements to ARIN services. 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.

---------

ACSP Suggestion 2022.8: Atomic Update option for RPKI API
https://www.arin.net/participate/community/acsp/suggestions/2022/2022-08/

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

Response from ARIN: 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.

Regards,

American Registry for Internet Numbers (ARIN)