From info at arin.net Thu Oct 5 12:58:33 2017 From: info at arin.net (ARIN) Date: Thu, 5 Oct 2017 12:58:33 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2017.17: Add HSTS Support to TeamARIN.net and GetIPv6.info Message-ID: <65828268-5a3c-7b5f-dfd7-37eabe1e1a07@arin.net> On 5 October, ARIN received a suggestion, numbered 2017.17 upon confirmed receipt, asking that we add HSTS support to teamarin.net and getipv6.info. We will review and respond to this suggestion after the ARIN 40 Public Policy and Members Meeting now in progress. The text of the suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2017-17.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Oct 11 11:36:48 2017 From: info at arin.net (ARIN) Date: Wed, 11 Oct 2017 11:36:48 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2017.18: Enhancement of Daily ASN Delegation File Message-ID: On 8 October, ARIN received a suggestion, numbered 2017.18 upon confirmed receipt, asking that we add information to enhance the daily ASN delegation file. We are reviewing this suggestion and will provide a response to the community soon. The text of the suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2017-18.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Oct 19 11:25:36 2017 From: info at arin.net (ARIN) Date: Thu, 19 Oct 2017 11:25:36 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2017.16: Allow registered brokers to be added to transfer tickets Message-ID: <59E8C3F0.7000202@arin.net> On 19 October, ARIN issued its response to ACSP 2017.16: Allow registered brokers to be added to transfer tickets. https://www.arin.net/participate/acsp/suggestions/2017-16.html *** Thank you for your suggestion, numbered 2017.16 upon confirmed receipt, requesting brokers be allowed to be added to transfer tickets. As you noted, it is currently possible for organizations to designate transfer brokers as one of their points of contact, thereby allowing them full access to transfer ticket communications between them and ARIN. This is an option available to all organizations who hold direct registrations in the ARIN database, regardless of membership or RSA/LRSA status. Separately, ARIN currently follows instructions from registrants inside their transfer tickets regarding communications with transfer brokers. If a registrant indicates inside their transfer ticket that they authorize ARIN to speak to a particular broker about the status and disposition of their transfer ticket, we follow those instructions. It is noted that the review of transfer tickets via email communications would allow others who are not points of contact to be added to the email thread for information or other purposes during the course of review for transfer requests. ARIN discontinued the review of transfer requests via email two years ago when we brought that service and associated processes into our more secure ARIN Online portal. Although customers have the option to receive the full text of ARIN's ticket responses via email, all customer interaction with the ticket takes place inside ARIN Online. It is possible for us to create a new contact type that would allow brokers, and others who might have a similar need, to provide assistance to companies in their ticket communications with ARIN. To help us better understand possible use cases and desired features in this area, we will conduct a community consultation on this topic. We plan to have this consultation posted for review by the community by Q1 of 2018. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until after the community consultation has concluded and ARIN has made implementation plans based on feedback received through that process. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Thu Oct 26 14:57:08 2017 From: info at arin.net (ARIN) Date: Thu, 26 Oct 2017 14:57:08 -0400 Subject: [ARIN-Suggestions] New Suggestions to ARIN ACSP Message-ID: <716f4e73-0d5f-6423-addd-efe2c0c20167@arin.net> ARIN is currently reviewing and formulating responses to two new suggestion received through the ACSP. 2017.19 - Publication of Meeting Transcripts https://www.arin.net/participate/acsp/suggestions/2017-19.html 2017.20 - Quarterly Reporting of Travel Expenses https://www.arin.net/participate/acsp/suggestions/2017-20.html We will update the mailing list with both responses as soon as they are completed. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Oct 27 13:17:34 2017 From: info at arin.net (ARIN) Date: Fri, 27 Oct 2017 13:17:34 -0400 Subject: [ARIN-Suggestions] UPDATE: Responses issued on ACSP 2017.17 and 2017.18 Message-ID: ARIN has issued the following responses to ACSP 2017.17 and 2017.18: ACSP Suggestion 2017.17: Add HSTS Support to TeamARIN.net and GetIPv6.info https://www.arin.net/participate/acsp/suggestions/2017-17.html Response: Thank you for your suggestion, numbered 2017.17 upon confirmed receipt, requesting HSTS support be added to teamarin.net and getipv6.info. As you noted, HSTS support was added to our production and OT&E services for arin.net in 2015. We agree this support should also be added to our outreach websites. Since the receipt of your suggestion earlier this month, we have added that support to getipv6.info, and are currently working on adding that support to teamarin.net. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until fully implemented. ACSP Suggestion 2017.18: Enhancement of Daily ASN Delegation File https://www.arin.net/participate/acsp/suggestions/2017-18.html Response: Thank you for your suggestion, numbered 2017.18 upon confirmed receipt, requesting an enhancement to the ASN delegation file that ARIN publishes via FTP on a daily basis for informational purposes. In cases a single registrant holds a consecutive block of AS numbers in the ARIN registry, we currently identify them as a block in this file. We understand that you are requesting we modify our reporting in these cases by singly listing each registered AS number. We agree listing the AS numbers as you describe (singly) could improve the usability of the file. We plan to implement the change you have suggested in 2018. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until fully implemented. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)