From info at arin.net Mon Jun 6 16:01:01 2016 From: info at arin.net (ARIN) Date: Mon, 6 Jun 2016 16:01:01 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2016.8: List all Related Unvalidated POCs Message-ID: <5755D67D.8040204@arin.net> ARIN issued the response below to the submitter of suggestion 2016.8:List all Related Unvalidated POCs: Suggestion: Description: The new dashboard does a nice job of listing unvalidated POCs. I (thought I) have been faithful in validating POCs as I receive notices, but I had no idea that I had four unvalidated POCs. Is it possible that when a validation email is sent, that both in the email and on landing page for that reminder email, that the other unvalidated POCs are listed ? just some way to be reminded of all the outstanding POCs? Value to Community: More POCs are validated Response: Thank you for your suggestion, numbered 2016.8 upon confirmed receipt, related to ARIN?s point of contact validation process. We agree that having more validated points of contact is of great value to the community. It is good to hear you are finding the features in our new ARIN Online dashboard useful. As you pointed out, one of the features of the new dashboard includes improved information about point of contact validation for logged in ARIN Online users. In response to your suggestion and other feedback we have received, we will be making additional improvements to the point of contact validation process. We expect improvements to point of contact validation notification to continue through Q1 of 2017. Your suggestion will remain open until implemented. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Jun 20 13:02:17 2016 From: info at arin.net (ARIN) Date: Mon, 20 Jun 2016 13:02:17 -0400 Subject: [ARIN-Suggestions] Three new Suggestions to the ACSP Message-ID: <57682199.2@arin.net> ARIN has confirmed and posted three new suggestions to the ARIN Consultation and Suggestion Process. ARIN is currently reviewing all three suggestions and will be issuing responses to the various submitters as they are completed. The full text and links for all three suggestions are provided, in full, below. 1. 2016.09: Include date since last response in POC Report - https://www.arin.net/participate/acsp/suggestions/2016-09.html Description: Update schema of "Report Of Resources With No Valid Contacts" to include the date since last response. This information is tracked, and shown via Whois-RWS, but is not present in the report. Value to Community: For parties performing analysis to help maintain registry accuracy, this information will be helpful when communicating with their customer base. 2. 2016.10: Allow Billing Consolidation for Organizations with both LRSA & RSA Resouces - https://www.arin.net/participate/acsp/suggestions/2016-10.html Description: Having multiple RSAs should not prevent consolidation of resources for billing purposes. Value to Community: Some organizations have both LRSA and RSA resources. Under the current fee structures adopted by the board, the fact that ARIN treats these as separate organizations and cannot consolidate them for billing purposes may in some cases create real disadvantages forcing the organizations in question to choose between paying excessive fees beyond what is necessary for the covered resources, giving up their LRSA rights and migrating those resources to an RSA, or disenfranchisement because they cannot put their resources under a single subscription agreement. This amounts to a poll tax on LRSA signatories and I believe it is unfair to that segment of the community. 3. 2016.11: Improvements to RESTful Web Services - https://www.arin.net/participate/acsp/suggestions/2016-11.html Description: Howdy, I am starting to use the rest service provided by ARIN to managed SWIP records (reassignments) and I have noticed a shortcoming by the rest service offered by ARIN. I have a suggestion that I would like to make and I hope this is the correct forum to do that in. If not, please let me know what is. For all available reset methods[1] I have noticed that I am unable to view "ALL" records. For example: I can issue GET /rest/customer/CUSTOMERHANDLE?apikey= which will return the information about that customer handle, but I am unable to issue: GET /rest/customer/?apikey= which should return a list of all customers along with their handle that the apikey has access to. The same "Get ALL records" suggestion should be applied to other methods NETs, POCs, Orgs, etc. It appears the only method that offers this are tickets (GET /rest/tickets/) On a side note: I am surprised that no rest or reports via ARIN online interface allows me to see what customer handles I have created. This will allow ARIN members to clean up and delete records that are no longer associated with reassignments. The current report offered by /rest/report/reassignment/NETHANDLE?apikey= does not list the customer handle ? no way to delete those records. [1]: https://www.arin.net/resources/restfulmethods.html Value to Community: Improved Rest Service Ability to Join Records (ORGs, Nets, Customers, POC) much easier at the Rest Service Layer rather than application/end user. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Jun 22 12:16:32 2016 From: info at arin.net (ARIN) Date: Wed, 22 Jun 2016 12:16:32 -0400 Subject: [ARIN-Suggestions] New ACSP. 2016.12: Interactive Fee Calculator Message-ID: <576AB9E0.1000800@arin.net> We have received a new ACSP suggestion, numbered 2016.12 upon confirmed receipt, requesting that we enhance the ARIN fee calculator. The suggestion is currently in review, and we will be providing a response to submitter when it is complete. The full text of the suggestion is provided below: The online fee estimator within the ARIN portal should be interactive. This means we should be able to add OR AND remove resources (IPv4, IPv6, ASN) and the online estimator should provide us an estimate of what the new fees would be. Think of this as a "What If I {add/removed} the following resource{s}" The resources we add OR AND remove to the estimator will in *no* way trigger any actions to the rest of the system (return resources, submit justification request, etc.) The whole purpose is for informational use and fee estimator should make that clear to the end user when adding OR AND removing resources. Value to Community: Reduce questions to ARIN staff Improve understanding of fee policies Help in the future when fees change (because they always will) Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jun 24 15:03:43 2016 From: info at arin.net (ARIN) Date: Fri, 24 Jun 2016 15:03:43 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2016.9: Include date since last response in POC Report Message-ID: <576D840F.8040808@arin.net> We have provided the following response to the submitter of ACSP 2016.9: Include date since last response in POC Report: Thank you for your suggestion, numbered 2016.9 upon confirmed receipt, that we include the date since last response in the Number Resources Without Valid POCs report. We agree that this is a useful addition to the report, and we are adding it to our list of future enhancements found on the list of outstanding projects awaiting prioritization: https://www.arin.net/features/planned.html. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. Suggestion Details: Description: Update schema of "Report Of Resources With No Valid Contacts" to include the date since last response. This information is tracked, and shown via Whois-RWS, but is not present in the report. Value to Community: For parties performing analysis to help maintain registry accuracy, this information will be helpful when communicating with their customer base. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)