From info at arin.net Mon Apr 3 13:07:52 2017 From: info at arin.net (ARIN) Date: Mon, 3 Apr 2017 12:07:52 -0500 Subject: [ARIN-Suggestions] New ACSP 2017.6: Registrant Validation Remediation Proposal Message-ID: On 3 April, 2017, we received a new suggestion to the ARIN Consultation and Suggestion process. https://arin.net/participate/acsp/suggestions/2017-6.html Description: Registrant Validation Remediation Proposal: New policy/procedure using registrant transfer procedure to validate unvalidated registrants by asking that they "transfer" their blocks to themselves using existing processes. Value to Community: Reduction of unvalidated registrants and ongoing checksum/remediation to improve whois We will be evaluating this suggestion and issuing a formal response within the next 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Apr 3 16:37:57 2017 From: info at arin.net (ARIN) Date: Mon, 3 Apr 2017 15:37:57 -0500 Subject: [ARIN-Suggestions] New ACSP 2017.7: Replacement of Jabber for Remote Participation Message-ID: On 3 April, 2017, we received a new suggestion to the ARIN Consultation and Suggestion Process. https://arin.net/participate/acsp/suggestions/2017-7.html Description: For the last ~10 years, ARIN's remote participation has been based on Jabber. Over that time, Jabber support has degraded and fallen behind what users generally expect of IM. In particular, it is quite difficult to get Jabber set up, to the point where I've given up and won't be remotely participating on Jabber for ARIN 39. I would recommend that ARIN consider switching to a more modern IM service like Slack for future ARIN meetings. Having set up Slack services for public and semi-public purposes, I can attest that doing so would be easier for everyone involved (ARIN and the remote participants) than the current system. And if Slack is not suitable for some reason, there are many other IM services now that would also work better than Jabber. Alternately, ARIN might consider simply using a web-based chat service alongside the webcast and/or transcript. Value to Community: Replacing Jabber would allow more people to remotely participate in ARIN meetings, and would reduce the setup burden on everyone involved. We will be evaluating this suggestion and issuing a formal response within the next 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Apr 5 12:42:39 2017 From: info at arin.net (ARIN) Date: Wed, 5 Apr 2017 11:42:39 -0500 Subject: [ARIN-Suggestions] New ACSP Suggestion 2017.8: Chat button for ARIN.NET website Message-ID: <2070364e-c975-038d-208a-ad7feb3ccac0@arin.net> On 5 April, 2017, we received a new suggestion to the ARIN Consultation and Suggestion Process. https://arin.net/participate/acsp/suggestions/2017-8.html Description: Chat button for ARIN.NET website Value to Community: Other RIRs provide a live chat button on their web site during business hours which allows people having difficulty with RS or navigation of the web site to get live online help. As ARIN embarks on their website revamp, this might be a good feature to consider. We will be evaluating this suggestion and issuing a formal response within the next 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Apr 7 15:44:12 2017 From: info at arin.net (ARIN) Date: Fri, 7 Apr 2017 15:44:12 -0400 Subject: [ARIN-Suggestions] NEW ACSP Suggestion 2017.9: Changes to IP Address Widget Message-ID: <7875c5a7-3efc-6a25-39fd-c79a2590fe2d@arin.net> On 5 April, 2017, we received a new suggestion to the ARIN Consultation and Suggestion Process. https://www.arin.net/participate/acsp/suggestions/2017-9.html Description: The main page of www.arin.net ought to show both IPv4 and IPv6 addresses in the "Your IPv[46] address is" field to dual stacked hosts, with a background color change and explanatory text to indicate a warning when the client appears to be coming from a single stacked IPv4 host. Value to Community: Some members of the public use www.arin.net's main page as their "what is my IP address" go-to resource. Warning when the client does not appear to be dual-stacked will help raise awareness of the importance of IPv6 adoption. The submitter does not consider single stacked IPv6-only clients to be an error or warning condition. We will be evaluating this suggestion and issuing a formal response within the next 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Apr 10 14:44:11 2017 From: info at arin.net (ARIN) Date: Mon, 10 Apr 2017 14:44:11 -0400 Subject: [ARIN-Suggestions] 3 Message-ID: <58EBD27B.2070807@arin.net> The ARIN Advisory Council (AC) met on 05 April 2017 and decided to send the following Recommended Draft Policy to Last Call: Recommended Draft Policy ARIN-2016-9: Streamline Merger & Acquisition Transfers The AC offered the following statement: "In its meeting on 05-APR-2017, the ARIN AC voted to advance 2016-9 Streamline Merger & Acquisition Transfers to Last Call, with the following changes: In the "list of conditions for clarity", strike the word "additional" and change "an" to "a", so that the revised text reads: "The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer." Concern was expressed by members of the community at the microphone at ARIN 39, and echoed by Staff, that the word "additional" was likely to confuse casual readers. The prevailing opinion was that its removal would result in greater clarity without affecting the plain meaning of the policy statement. Removal of "additional" necessitated changing "an" to "a" for grammatical correctness." Feedback is encouraged during the last call period. All comments should be provided to the Public Policy Mailing List. This last call will expire on 24 April 2017. The Recommended Draft Policy text is below and available at: https://www.arin.net/policy/proposals/ The ARIN Policy Development Process is available at: https://www.arin.net/policy/pdp.html Regards, Sean Hopkins Policy Analyst American Registry for Internet Numbers (ARIN) Recommended Draft Policy ARIN-2016-9: Streamline Merger & Acquisition Transfers AC's Statement of Conformance with ARIN's Principles of Internet Number Resource Policy The proposal is technically sound and enables fair and impartial number policy by ensuring that new organizations involved in mergers and acquisitions may conduct such activities with a reduced procedural burden from ARIN. The staff and legal review noted three issues, all of which have been addressed. There is support for the proposal on PPML and concerns that have been raised by the community regarding the proposal on PPML or elsewhere have also been addressed. Problem Statement: In some 8.2 transfer situations, the current policy has the unwanted side effect of encouraging organizations not to update registration data, thus leaving the number resource in the name of a now defunct entity. It is not uncommon for an entity which has bought another entity (with existing number resources) to leave Organizational data (Whois) in the name of the acquired company. The requirements in Section 8.2 put a justification burden on the acquiring organization, which was a legitimate protection while free pool assignments were available. It is worth revisiting Section 8.2 and looking for opportunities to simplify the policy in the interest of improving the registry data. Consider the following: 1. In the case where both organizations (acquirer, acquired) have justified their existing number resources from an issuer (e.g. SRI-NIC, GSI, ARIN) under the policies that were in force at the time of issuance, the number resources have already been justified once. 2. ARIN does not customarily require organizations holding address space to document utilization except when they are asking ARIN to issue more space. 3. Section 8.2 M&A is not asking ARIN to issue more space or provide authorization to acquire space in an 8.3 transfer. It is simply updating ARIN's database to reflect the current reality, that control of a company has changed. Language that speaks of required return or transfer of space is of questionable enforceability in the context of the current RSA (section 6, "ARIN has no right to revoke any Included Number Resources under this Agreement due to lack of utilization by Holder"). Clauses that serve to scare organizations away from updating their information are counter to the goal of maintaining good data in Whois. Policy should allow ARIN staff to concentrate finite resources on ascertaining chain of custody so as to minimize the chance of fraudulent transfers rather than auditing space already issued. Policy statement: Delete the bullet point in NRPM 8.2 that reads: For mergers and acquisition transfers, the recipient entity must provide evidence that they have acquired assets that use the resources to be transferred from the current registrant. ARIN will maintain an up-to-date list of acceptable types of documentation. Add this statement to list of conditions for clarity: "The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer." Add this conditional to the bottom of 8.2 for linguistic clarity: "AND one or more of the following: The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant. OR The recipient must show that they have acquired the entire entity which is the current registrant." Remove the following paragraph from Section 8.2 of the NRPM: ARIN will proceed with processing transfer requests even if the number resources of the combined organizations exceed what can be justified under current ARIN transfer policy as defined in section 8.5. In that event, ARIN will work with the resource holder(s) to transfer the extra number resources to other organization(s) or accept a voluntary return of the extra number resources to ARIN. These four changes will leave Section 8.2 looking like this: 8.2. Mergers and Acquisitions ARIN will consider requests for the transfer of number resources in the case of mergers, acquisitions, and reorganizations under the following conditions: The current registrant must not be involved in any dispute as to the status of the resources to be transferred. The new entity must sign an RSA covering all resources to be transferred. The resources to be transferred will be subject to ARIN policies. The minimum transfer size is the smaller of the original allocation size or the applicable minimum allocation size in current policy. The Internet number resources being transferred as part of an 8.2 transfer will not be subject to a needs-based assessment during the process of the 8.2 transfer. AND one or more of the following: The recipient must provide evidence that they have acquired the assets that use the resources to be transferred from the current registrant. OR The recipient must show that they have acquired the entire entity which is the current registrant. Timetable for implementation: Immediate From info at arin.net Wed Apr 19 13:55:13 2017 From: info at arin.net (ARIN) Date: Wed, 19 Apr 2017 13:55:13 -0400 Subject: [ARIN-Suggestions] Responses to ACSP 2017.6, 2017.7, 2017.8, and 2017.9 Message-ID: On 19 April, we issued responses to four ACSPs. We have closed 2017.6, and 2017.7, 2017.8, and 2017.9 will remain open until implemented. Response details below: ACSP 2016.6: Registrant Validation Remediation Proposal https://arin.net/participate/acsp/suggestions/2017-6.html Response: Thank you for your suggestion, numbered 2017.6 upon confirmed receipt, to use transfer procedures to validate registrants that have non-validated records. ARIN registration staff currently implements internal procedures similar to what you are suggesting through our Point of Contact (POC) and Organization Identifier (ORG ID) recovery processes. Through these processes, we verify the authority of the individual attempting to recover the POC and/or ORG ID using procedures that are similar to those you would encounter in a transfer request. This results in validated registration data for Whois and protects registration rights holders by thwarting hijacking attempts. Additionally, during the ORG ID recovery process, we sometimes find in our review that the legal chain of custody has changed for a registration record and require the individual acting on behalf of the organization to submit a Merger/Acquisition/Reorganization transfer request (NRPM 8.2) before they may gain authoritative control over the subject resources. https://www.arin.net/resources/request/org.html#recover https://www.arin.net/resources/request/poc.html#recover2 Thank you for participating in the ARIN Consultation and Suggestion Process. We believe that the functionality that you describe already exists via ARIN?s current POC and ORG ID recovery processes, and as such we will be closing your suggestion and will retain documentation of it on the ACSP section of our public website. If you believe that there is additional functionality needed in this area, please submit a suggestion which highlights the additional functionality required. ACSP 2017.7: Replacement of Jabber for Remote Participation https://arin.net/participate/acsp/suggestions/2017-7.html Response: Thank you for your suggestion, numbered 2017.7 upon confirmed receipt, to replace Jabber as our remote participation chat service at ARIN meetings. We agree it is time to replace the use of Jabber at ARIN meetings with a more modern chat application, especially considering feedback that it has caused a member of the community to decide not to participate remotely. We will review available options, including Slack, to determine their ease of use and availability over IPv6 between now and our next Public Policy Meeting in October with the goal of having Jabber replaced by that time. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. ACSP 2017.8: Chat button for ARIN.NET website https://arin.net/participate/acsp/suggestions/2017-8.html Response: Thank you for your suggestion, numbered 2017.8 upon confirmed receipt, to add a live chat button to the ARIN website as we embark on updates to its design and navigation this year. We agree your suggestion will serve as a positive enhancement to our already available telephone help-desk and other communication options currently available to ARIN customers. Availability of this new communication feature will be introduced incrementally, so we may monitor its impact on staffing resources. We will make this new feature a requirement of our website redesign that begins in Q2 of 2017. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. ACSP 2017.9: Changes to IP Address Widget https://arin.net/participate/acsp/suggestions/2017-9.html Response: Thank you for your suggestion, numbered 2017.9 upon confirmed receipt, to make changes to the IP address widget that appears at the top of arin.net to indicate to visitors the IP address they are using to access the site. We agree it can be beneficial to users to see improved information about how they are connecting to the ARIN website and that it could act as an additional motivation for IPv6 adoption. We will investigate available implantation options and make this new feature a requirement of our website redesign that begins in Q2 of 2017. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Apr 27 13:25:31 2017 From: info at arin.net (ARIN) Date: Thu, 27 Apr 2017 13:25:31 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestions 2017.11 and 2017.12 Message-ID: <9f2ff4bb-c3a8-f51a-8f34-cd0a5f7e066c@arin.net> On 26 April, 2017, we received two new suggestions to the ARIN Consultation and Suggestion Process. * ACSP Suggestion 2017.11: Mailing List Support of DMARC [NEW] https://www.arin.net/participate/acsp/suggestions/2017-11.html Description: All ARIN mailing lists do NOT support senders with DMARC records. What this means is that senders who have DMARC enabled will be able to post to the mailman mailing list (and it will show up online via the archives), but when mailman distributes (relays) the senders message to all users subscribed to that list, each users MTA's will reject the message. This is currently happening to the open consult http://lists.arin.net/pipermail/arin-consult/2017-April/000792.html mailing list, as just ONE example. The implications of not fixing this is tremendous. More information published by Mailman: https://wiki.list.org/DEV/DMARC Value to Community: If implemented, community will be able to resume interacting with one another via the current mailing lists. * ACSP Suggestion 2017.12: Remove phone number as a required field in ACSP Submission [NEW] https://www.arin.net/participate/acsp/suggestions/2017-12.html Description: When submitting a suggestion via https://www.arin.net/public/acsp/index.xhtml ARIN currently collects phone numbers as one of the required fields. The page layout / user experience makes it unclear as to what is done with that information. Is the phone number published as part of the request? Is it used for internal purposes? What specifically is shared with the public when the attribution of "List me as Author?" Only first and last name? What about email? Suggestion: Remove collecting of phone numbers as a required field. Enhance the current page and make it clear to the end user what will be shared to the public vs not shared when either attribution values (Anonymous or List me as author) is selected. Value to Community: Enhanced user experience We will be evaluating these suggestions and issue a formal response within the next 10 business days. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)