From info at arin.net Tue Feb 4 11:36:18 2020 From: info at arin.net (ARIN) Date: Tue, 4 Feb 2020 11:36:18 -0500 Subject: [ARIN-Suggestions] Now Closed - ACSP 2019.23: Smart Cursor in Multi-factor Authentication Message-ID: <6c44c702-8020-7d56-61e5-0c622ea93dd2@arin.net> On 4 February, we closed ACSP 2019.23 with the following response: Thank you for your suggestion, numbered 2019.23 on confirmed receipt, asking that we automatically place the cursor in the first active field for multi-factor authentication. We have completed this work with our most recent deployment. Because this work has been completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. The full text of the suggestion and its history are available at: https://www.arin.net/vault/participate/acsp/suggestions/2019-23.html Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Tue Feb 4 11:37:52 2020 From: info at arin.net (ARIN) Date: Tue, 4 Feb 2020 11:37:52 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2020.3: Support RFC 8183 Message-ID: On 4 February we issued the following response to ACSP 2020.3: Support RFC 8183: Thank you for your suggestion, numbered 2020.3 upon confirmed receipt, that we should align our standards for setting up delegated RPKI with RFC 8183. We agree that this is a good suggestion and we are adding it to our list of features to include in our future RPKI improvements. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. The full text of the suggestion is available below, or at: https://www.arin.net/participate/community/acsp/suggestions/2020-3/ Description: Support RFC 8183 Value to Community: ARIN?s delegated RPKI currently uses a non-standard key exchange format. ARIN standards for setting up delegated RPKI. hould align with the standards established RFC 8183. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Mon Feb 10 15:35:17 2020 From: info at arin.net (ARIN) Date: Mon, 10 Feb 2020 15:35:17 -0500 Subject: [ARIN-Suggestions] Two New ACSP Suggestions - 2020.4: Web GUI for IRR & 2020.5: Service Availability Page Message-ID: <3c3a85b6-6a67-436c-95b7-fbd0f759119e@arin.net> We received two new ACSP suggestions, numbered 2020.4 and 2020.5 Upon confirmed receipt.? We are currently developing responses to both suggestions. 2020.4: Web GUI for ARIN IRR https://www.arin.net/participate/community/acsp/suggestions/2020-4/ Description: ARIN IRR should have a Web UI to make it easier to use and also usable over an encrypted protocol. Value to Community: There is currently an issue with the usability of the ARIN IRR due to the email interface and the manual process to get a PGP key added. A web UI to create/delete/edit route(6)/as-set/aut-num objects would greatly simplify the use of the IRR. 2020.5: Service Availability Page https://www.arin.net/participate/community/acsp/suggestions/2020-5/ Description: ARIN should create and maintain a publicly available status page for their services. This status page should reflect the current operational status of ARIN?s services including but not limited to ARIN Online, all aspects of RPKI, Whois, RDAP, IRR, Regrws, hostmaster email, DNS, and all aspects of OTE. Ideally, the status page would reflect each service component individually with a colored indicator such as red for complete service outage, yellow for service degradation, and green for service operating normally. Additionally, the status page should link to publicly available post-incident reports. Value to Community: As ARIN has both planned and unplanned outages, a status page provides the community which is dependent on ARIN for technical services a quick method to determine information necessary for troubleshooting operational issues, especially during non-business hours when ARIN plans most of its scheduled maintenance. This status page would also provide the community transparency into ARIN?s technical operations, earning trust and building confidence for those dependent on ARIN for their technical needs. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Tue Feb 11 14:58:46 2020 From: info at arin.net (ARIN) Date: Tue, 11 Feb 2020 14:58:46 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2020.2: RESTful Interface for IRR Message-ID: <732ee93b-fb9a-8b60-c55a-56dc7c579031@arin.net> On 10 February we issued the following response to ACSP 2020.2: RESTful Interface for IRR: Thank you for your suggestion, numbered 2020.2 upon confirmed receipt, that we should have a RESTful interface for our new IRR that is compatible with RADb. As we continue to develop this service, ARIN will strive to ensure compatibility with other Internet Routing Registries (IRRs) but we cannot guarantee compatibility with any one specific IRR. ARIN will develop its restful interface in accordance with current specifications and best practices. Thank you for your participation in the ARIN Consultation and Suggestion Process. Your suggestion will remain open as we define features and continue our work on the new ARIN IRR through the end of 2020. The full text of the suggestion is available below, or at: https://www.arin.net/participate/community/acsp/suggestions/2020-2/ Description: ARIN IRR should have a restful interface compatible with RADb. Value to Community: For people who use RADb will not have to write new code to use the ARIN IRR making the transition easier for the community at large. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Tue Feb 18 15:52:40 2020 From: info at arin.net (ARIN) Date: Tue, 18 Feb 2020 15:52:40 -0500 Subject: [ARIN-Suggestions] Two ACSP responses issued Message-ID: We issued responses for two suggestions today. 1. ACSP 2020.1: RFC 8181-Compliant Publication Service for Delegated RPKI https://www.arin.net/participate/community/acsp/suggestions/2020-1/ Thank you for your suggestion, numbered 2020.1 on confirmed receipt, asking that we offer an RFC8181 compliant RPKI Publication Service for members running Delegated RPKI. We agree that offering RPKI publication as a service to customers would provide benefit to those who wish to run delegated RPKI. We are closely following emerging initiatives and will be looking to leverage existing relevant work where possible.? This suggestion will remain open for prioritization and inclusion on our future work plan. Thank you for participating in the ARIN Consultation and Suggestion Process. *** ?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. Timeframe: Not specified 2. ACSP 2020.4: Web GUI for ARIN IRR https://www.arin.net/participate/community/acsp/suggestions/2020-4/ That you for your suggestion, numbered 2020.4 upon confirmed receipt, that we provide web UI available over an encrypted protocol for our IRR. We are currently working to develop a new IRR service which will have a web UI. This UI? will be available over HTTPS transport which is encrypted.? We are scheduled to have this service available to ARIN customers by the end of Q2 of 2020. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until work is completed. *** ?Description: ARIN IRR should have a Web UI to make it easier to use and also usable over an encrypted protocol. Value to Community: There is currently an issue with the usability of the ARIN IRR due to the email interface and the manual process to get a PGP key added. A web UI to create/delete/edit route(6)/as-set/aut-num objects would greatly simplify the use of the IRR. Timeframe: Not specified Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Wed Feb 26 16:45:31 2020 From: info at arin.net (ARIN) Date: Wed, 26 Feb 2020 16:45:31 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2020.5: Service Availability Page Message-ID: <2811d2b5-9b8f-e40a-b635-1f273155cfab@arin.net> On 25 February we issued the following response to ACSP 2020.5: Service Availability Page: Thank you for your suggestion, numbered 2020.5 on confirmed receipt, asking that we create and maintain a public page that provides the status of our services. We agree this would be beneficial improvement and will place it on our list of future improvements so that it can be prioritized. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. The full text of the suggestion is available below, or at: https://www.arin.net/participate/community/acsp/suggestions/2020-5/ Description: ARIN should create and maintain a publicly available status page for their services. This status page should reflect the current operational status of ARIN?s services including but not limited to ARIN Online, all aspects of RPKI, Whois, RDAP, IRR, Regrws, hostmaster email, DNS, and all aspects of OTE. Ideally, the status page would reflect each service component individually with a colored indicator such as red for complete service outage, yellow for service degradation, and green for service operating normally. Additionally, the status page should link to publicly available post-incident reports. Value to Community: As ARIN has both planned and unplanned outages, a status page provides the community which is dependent on ARIN for technical services a quick method to determine information necessary for troubleshooting operational issues, especially during non-business hours when ARIN plans most of its scheduled maintenance. This status page would also provide the community transparency into ARIN?s technical operations, earning trust and building confidence for those dependent on ARIN for their technical needs. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Fri Feb 28 11:38:31 2020 From: info at arin.net (ARIN) Date: Fri, 28 Feb 2020 11:38:31 -0500 Subject: [ARIN-Suggestions] New ACSP 2020.6: Legacy Resource Statistics Message-ID: <8244f467-0f5c-28e8-256a-7b868e189deb@arin.net> On 28 February, we received a new suggestion, numbered 2020.6 upon confirmed receipt, asking that we publish relevant statistics about legacy resources for the use of policy and research analysts. This suggestion is currently being reviewed and we will issue our response when it is available.? You can view the suggestion at: https://www.arin.net/participate/community/acsp/suggestions/2020-6/ Regards, American Registry for Internet Numbers (ARIN)