From info at arin.net Mon Mar 7 15:32:34 2022 From: info at arin.net (ARIN) Date: Mon, 07 Mar 2022 15:32:34 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion and Responses Message-ID: One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). It is in review and pending response. One previous suggestions have been reviewed and pending implementation, with our response below. 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 pending ---------- ACSP Suggestion 2022.2: Operational Support for Ghostbusters RPKI records per RFC 6493 https://www.arin.net/participate/community/acsp/suggestions/2022/2022-02/ Description: Please support creation, maintenance, and publication of Ghostbusters RPKI records per RFC 6493 Value to Community: Would allow for contacting relevant parties to debug operational RPKI issues. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.2 upon confirmed receipt, asking that ARIN provider operational support for Ghostbusters RPKI records per RFC 6493. We agree that Support for Ghostbusters records in the ARIN repository gives organizations more control over the contact information they choose to share in the RPKI infrastructure, and we will schedule this for future development. This suggestion will remain open pending implementation. Thank you for participating in ARIN?s Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Thu Mar 10 09:31:29 2022 From: info at arin.net (ARIN) Date: Thu, 10 Mar 2022 09:31:29 -0500 Subject: [ARIN-Suggestions] Response to 2021.27: Add inet-num to ARIN Authenticated IRR Message-ID: ACSP Suggestion 2021.27: Add inet-num to ARIN Authenticated IRR https://www.arin.net/participate/community/acsp/suggestions/2021/2021-27/ Description: In previous requests years ago, we could request an inet-num to set geolocation that doesn?t match the RIR address space physical location. Since the use of inet-num is being depreciated; we are requesting ARIN revisit the deprecation of inet-num as a way to centralize geolocation assignments which third party geolocation services providers could use as a geolocation source. Value to Community: This will help stability and centralization that 3rd party geolocation can use as a dependable source for geolocation variances. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2021.27 upon confirmed receipt, requesting that ARIN add inetnum: objects to the Authenticated IRR for the purpose of publishing geolocation data. After investigating the usage of inetnum: objects, prior to the creation of the ARIN authenticated IRR, it was found usage of inetnum: was extremely limited, and inclusion of geolocation coordinates was not detected. This factored into our original decision to discontinue support for inetnum: objects when the ARIN authenticated IRR was created. We researched other RIRs, and 3rd party IRR operator databases for inetnum: objects populated with geo coordinates, the count ranged from statistically insignificant to zero. While discussing this suggestion with the submitter, alternatives for publishing this data were presented, including but not limited to, using a remark in an existing route: object populated with geolocation data or establishing an RFC8805 compliant Self-Published IP Geolocation Feed, both mitigate the need to restore support, create and maintain new inetnum: objects. As there are alternative ways available to publish geolocation data that do not necessitate restoring inetnum: to the ARIN IRR, we are not going to pursue development of this suggestion. Thank you for participating in ARIN?s Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Tue Mar 15 12:49:46 2022 From: info at arin.net (ARIN) Date: Tue, 15 Mar 2022 12:49:46 -0400 Subject: [ARIN-Suggestions] New Responses for ACSP Suggestions 2022.7 and 2022.8 Message-ID: <51DA7410-A59E-462F-ADE3-1A10A9F3FD60@arin.net> 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)