From info at arin.net Mon Feb 5 14:12:41 2018 From: info at arin.net (ARIN) Date: Mon, 5 Feb 2018 14:12:41 -0500 Subject: [ARIN-Suggestions] Closing ACSP 2017.7: Replacement of Jabber for Remote Participation Message-ID: <44ed35da-638e-01e0-9ea3-00ce0493f2fa@arin.net> On 5 February, we officially closed ACSP 2017.7: Replacement of Jabber for Remote Participation as completed. Please see the full text of the closing response below: Thank you for your suggestion, numbered 2017.7 upon confirmed receipt, to replace Jabber as the remote participation communication tool for ARIN meetings. We used Jabber for the last time at ARIN's October 2017 meeting. Beginning at our April 2018 meeting, Jabber will be replaced as our remote participation communication tool by Slack. Our remote participation page for the upcoming meeting reflects this permanent change. As such, we are closing this suggestion. Thank you again for your participation in the ARIN Consultation and Suggestion Process. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Feb 5 16:21:28 2018 From: info at arin.net (ARIN) Date: Mon, 5 Feb 2018 16:21:28 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2017.23: Changes To RegRWS Access With API Key Authentication Message-ID: <435f6448-bb98-1a22-67de-e1f7d78af22d@arin.net> On 5 February, we provided our initial response on ACSP 2017.23: Changes To RegRWS Access With API Key Authentication. https://www.arin.net/participate/acsp/suggestions/2017-23.html The full text is provided below: Thank you for your suggestion, numbered 2017.23 upon confirmed receipt, requesting ARIN make an improvement to our RegRWS service. We have reviewed your suggestion and communicated with you via telephone to better understand your request. We have determined we can accommodate this suggestion, alongside similar API related suggestions, at a future date when we conduct a comprehensive update to our API. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We will review that schedule for changes and new additions early this year, and at that time will consider if scheduling for this suggestion may be moved up. 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) From info at arin.net Mon Feb 12 15:07:41 2018 From: info at arin.net (ARIN) Date: Mon, 12 Feb 2018 15:07:41 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2017.19: Publication of Meeting Transcripts Message-ID: <6efbb80e-04d4-d728-e542-9acd98ac70bb@arin.net> On 12 February, we issued our official response and closed ACSP 2017.19: Publication of Meeting Transcripts. The full text of the suggestion can be found at: https://www.arin.net/participate/acsp/suggestions/2017-19.html Response in full: Thank you for your suggestion, numbered 2017.19 upon confirmed receipt, requesting publication of the ARIN meeting transcripts. As confirmed through follow-up communications with you about this suggestion, ARIN does publish the full meeting transcript along with other archival information in our meeting report following each Public Policy and Members' Meeting. For approximately one week between the conclusion of each meeting and the publishing of the meeting report and archive page, the official meeting page available leading up to and during the live event is still visible. During this period, the meeting page contains information about the meeting, but does not include a copy of the live transcript. This meeting page for the live event is fully replaced by our meeting report and archive, once it is published. As a result of your suggestion, we will keep the live transcript, as it existed during the execution of the meeting, available on the meeting web page during the week between the close of an ARIN meeting and the publishing of the formal meeting report. This transcript will be accompanied by a disclaimer and notification that it will be replaced by the formal meeting report within one business week. Thank you for participating in the ARIN Consultation and Suggestion Process. We are closing your suggestion with the commitment to leave the meeting transcript available for the week between the close of a meeting and the publishing of the formal meeting report in the future. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Tue Feb 27 12:10:13 2018 From: info at arin.net (ARIN) Date: Tue, 27 Feb 2018 12:10:13 -0500 Subject: [ARIN-Suggestions] NEW ACSP 2018.2: Improvements to Whois Inaccuracy Reporting Message-ID: <3d906044-956d-53dd-d22f-b9a04769ac34@arin.net> On 26 February, we received a new ACSP 2018.2: Improvements to Whois Inaccuracy Reporting. https://www.arin.net/participate/acsp/suggestions/2018-2.html Description: I would like to put forward a proposal which I believe serves the ARIN organization, the ARIN community and the general public, in which the public can be better engaged in reporting ARIN inaccuracies. Currently, the method for reporting an ARIN inaccuracy is not only non-tranparent, but without feedback that reporting such inaccuracies has any affect, I believe that the larger general community would become disallusioned, and not contribute to improving the accuracy. ARIN has often reported on the difficulty in auditing the records, both in SWIP records, ownership records, and references to 'whois' data. The current method is to follow the instructions listed at https://www.arin.net/public/whoisinaccuracy/index.xhtml. However, this is a one way report, and there is no way the submitter can identify if the report was even received and reviewed by a human, let alone know if an action was taken. I would suggest that instead, a 'ticket' system would be used, so that the report would be available for review by the ARIN team, and the ARIN team could provide feedback on when and what form of a notification was made to the holder of that ARIN space, and the progress to rectification. The general public could also review these tickets, and this would ensure that reports do not slip through the cracks, and are properly followed up on, and that the ARIN mandates are being followed correctly and in a timely manner. The public could also review the information BEFORE submitting so that could prevent duplicate reports. And by publicly showing tickets in progress, ARIN holders would also have an incentive to fix the problem in a timely manner. IT might also be integrated into an action system, alerting IP Space holders of open tickets, that they might not be aware of, and offers another avenue for reporting, if for instance the contact information on file for the report is no longer valid. It also COULD be used by ARIN staff, eg that renewals do not get actioned while there are open tickets to be addressed, to help them with their mandate of maintaining upto date information and accuracy. Value to Community: Encourages the community to be involved in maintaining and fixing the accuracy of the ARIN database. Let's them see the value of making such reports, to encourage future reports. Enables the community to assess and audit ARIN's actioning of such reports. Allows them to determine when inaccurate information has been corrected. Saves them from submitting duplicate requests, when they can see that the report already has an action trail. ** We are currently evaluating this suggestion, and will provide a response to the community as soon as it is available. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)