From info at arin.net Mon May 6 13:43:49 2019 From: info at arin.net (ARIN) Date: Mon, 6 May 2019 13:43:49 -0400 Subject: [ARIN-Suggestions] Closure of ACSP 2019.7: Add Point of Contact (POC) notification email Message-ID: On 10 April, we received a new suggestion, numbered 2019.7 upon confirmed receipt, that recommended add optional notification email fields to Point of Contact records.? After internal review, we have notified the author that we will not be moving forward with this suggestion. The full text of the suggestion and our response to the author are available below, or at: https://www.arin.net/vault/participate/acsp/suggestions/2019-7.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) *** Description: POC notification email For all POCs add an optional field of notification email, which can contain one or more email addresses. The notification email or emails will not be publicly published (this is similar to the old DMR POCs). Whenever ARIN emails a POC, ARIN will send email to the publicly published email, as well as all the notification emails. Ideally, there would also be a way to mark if the email addresses of ARIN Online accounts that are linked to a POC should: ??? always be included as a notification email ??? specify a sub-set of linked account emails to be included ??? they are removed when an account is un-linked Value to Community: This will increase the reliability of email communication between ARIN and resources holders by exposing an email address that is not subject to public scraping and spam. This is very important given 2017-12 notification to unwitting POCs will only be sent to the public email of that POC. Such an email may simply be discarded by the noc, billing, or abuse teams, and not directed to the IP addressing team or those that have a relationship with ARIN." Timeframe: Not specified Response: Thank you for your suggestion, numbered 2019.7 upon confirmed receipt. As we understand it, this suggestion recommends expanding on the functionality available to customize email management on ARIN Online user accounts. It appears that much of this functionality already exists or is available to customers through their own email management systems, particularly as pertains to spam mitigation and email filtering. It is important to the community that organizations maintain accurate, publicly-available POCs, and it is incumbent on organizations to make sure that mail to those addresses is properly monitored and reviewed by their staff.? For these reasons we do not plan to put this suggestion on our development roadmap. Thank you for your participation in the ARIN Consultation and Suggestion Process. This suggestion is now closed. From info at arin.net Wed May 8 13:54:33 2019 From: info at arin.net (ARIN) Date: Wed, 8 May 2019 13:54:33 -0400 Subject: [ARIN-Suggestions] Response and Closure of ACSP 2019.9: PDP Improvements Message-ID: <945c1635-0d63-3632-cbfd-7bc297757efe@arin.net> On 2 May, we received a new suggestion, numbered 2019.9 upon confirmed receipt, that recommended edits and clarifications to the Petitions section of the Policy Development Process (PDP) in order to make the process clearer and more fair.?? After internal review, we have notified the author that we will refer this suggestion to the Board for consideration. The full text of the suggestion and our response to the author are available below, or at: https://www.arin.net/vault/participate/acsp/suggestions/2019-9.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) *** Description: PDP text for the petition process is not clear and need to be improved. In view of my experience in the recent petition, I see several issues: 1) The text doesn't mention if is natural or working days. The staff is interpreting it as natural days, and in that case it is extremely short, considering that the process need to be followed by people not just from the ARIN service region. In our case, was in the middle of a weekend and co-author country holidays. I will say that it should be either 7 or even 10 natural days (for each time frame), because it will be difficult to seeks "working days" in all the countries. I understand that people just need to say, if they support the petition "I support it", but this is not something that people do over the weekend, or even in the middle of the week they will give priority to respond within the deadline. What about vacation periods, which may be longer than 7 days. Should an exception deadline be considered at staff discretion if it happens within eastern, summer holidays, xmas, etc. ? 2) It is not clear either if the 5 days are for starting the petition or from start-to-end. It looks like it is 5 days to start the petition, then 5 days to get the support. Should be clearer. 3) It should be stated that co-authors also count for the number of petitioners, as they are community members. 4) I understand that in some cases, several participants from a single organization should be counted only as one, to prevent a single organization to make its own petition happening, but this should be enforced only in those cases. Otherwise, the PDP is for community members, and even within a single organization, there are different views, so all them should count. 5) Some community participants may not be affiliated, or they don't want to speak on behalf of its employeer (or not allowed to). So asking for their affiliation, except in the case indicated 4), should not be needed. Value to Community: Ensuring that the process is well understood and fair. Timeframe: Not specified *** Response: Thank you for your suggestion, numbered 2019.9 upon confirmed receipt. As we understand it, this suggestion recommends edits and clarifications to the Petitions section of the Policy Development Process (PDP) in order to make the process clearer and more fair. Given that changes to the PDP are made per direction of the ARIN Board of Trustees, this suggestion will be provided to the ARIN Board Chair, and it will be reviewed during the next periodic update to the PDP. Thank you for your participation in the ARIN Consultation and Suggestion Process.? This suggestion is now closed. From info at arin.net Tue May 14 13:31:54 2019 From: info at arin.net (ARIN) Date: Tue, 14 May 2019 13:31:54 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2019.10: CIDR Notation on ARIN-Issued Emails Message-ID: On 9 May, we received a new suggestion, numbered 2019.10 upon confirmed receipt, that ARIN use CIDR notation to display addresses in the arin-issued report emails. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-10/ *** Description: CIDR notation on ARIN-issued emails Value to Community: Easier to read than the current XXX.XXX.XXX.XXX-YYY.YYY.YYY.YYY e.g. change ?Add 204.10.185.0-204.10.185.255? to ?Add 204.10.185.0/24? I like to scan the list for the sizes of the blocks. Timeframe: Not specified *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 15 10:11:46 2019 From: info at arin.net (ARIN) Date: Wed, 15 May 2019 10:11:46 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2019.11: ROA Search Functionality Message-ID: On 14 May, we received a new suggestion, numbered 2019.11 upon confirmed receipt, that ARIN restore ROA search functionality. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-11/ *** Description: Bring Back ROA Search Functionality Value to Community: Easily find specific ROAs for prefixes without having to scroll through hundreds of pages. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu May 16 11:48:55 2019 From: info at arin.net (ARIN) Date: Thu, 16 May 2019 11:48:55 -0400 Subject: [ARIN-Suggestions] New ACSP 2019.12: Changes to Special Policy Actions Section of PDP Message-ID: <577357c7-41d7-c83f-23c5-8828aeb20158@arin.net> On 15 May, we received a new suggestion, numbered 2019.12 upon confirmed receipt, that ARIN make clarifying changes to the special policy actions section of the Policy Development Process. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-12/ *** Description: Add additional detail to section 10 (Special Policy Actions) of the PDP Value to Community: Section 10 of the PDP (Special Policy Actions) is a seldom used section, but when it is used it is usually a significant action. The current PDP contains limited detail about the processes the community, advisory council, and board should go through when dealing with an suspended or emergency policy action. My suggestion is to add additional detail and process flow language to this section of the PDP using the recent suspension of the wait-list policy as valued input into how a suspended policy may be updated. My hope is that the additional details gives the board, advisory council, and community a better road map of how a suspended or emergency policy will be reviewed and implemented. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu May 16 16:18:43 2019 From: info at arin.net (ARIN) Date: Thu, 16 May 2019 16:18:43 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2019.13: Make ARIN Services IPv6-only Message-ID: <15a43626-65af-7d70-64cf-b861b261692d@arin.net> On 16 May, we received a new suggestion, numbered 2019.13 upon confirmed receipt, that ARIN move toward making service available via IPv6-only. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-13/ *** Description: Encourage IPv6 Adoption by making ARIN on-line services increasingly IPv6 only. (Start with, say, the 6th of each month being IPv6-only day where ARIN on-line turns off it's A records and it's IPv4 address(es)). Beginning in 2020, additionally turn IPv4 off for the entire month of June. Beginning in 2021, add the month of December. In 2022, make it the last month of each quarter (March, June, September, December). Beginning in 2023, just turn off IPv4 for all of ARIN on-line. Value to Community: This can send a clear message to ARIN customers that IPv6 is the future of the internet and help them understand the need to deploy IPv6 within their network. By ramping up to ARIN on-line being an IPv6-only web site ver the course of a few years, people have time to deploy and test, but starting in 2023, even if you want to transfer in more IPv4, you should be able to get to ARIN via IPv6 to do so. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 22 08:53:08 2019 From: info at arin.net (ARIN) Date: Wed, 22 May 2019 08:53:08 -0400 Subject: [ARIN-Suggestions] Response and Closing of ACSP 2019.10: CIDR Notation in ARIN-issued emails Message-ID: <523ebb53-0ebc-78e1-aae0-a7385081019d@arin.net> On 21 May, we issued a closing response to ACSP 2019.10: CIDR Notation in ARIN-issued emails. Please see the full text of our response and the suggestion below or online at: https://www.arin.net/vault/participate/acsp/suggestions/2019-10.html Response: Thank you for your suggestion, numbered 2019.10 upon confirmed receipt, suggesting that we use CIDR notation in the arin-issued report to make it easier to scan for block sizes. The format of the arin-issued report was defined through a Community Consultation (see:https://www.arin.net/vault/announcements/2009/20090102.html). We have reason to believe that community members process this report through scripting, and that to make a change to the format of the report would create problems for those users. Out of an abundance of caution, we will not be making a change to the format of the report at this time. Thank you for your participation in the ARIN Consultation and Suggestion Process.? This suggestion is now closed. Suggestion: Description: CIDR notation on ARIN-issued emails Value to Community: Easier to read than the current XXX.XXX.XXX.XXX-YYY.YYY.YYY.YYY e.g. change ?Add 204.10.185.0-204.10.185.255? to ?Add 204.10.185.0/24? I like to scan the list for the sizes of the blocks. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 22 09:31:15 2019 From: info at arin.net (ARIN) Date: Wed, 22 May 2019 09:31:15 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2019:11: ROA Search Functionality Message-ID: <1fc41c86-96fb-fb3e-4416-54764940c4ca@arin.net> On 21 May, we issued a response to ACSP 2019.11: ROA Search Functionality. Please see the full text of our response and the suggestion below or online at: https://www.arin.net/participate/community/acsp/suggestions/2019-11/ Response: Thank you for your suggestion, numbered 2019.11 upon confirmed receipt, requesting that we restore ROA search functionality. Prior to 2 March, users were able to find a ROA by prefix using the search functionality in their browser.? This was not a feature of ARIN Online, and currently it is not possible due to changes to the user interface. We are aware this is a problem for users, and we are in the process of developing functionality so users can search for ROAs by Origin AS and prefix. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. Suggestion: Description: Bring Back ROA Search Functionality Value to Community: Easily find specific ROAs for prefixes without having to scroll through hundreds of pages. Timeframe: Not specified Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 22 15:10:20 2019 From: info at arin.net (ARIN) Date: Wed, 22 May 2019 15:10:20 -0400 Subject: [ARIN-Suggestions] New ACSP 2019.14: Implement FIDO2 (WebAuthn) for ARIN Online Message-ID: <1e05ad21-2a1b-4a3e-82d9-2dfa2fc489e2@arin.net> On 17 May, we received a new suggestion, numbered 2019.14 upon confirmed receipt, that ARIN implement FIDO2 (WebAuthn) for ARIN Online as an optional authenticator to eliminate passwords entirely.. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-14/ *** Description: Implement FIDO2 (WebAuthn) for ARIN Online as an optional authenticator to eliminate passwords entirely. Value to Community: Passwords and OTP can be complex, and often result in reluctance to implement proper protections of ARIN Online accounts. Implementation of WebAuthn and FIDO2 can offer an alternative to not only eliminate passwords but at the same time provide strong authentication (as Microsoft Windows 10 and Azure does with FIDO2 authenticaters). Note that best practice is always to ensure that you have a backup Security Key in place, so allowing more than one key is likely important allowing one to place the backup key in a secure location. FWIW, this was mentioned at the mic at the recent meeting, but as I did not write down the name of the proposer, I cannot give proper credit. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 29 14:29:14 2019 From: info at arin.net (ARIN) Date: Wed, 29 May 2019 14:29:14 -0400 Subject: [ARIN-Suggestions] Response and Closing of ACSP 2019.12: Changes to Special Policy Actions Section of PDP Message-ID: <4a900499-2083-c6bd-b6de-3ae10ff451e6@arin.net> On 29 May, we issued a closing response to ACSP 2019.12: Changes to Special Policy Actions Section of PDP. Please see the full text of our response and the suggestion below or online at: https://www.arin.net/vault/participate/acsp/suggestions/2019-12.html Response: Thank you for your suggestion, numbered 2019.12 upon confirmed receipt. As we understand it, this suggestion recommends edits and clarifications to the Special Policy Actions section of the Policy Development Process (PDP) in order to make the process clearer and provide a better roadmap for implementation of this type of event. Given that changes to the PDP are made per direction of the ARIN Board of Trustees, this suggestion will be provided to the ARIN Board Chair, and it will be reviewed during the next periodic update to the PDP. Thank you for your participation in the ARIN Consultation and Suggestion Process.? This suggestion is now closed. Suggestion: Description: Add additional detail to section 10 (Special Policy Actions) of the PDP Value to Community: Section 10 of the PDP (Special Policy Actions) is a seldom used section, but when it is used it is usually a significant action. The current PDP contains limited detail about the processes the community, advisory council, and board should go through when dealing with an suspended or emergency policy action. My suggestion is to add additional detail and process flow language to this section of the PDP using the recent suspension of the wait-list policy as valued input into how a suspended policy may be updated. My hope is that the additional details gives the board, advisory council, and community a better road map of how a suspended or emergency policy will be reviewed and implemented. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed May 29 14:30:19 2019 From: info at arin.net (ARIN) Date: Wed, 29 May 2019 14:30:19 -0400 Subject: [ARIN-Suggestions] Response and Closing of ACSP 2019.13: Make ARIN Services IPv6-only Message-ID: On 29 May, we issued a closing response to ACSP 2019.13: Make ARIN Services IPv6-only. Please see the full text of our response and the suggestion below or online at: https://www.arin.net/vault/participate/acsp/suggestions/2019-13.html Response: Thank you for your suggestion, numbered 2019.13 upon confirmed receipt. As we understand it, this suggestion recommends ARIN begin a staged approach to making our services IPv6-only. We have historically worked to make sure that our services are available over both IPv4 and IPv6 wherever possible, and we will continue to do so as long as both protocols remain in common use. Thank you for your participation in the ARIN Consultation and Suggestion Process.? This suggestion is now closed. Suggestion: Description: Encourage IPv6 Adoption by making ARIN on-line services increasingly IPv6 only. (Start with, say, the 6th of each month being IPv6-only day where ARIN on-line turns off it's A records and it's IPv4 address(es)). Beginning in 2020, additionally turn IPv4 off for the entire month of June. Beginning in 2021, add the month of December. In 2022, make it the last month of each quarter (March, June, September, December). Beginning in 2023, just turn off IPv4 for all of ARIN on-line. Value to Community: This can send a clear message to ARIN customers that IPv6 is the future of the internet and help them understand the need to deploy IPv6 within their network. By ramping up to ARIN on-line being an IPv6-only web site ver the course of a few years, people have time to deploy and test, but starting in 2023, even if you want to transfer in more IPv4, you should be able to get to ARIN via IPv6 to do so. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri May 31 12:48:15 2019 From: info at arin.net (ARIN) Date: Fri, 31 May 2019 12:48:15 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2019.14: Implement FIDO2 (WebAuthn) for ARIN Online Message-ID: <2932195f-c0f8-4a41-e8ea-e066deabd0c0@arin.net> On 29 May, we issued a response to ACSP 2019.14: Implement FIDO2 (WebAuthn) for ARIN Online. Please see the full text of our response and the suggestion below or online at: https://www.arin.net/participate/community/acsp/suggestions/2019-14/ Response: Thank you for your suggestion, numbered 2019.14 upon confirmed receipt, that ARIN implement FIDO2 (WebAuthn) for ARIN Online. This suggestion will remain open for consideration alongside other potential improvements to our ARIN Online login functionality for inclusion on our future work plan. Suggestion: Passwords and OTP can be complex, and often result in reluctance to implement proper protections of ARIN Online accounts. Implementation of WebAuthn and FIDO2 can offer an alternative to not only eliminate passwords but at the same time provide strong authentication (as Microsoft Windows 10 and Azure does with FIDO2 authenticaters). Note that best practice is always to ensure that you have a backup Security Key in place, so allowing more than one key is likely important allowing one to place the backup key in a secure location. FWIW, this was mentioned at the mic at the recent meeting, but as I did not write down the name of the proposer, I cannot give proper credit. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)