From info at arin.net Thu Nov 3 11:43:26 2022 From: info at arin.net (ARIN) Date: Thu, 03 Nov 2022 11:43:26 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestions and Responses Message-ID: <047CC744-15FB-43E1-AF8A-1F9BE18F434C@arin.net> Two new suggestions have been received (2022.26 and 2022.27), and responses from ARIN have been posted for both. You may find the new suggestions and latest responses from ARIN at the links below. Regards, American Registry for Internet Numbers (ARIN) ---------- 2022.26: Add Functionality to Assist Customers Transitioning From Hosted to Delegated RPKI https://www.arin.net/participate/community/acsp/suggestions/2022/2022-26/ Author: Michael Drzal Submitted On: 17 October 2022 Description: The choice of hosted or delegated RPKI is made at the organization level. If a customer chooses to switch from hosted to delegated RPKI, all ROAs are invalidated and the customer must recreate all of the ROAs in the new system. During the transition period, the prefixes are not protected from BGP hijacks. This becomes a bigger deal when there are hundreds of ROAs involved. In our case our largest org has 515 prefixes each with multiple ROAs. We intentionally slow the rate of change in ROAs to avoid having unwanted effects within global internet routing. At our current rate, it would take us 25 hours to create all of the new ROAs. This is less of a concern for organizations with 1-2 prefixes that could easily recreate their ROAs within seconds. It would be beneficial to allow customers to run hosted and delegated RPKI in the same org at the same time for the purpose of transitioning between the two modes. Value to Community: This would allow customers to switch between delegated and hosted RPKI without opening up their resources to route hijacks. Customers with a larger number of prefixes are the ones who are more likely to investigate moving to delegated RPKI, but they are also the ones most affected by this issue. Timeframe: Not specified Status: Open Updated: 02 November 2022 Response from ARIN: Thank you for your suggestion, numbered 2022.26 on confirmed receipt, requesting that ARIN add functionality to assist customers transitioning from hosted to delegated RPKI. We agree this feature has the potential to ease the transition between RPKI deployment types for organizations with large numbers of resources covered by ROAs. We will investigate the requirements to build this new feature and schedule it for future development. Your suggestion will remain open until implemented. Thank you for participating in the ARIN Consultation and Suggestion Process. ---------- 2022.27: Fee Implementation For ARIN Public Policy and Members Meetings https://www.arin.net/participate/community/acsp/suggestions/2022/2022-27/ Author: Anonymous Submitted On: 25 October 2022 Description: Charge a small amount ($100-300) for ARIN Meetings. Value to Community: This will reduce the quantity of fake Visa requests and reduce non-attendees registering for perks only, and not actually participating in the meetings. (Also allow no-fee registrations with a justification for students and those that do not have employer funding but should require an application and approval.) Timeframe: Not specified Status: Closed Updated: 02 November 2022 Response from ARIN: Thank you for your suggestion, numbered 2022.27 upon confirmed receipt, requesting that ARIN charge a minimal fee for in-person registration to attend ARIN Public Policy and Member Meetings while allowing for fee waivers for those with approved justification. Given that such a fee change would fall under the guidance of the ARIN Board of Trustees, this suggestion has been provided to the ARIN Board Chair for future consideration. Thank you for your participation in the ARIN Consultation and Suggestion Process. This suggestion is now closed. From info at arin.net Mon Nov 7 16:02:12 2022 From: info at arin.net (ARIN) Date: Mon, 07 Nov 2022 16:02:12 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestions and Responses Message-ID: <781556D6-DA5F-4C32-8981-0CDEA7F2E65B@arin.net> Two new suggestions have been received (2022.28 and 2022.29), and responses from ARIN have been posted for both. You may find the new suggestions and latest responses from ARIN at the links below. Regards, American Registry for Internet Numbers (ARIN) -------- 2022.28: Add Email as a Two-Factor Authentication Method https://www.arin.net/participate/community/acsp/suggestions/2022/2022-28/ Author: Al Whaley Submitted On: 3 November 2022 Description: Allow email for 2FA (two factor authentication) for accessing an ARIN account. Value to Community: Many of us are not allowed to use personal cell phones for professional work, a restriction that seems appropriate. Limiting authentication to cell phones is not professional. Using work emails is professional. Security is generally better with email than with SMS. At a minimum email should be an option for 2FA for accessing our ARIN accounts. Timeframe: Not specified Status: Open Updated: 7 November 2022 Response from ARIN: Thank you for your suggestion, numbered 2022.28 on confirmed receipt, requesting that ARIN allow email for two-factor authentication (2FA). ARIN will have four options for customers to set up 2FA on their ARIN Online accounts prior to 1 February 2023, when we require accounts to be secured: - Time-based One-time Password (TOTP) using an authenticator of your choice - Short Message Service SMS or Voice Call for customers within the ARIN service region - FIDO2/Passkey (available January 2023) We continue to receive input from customers for additional options, and plan to conduct a Community Consultation to assess support for continued development related to 2FA for ARIN Online accounts. Your suggestion will remain open pending the outcome of the consultation and any potential related development effort. Thank you for participating in the ARIN Consultation and Suggestion Process. --------- 2022.29: Allow Phone Numbers Outside of the ARIN Region to be Eligible for SMS Two-Factor Authentication https://www.arin.net/participate/community/acsp/suggestions/2022/2022-29/ Author: Andy Beverly Submitted On: 03 November 2022 Description: Enable non-ARIN mobile numbers for SMS 2-factor authentication Value to Community: This would enable administrators who have a mobile phone number outside of the ARIN region to be able to use SMS for 2-factor authentication. Timeframe: Not specified Status: Open Updated: 07 November 2022 Response from ARIN: Thank you for your suggestion, numbered 2022.29 on confirmed receipt, requesting that ARIN enable SMS for two-factor authentication (2FA) for customers who reside outside the ARIN service region. ARIN will have four options for customers to set up 2FA on their ARIN Online accounts prior to 1 February 2023, when we require accounts to be secured: - Time-based One-time Password (TOTP) using an authenticator of your choice - Short Message Service SMS or Voice Call for customers within the ARIN service region - FIDO2/Passkey (available January 2023) We continue to receive input from customers for additional options, and plan to conduct a Community Consultation to assess support for continued development related to 2FA for ARIN Online accounts. Your suggestion will remain open pending the outcome of the consultation and any potential related development effort. Thank you for participating in the ARIN Consultation and Suggestion Process.