From info at arin.net Thu Jan 6 11:38:07 2022 From: info at arin.net (ARIN) Date: Thu, 06 Jan 2022 11:38:07 -0500 Subject: [ARIN-Suggestions] Response to 2021.28: Add fido2 Authentication to ARIN Login Message-ID: <73FF09F7-E9F9-452D-B478-ECBC625B2175@arin.net> On 6 January, we issued our response to ACSP 2021.28, which was received on 27 December 2021: Thank you for your suggestion, numbered 2021.28 upon receipt, requesting that ARIN offer Web Authentication (WebAuthn) and FIDO2 security key support. This suggestion appears to be a duplicate of both ACSP 2021.2: Offer Web Authentication (WebAuthn) and FIDO2 Security Key Support and ACSP 2019.14: Implement FIDO2 (WebAuthn) for ARIN Online. We agree that FIDO2 provides additional security and is rapidly gaining traction as an authentication method and would be a good addition to ARIN Online. We are currently reviewing our roadmap to determine when this work can be scheduled. These suggestions will remain open while we determine placement on our development roadmap. The full text of the suggestion is available below and at: https://www.arin.net/participate/community/acsp/suggestions/2021/2021-28/ Description: Add fido2 authentication for secure login using security keys and smart cards. Value to Community: This adds a great additional layer of security for all users and organizations that deploy FIDO 2 capable security keys. These security keys are generally more secure than traditional time-based OTP algorithms due to the tamper resistant nature of the device. Timeframe: Not specified Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jan 14 15:00:40 2022 From: info at arin.net (ARIN) Date: Fri, 14 Jan 2022 15:00:40 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestions Message-ID: Three new suggestions were recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Two are in review and pending response, and the third has been closed as out of scope. ACSP Suggestion 2022.1: Change Nomenclature Regarding Points of Contact https://www.arin.net/participate/community/acsp/suggestions/2022/2021-01/ Description: Contact information objects (?POCs?) should not be referred to as ?POCs? because that could also mean ?person of color?, effectively perpetuating racism to Blacks. Please rename ?POC? to something else. Value to Community: Makes ARIN community more inclusive Timeframe: Not specified Response Pending ACSP Suggestion 2022.2: Operational Support for Ghostbusters RPKI records per RFC 6493 https://www.arin.net/participate/community/acsp/suggestions/2022/2021-02/ Description: Please support creation, maintenance, and publication of Ghostbusters RPKI records per RFC 6493 Value to Community: Would allow for contacting relevant parties to debug operational RPKI issues. Timeframe: Not specified Response Pending ACSP Suggestion 2022.3: Contact Information on Domains https://www.arin.net/participate/community/acsp/suggestions/2022/2021-03/ Description: Re-evaluate the process and consequences of failing to respond, validate or update WHOIS contact information on domains Value to Community: Currently, if an email is missed and contact information isn?t validated or updated the domain name is locked. In certain cases, where all email accounts required to validate and resolve the issues are of the domain in question. Registrars force users to engage in a lengthy process that can take up to 72 hours. This is untenable as financial harm is brought upon business over an assumption that a domain, that was once already purchased, and validated as owned by a real person is no longer the case, purely on the passage of time. It?s far to easy to miss or mischaracterize these emails by office staff. The concept that somehow a domain, owned by a business with no changes required to it?s contact information somehow is invalidated by default is ridiculous. At the very least, registrars should have the flexibility to enable the domain on a temporary basis to enable the exact DNS records that were working before the hold to allow communications to email accounts configured under that domain and required to resolve any issues. Timeframe: Not specified Response: Thank you for your suggestion, numbered 2022.3 on confirmed receipt, asking that ARIN re-evaluate the process and consequence of failing to update or validate Whois contact information. Your suggestion specifies this as an issue related to management of domain names, and because that data is not part of ARIN?s Whois this is not an issue under our control. This is a matter for the domain registry based on the details you provided. We are closing this suggestion as Out of Scope. Regards, American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Tue Jan 18 16:19:18 2022 From: info at arin.net (ARIN) Date: Tue, 18 Jan 2022 16:19:18 -0500 Subject: [ARIN-Suggestions] Response to ACSP Suggestion 2021.16: Add New Optional Legal Service Point of Contact Message-ID: <3BB05AE1-21E0-4CCD-A8B4-226162914DE0@arin.net> Thank you for your suggestion, numbered 2021.16 on confirmed receipt, asking that we add a new optional Legal Point of Contact field for organizations. After reviewing your suggestion, we have determined that maintaining a Legal Point of Contact field is beyond the scope of the core Whois service. However, registrants have the ability to include legal-related contact information in the Public Comments field if they wish to share this optional information. Because the existing Public Comments field is available for registrants to provide this type of optional information, we are closing your suggestion. We thank you for your participation in ARIN?s Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Wed Jan 19 16:26:09 2022 From: info at arin.net (ARIN) Date: Wed, 19 Jan 2022 16:26:09 -0500 Subject: [ARIN-Suggestions] Response to ACSP Suggestion 2022.01: Change Nomenclature Regarding Points of Contact Message-ID: <17E44F51-49CA-46DF-8E0C-58AF94EC6FB7@arin.net> Original Suggestion Text Author: Anonymous??? Submitted On: 05 January 2022 Description: Contact information objects (?POCs?) should not be referred to as ?POCs? because that could also mean ?person of color?, effectively perpetuating racism to Blacks. Please rename ?POC? to something else. Value to Community: Makes ARIN community more inclusive Timeframe: Not specified URL:?https://www.arin.net/participate/community/acsp/suggestions/2022/2022-01/ -------- ARIN Comment Thank you for your suggestion, numbered 2022.01 upon confirmed receipt, asking that ARIN consider renaming our contact information objects to something other than ?POC? to be more inclusive in our language. ?POC? as an acronym for Point of Contact is a term that predates ARIN?s formation, and which can be found in?https://datatracker.ietf.org/doc/html/rfc1325. However, it is clear the term ?POC? has a variety of alternative associations, and as such, could be confusing to individuals who are not familiar with our use of that term. This is a timely point to raise because ARIN has been evaluating the impact of acronyms and jargon as a potential barrier to a common and consistent understanding of policies and procedures for our community. It is our goal to create an ?easy to understand? and efficient customer experience, and this includes using clear and unambiguous language. Once we have developed guidelines for appropriate jargon usage in our communications (planned for later in 2022), we will provide them to the community for their review. As it pertains to the use of the term ?POC?, we will start the process of transitioning our documentation to reference Contact types, rather than ?POC? in Q1 2022, and we will make the necessary changes to our ARIN Online application to update this terminology as the opportunity arises.? Because work can begin now to address this suggestion, it will be closed as ?in progress?. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN)