From info at arin.net Wed Dec 6 15:26:51 2017 From: info at arin.net (ARIN) Date: Wed, 6 Dec 2017 15:26:51 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2017.27: Allow Directors from Other Organizations to Serve on ARIN Board and In Executive Roles Message-ID: Today we issued the following closing response to ACSP 2017.27: Thank you for your suggestion, numbered 2017.27 upon confirmed receipt, requesting that ARIN allow directors from other organizations to serve on ARIN?s Board of Trustees and in executive roles, and vice versa. We acknowledge your suggestion is correctly based, in part, on the ARIN Board of Trustees? conflict of interest policy as found at: https://www.arin.net/participate/elections/conflicts.html Such a suggested change to the conflict of interest policy will be subject to review by the ARIN Board of Trustees as it is within their scope of responsibilities. As such this suggestion, including its applicability to ARIN?s executive staff, will be brought to the attention of the ARIN Board for their consideration at a forthcoming monthly meeting. Thank you for your participation in the ARIN Consultation and Suggestion Process. This suggestion is now closed. Regards, John Curran President & CEO American Registry for Internet Numbers (ARIN) From info at arin.net Thu Dec 14 15:37:48 2017 From: info at arin.net (ARIN) Date: Thu, 14 Dec 2017 15:37:48 -0500 Subject: [ARIN-Suggestions] Responses to ACSP 2017.28, 2017.25, and 2017.24 Message-ID: <3e4f9a45-6040-19e1-f6f8-738bae3ba18d@arin.net> Today we issued responses to three recent suggestions: *ACSP 2017.24: Allow NET objects of Simple Reassignments to hold POC objects* https://www.arin.net/participate/acsp/suggestions/2017-24.html Response: Thank you for your suggestion, numbered 2017.24 upon confirmed receipt, requesting ARIN allow network objects of simple reassignments to hold POC objects. The addition of POC objects to the networks of simple reassignments would remove distinction between our currently available simple reassignments, where the addition of POC objects is not currently possible, and our detailed reassignments, where it is possible. We note in your suggestion that you may be seeking the ability to retain the use of a simple reassignment (and not use detailed reassignment), in some cases, but still be able to designate an abuse contact that is associated with the downstream organization. This type of change to the features of ARIN's reassignment systems may be of special interest to other users of ARIN's services and may generate a wider discussion about reassignment system functionality and available features. To determine community interest on that topic, we will open a related community consultation in Q1 of 2018. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until reviewed through the consultation process and a determination is made on potential changes to ARIN's reassignment systems. *ACSP 2017.25: Allow Changes to Org Handle in a Detailed Reassignment Without Requiring Deletion* https://www.arin.net/participate/acsp/suggestions/2017-25.html Response: Thank you for your suggestion, numbered 2017.25 upon confirmed receipt, requesting ARIN allow changing the Org handle in a Detailed Reassignment without the necessity to delete it first. We agree that allowing this new feature with detailed reassignments could prevent interruptions in reassignment information reporting in situations where a reassignment is deleted and there are issues with the new one being immediately added. This type of change to the features of ARIN's reassignment systems may be of special interest to other users of ARIN's services and may generate a wider discussion about reassignment system functionality and available features. To determine community interest on that topic, we will open a related community consultation in Q1 of 2018. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until reviewed through the consultation process and a determination is made on potential changes to ARIN's reassignment systems. *ACSP 2017.28: Improvements to POC Searches Within ARIN Online* https://www.arin.net/participate/acsp/suggestions/2017-28.html* * Response: Thank you for your suggestion, numbered 2017.28 upon confirmed receipt, requesting improvements to POC searches in ARIN Online. We are currently in the process of making user interface improvements to ARIN Online based on feedback received in previously submitted suggestions through the ACSP process and other feedback mechanisms. We will include your suggested feedback alongside other suggestions as we continue to make these user interface improvements. 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) -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Fri Dec 15 13:45:02 2017 From: info at arin.net (ARIN) Date: Fri, 15 Dec 2017 13:45:02 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2017.22: Disable OT&E API, keys (RegRWS) in Production Systems Message-ID: <6f03a01e-493c-197b-2405-957177c1ad73@arin.net> Today we issued the initial response to ACSP 2017.22: Disable OT&E API keys (RegRWS) in Production Systems https://www.arin.net/participate/acsp/suggestions/2017-22.html Response: Thank you for your suggestion, numbered 2017.22 upon confirmed receipt, requesting ARIN disable OT&E API keys (RegRWS) on the production database. We agree that disabling OT&E API keys on the production system could prevent accidental usage across systems and we will work to implement your suggestion. 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 next 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 Thu Dec 21 15:19:18 2017 From: info at arin.net (ARIN) Date: Thu, 21 Dec 2017 15:19:18 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2017.21: Display Account Type of Org IDs Message-ID: <5A3C1746.1060105@arin.net> Today we issued the initial response to ACSP 2017.21: Display Account Type of Org IDs https://www.arin.net/participate/acsp/suggestions/2017-21.html Response: Thank you for your suggestion, numbered 2017.21 upon confirmed receipt, requesting ARIN add information to the organization screen in ARIN Online to better identify if the account is considered end-user, subscription services plan, or legacy. We agree that adding the account type information to the organization screen would be helpful to users of ARIN Online and will work to implement your suggestion. 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 next 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)