From info at arin.net Fri Feb 11 10:54:40 2022 From: info at arin.net (ARIN) Date: Fri, 11 Feb 2022 10:54:40 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestions Message-ID: Two new suggestions were recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). One has been reviewed and is pending implementation, and the other is in review and pending response. ---------- ACSP Suggestion 2022.4: ARIN Online - Display RSA/LRSA Status https://www.arin.net/participate/community/acsp/suggestions/2022/2022-04/ Description: Give ARIN Orgs the ability to see if their IP resources are covered by an L/RSA via the user dashboard. Value to Community: ARIN requires IP resources to be covered an L/RSA to use RPKI services and the ARIN authenticated IRR. Giving resource holders the ability to identify which, if any, need an L/RSA before signing up for RPKI and IRR services, and should limit the calls to the ARIN help desk requesting this information. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.4 on confirmed receipt, requesting that we display RSA/LRSA status on resources in ARIN Online so customers can check their resources to see if they are eligible to use ARIN?s authenticated Internet Routing Registry (IRR) and Resource Public Key Infrastructure (RPKI) services. We agree this is a beneficial improvement for both customers and staff and will prioritize it for implementation this year. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. ---------- ACSP Suggestion 2022.5: Alternative to API Token in REST calls https://www.arin.net/participate/community/acsp/suggestions/2022/2022-05/ Description: Alternative to sending API Token as URL parameter in REST calls. Either sending as POST form data or as an HTTP header field would be preferable as those should not tend to be logged in production systems. Some other implementations of REST interfaces are using X-CSRFToken in the HTTP header field. e.g. curl -H ?X-CSRFToken: $myToken? -X GET http:/my.fqdn/noun Value to Community: Logging systems often log the entire URL and hence unnecessarily expose the API token to anyone with access to and reading the logs. This could accidentally lead to a security incident caused by unauthorized access to ARIN resources from a valid hijacked token. Timeframe: Not specified Response Pending Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Wed Feb 23 14:21:53 2022 From: info at arin.net (ARIN) Date: Wed, 23 Feb 2022 14:21:53 -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. Two previous suggestions have been reviewed and pending implementation, with 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 Pending ---------- ACSP Suggestion 2022.6: Increase API Token Length https://www.arin.net/participate/community/acsp/suggestions/2022/2022-06/ Description: After stripping the ?API? and ?-? characters the token has only 16 characters, each character having 36 unique values. Double the current length to 32 variable characters. Value to Community: Longer token aligned to other API implementations will make the tokens more difficult to brute force. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.6 on confirmed receipt, requesting that we extend the length of API tokens to 36 characters to make them less susceptible to brute force attacks. We agree this would be a helpful change and increase the security of the API tokens. We will place this suggestion on the list for prioritization for the 2023 Engineering Roadmap. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. ---------- ACSP Suggestion 2022.5: Alternative to API Token in REST calls https://www.arin.net/participate/community/acsp/suggestions/2022/2022-05/ Description: Alternative to sending API Token as URL parameter in REST calls. Either sending as POST form data or as an HTTP header field would be preferable as those should not tend to be logged in production systems. Some other implementations of REST interfaces are using X-CSRFToken in the HTTP header field. e.g. curl -H ?X-CSRFToken: $myToken? -X GET http:/my.fqdn/noun Value to Community: Logging systems often log the entire URL and hence unnecessarily expose the API token to anyone with access to and reading the logs. This could accidentally lead to a security incident caused by unauthorized access to ARIN resources from a valid hijacked token. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.5 on confirmed receipt, requesting that we consider alternatives to sending the API token as a URL parameter in REST calls to improve security. We agree that a change of this type would improve security. In evaluating this suggestion, we have determined that making the change to send the API token as part of the HTTP header field would be the best solution as it will also allow ARIN to support this new feature as well as the current query parameter. We will place this suggestion on the list for prioritization for the 2023 Engineering Roadmap. 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) From info at arin.net Mon Feb 28 16:36:49 2022 From: info at arin.net (ARIN) Date: Mon, 28 Feb 2022 16:36:49 -0500 Subject: [ARIN-Suggestions] ACSP 2020.1: RFC8181-Compliant Publication Service for Delegated RPKI is now Closed Message-ID: <25A9A0B0-CBB1-4F26-94B0-2FC35B4BB40C@arin.net> ORIGINAL SUGGESTION LINK: https://www.arin.net/participate/community/acsp/suggestions/2020/2020-1/ Author: Alex Band? Submitted On: 08 January 2020 Description: Offer an RFC8181 compliant RPKI Publication Service for members running Delegated RPKI. Value to Community: Running Delegated RPKI offers considerable benefits to ARIN members who want to be operationally independent from the Hosted RPKI system that ARIN offers, for example because members require more automation than the hosted web interface and ARIN RPKI API offer, or because they need to manage ROAs for address space that is spread across multiple RIR regions. Delegated RPKI lets organisations create and manage their own Certificate Authority and ROAs, but publication of the cryptographic material can be outsourced to a third party, as specified in RFC 8181. ARIN already has extensive experience with hosting RPKI data and has all the required infrastructure. Because there is an existing contractual relationship between ARIN and members who use RPKI services, it makes ARIN an ideal candidate for offering RPKI publication as a service. LATEST RESPONSE FROM ARIN 28 February 2022 Thank you for your suggestion, numbered 2020.1 on confirmed receipt, requesting that we offer an RFC8181 compliant RPKI Publication Service for members running Delegated RPKI. With our latest release, we have deployed an RFC 8181 compliant RPKI Publication Service. Instructions for this option are available at: https://www.arin.net/resources/manage/rpki/delegated/#arin-publication-service-for-delegated-rpki. Because this work is completed, we are closing this suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: