From info at arin.net Fri May 6 16:18:07 2022 From: info at arin.net (ARIN) Date: Fri, 06 May 2022 16:18:07 -0400 Subject: [ARIN-Suggestions] Response for ACSP Suggestion 2022.13 Message-ID: <38882CB2-BB4C-44BC-9E74-7F5442E40FA1@arin.net> A response from ARIN has been posted for the 2022.11 suggestion. Find the original suggestion and our response below: ------ ACSP Suggestion 2022.13: Extend REST API to check Whois data https://www.arin.net/participate/community/acsp/suggestions/2022/2022-13/ Description: Extend RestAPI to check whois data, for not only resources you own or got reallocated, but everything else as well.For example, if someone reallocated /16 to my org I want to check who did it (in case I do not know, or just need for other purpose) I use NET parent handle and check it. Currently as Parent is not managed by my org I get 401 unauthorized, funny thing is that the same information can be collected using whois query and ARIN portal, but via API not, it forced us to use additional resources, services to receive needed information. Value to Community: By ?opening? RestAPI to check such things as parent of NET, etc, we community can easier find responsible organisations in case of hijacks, abuse contact. Find ?connection? between Organisation which reallocated the networks and who is using it. RIPE has open API, for some calls, I believe ARIN can do it as well. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.13 upon confirmed receipt, asking if ARIN could extend the REST API to check Whois data. We were glad to direct you to the functionality available using WhoisRWS to run the queries you need. WhoisRWS (XML based): https://www.arin.net/resources/registry/whois/rws/ Because there is existing functionality that meets the need described, we will be closing your suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Mon May 16 13:55:02 2022 From: info at arin.net (ARIN) Date: Mon, 16 May 2022 13:55:02 -0400 Subject: [ARIN-Suggestions] Response for ACSP Suggestion 2022.14 Message-ID: <0BFB688B-6E22-4A87-A4F6-D0F6490B23ED@arin.net> A response from ARIN has been posted for the 2022.14 suggestion. Find the original suggestion and our response below: ------ ACSP Suggestion 2022.14: Add Ability to Modify Existing RPKI ROA https://www.arin.net/participate/community/acsp/suggestions/2022/2022-14/ Description: Add modify function on ARIN site for existing RPKI ROA, especially ROA with multiple prefixes in one ROA entry. Value to Community: Currently with ARIN ROA, there is no way to modify them once they are created. ROA with an upcoming expiration date requires it to be deleted and re-added because it is not possible to modify the ROA expiration date in order to extend the ROA. It would reduce error if we could modify a ROA instead of having to delete it and add it again when they are close to expiring. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.14 upon confirmed receipt, asking that ARIN add functionality to allow customers to modify RPKI ROAs so that they do not need to be deleted and re-added when they are pending expiration. ARIN is already developing functionality that will automatically re-roll ROAs to reset their expiration date. This new feature will update the end validity date prior to expiration without any action from the customer. We are closing this suggestion because you have confirmed that this alternate solution will satisfy the spirit of your request. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN)