From info at arin.net Wed Sep 9 13:33:31 2020 From: info at arin.net (ARIN) Date: Wed, 9 Sep 2020 13:33:31 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2020.14: Send Invoices Earlier Message-ID: <07373ea3-6618-1d10-596e-3fe8a9c8a2c5@arin.net> On 9 September we issued our response to ACSP 2020.14 which was received on 25 August. The full text of the suggestion and our response can be found below: ACSP Suggestion 2020.14: Send Invoices Earlier https://www.arin.net/participate/community/acsp/suggestions/2020-14/ Description: Large providers commonly run into an issue with finance departments/automated check and practices where it takes up to 90 days to pay off a large invoice once a real invoice is received. Estimate invoices are considered invalid. When specifically asked if an invoice can be sent earlier than the standard ?invoicing? time, staff has stated that it cannot be done. Organizations would like to pay things on time, but for some larger scale invoices, it takes longer to get it cleared through executives and finance. Some in the community are asking to have the invoices sent out earlier so they can be paid on time/by their due date. Value to Community: ARIN finance will be paid on time/this gives community members time to work with their finance departments and executives in large scale environments. This is especially useful during this COVID period where many people are not in a standard office environment and normal signatures are much harder to get. Timeframe: Not specified RESPONSE: Thank you for your suggestion, numbered 2020.14, upon confirmed receipt, asking that ARIN send invoices earlier to allow organizations to get through their internal processes so that they can pay on time. Per the current procedures documented on our website, we do send the original invoice to the Billing Contact of record 60 days in advance. However, we understand that some organizations need more than the 60 days provide to complete their organizations internal approval processes, and we intend to make improvements that will allow Organizations to receive their invoices 90 days in advance to address this problem. We are currently determining the best way to implement this change in our systems. This suggestion will remain open until implemented. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Mon Sep 14 16:50:03 2020 From: info at arin.net (ARIN) Date: Mon, 14 Sep 2020 16:50:03 -0400 Subject: [ARIN-Suggestions] Two ACSPs closed as complete Message-ID: <470a8726-c8e3-aafb-9523-2de3d6265c5b@arin.net> On 14 September, we sent notification on the completion of work related to two suggestions submitted through the ARIN Consultation and Suggestion Process.? The complete text of both suggestions and the closing response is available below. 1. Closing ACSP 2014.30: Reflect Returns in IRR Data Thank you for your suggestion, numbered 2014.30 upon confirmed receipt, requesting that ARIN should remove the objects related to returned Organizations and ASNs from our IRR database. This functionality is part of the implementation of our new Internet Routing Registry. Because this clean-up is now part of our processes, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. Suggestion Text and URL: https://www.arin.net/participate/community/acsp/suggestions/2014/2014-30/ Description: When an organization or ASN is returned, ARIN should validate that the ARIN IRR maintainer object related to the returned ORG or ASN are removed from the IRR database along with any maintained objects. If there are objects present in the IRR subject to this action, ARIN should notify the entity returning the ORG or ASN of such action. Value to Community: Keeps the IRR database up-to-date Timeframe: Immediate 2.Closing ACSP 2019.2: Eliminate or Increase Revoked ROA per OrgID Thank you for your suggestion, numbered 2019.2 upon confirmed receipt, requesting that ARIN to eliminate or increase revoked ROA limit of 1400 per Org ID. With our most recent deployment we upgraded the hardware security modules in our Resource Public Key Infrastructure (RPKI) system. This upgrade removed the hard restriction of users not having the ability to delete more than 1,400 ROAs due to CRL size limitations.? We have dramatically increased this limit but encourage those users who plan to delete more than 20K ROAs at a time to contact RSD with their plans Because this work has been completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. Suggestion Text and URL: https://www.arin.net/participate/community/acsp/suggestions/2019/2019-2/ Description: Eliminate or Increase Revoked ROA Limit of 1400 per OrgID Value to Community: The limit of 1400 revoked ROAs should be eliminated or dramatically increased to ensure an Org never hits that limit. This would allow businesses to revoke any number of their ROAs as well as enable them to continue to create an extended lifetime for a ROA without fear of hitting the limit. Timeframe: Not specified Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Mon Sep 28 13:26:33 2020 From: info at arin.net (info at arin.net) Date: Mon, 28 Sep 2020 13:26:33 -0400 Subject: [ARIN-Suggestions] Five ACSP suggestions closed on 28 September In-Reply-To: <06e39ebd-b0f4-532e-edd6-56084d0d1489@arin.net> References: <06e39ebd-b0f4-532e-edd6-56084d0d1489@arin.net> Message-ID: <46d28318-bb7c-dfdc-d53e-a58308ff6bed@arin.net> The following suggestions have been closed: 1. ACSP 2020.14: Send Invoices Earlier https://www.arin.net/participate/community/acsp/suggestions/2020/2020-14/ Response: Thank you for your suggestion, numbered 2020.14, upon confirmed receipt, asking that ARIN send invoices earlier to allow organizations to get through their internal processes so that they can pay on time. We recognize that due to the amount of the annual fees for 4x and 5x sized organizations, that additional processing time may be needed to complete payment for their annual fees. We have established an internal process to allow for earlier sending of invoices for interested organizations. Organizations in these two categories who want earlier invoices can contact Financial Services one time to make that request and we will update our internal systems to force earlier annual invoicing for that organization. Because these customers will be accommodated at their request, we consider this suggestion completed.? Thank you for your participation in the ARIN Consultation and Suggestion Process. 2. ACSP 2019.19: Billing Reminders for 4X and 5X Category https://www.arin.net/participate/community/acsp/suggestions/2019/2019-19/ Response: Thank you for your suggestion, numbered 2019.19 upon confirmed receipt, asking that ARIN provide earlier billing notification to 4x and 5x sized organizations. We recognize that due to the amount of the annual fees for 4x and 5x sized organizations, that additional processing time may be needed to complete payment for their annual fees. Organizations in these two categories are welcome to contact Financial Services to request an earlier invoice. Because these customers will be accommodated at their request, we consider this suggestion completed.? Thank you for your participation in the ARIN Consultation and Suggestion Process. 3. ACSP 2017.22: Disable OT&E API keys (RegRWS) on the production database https://www.arin.net/participate/community/acsp/suggestions/2017/2017-22/ 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 have improved our documentation about API keys on our Operational Test and Evaluation Environment (OT&E) page (found at:https://www.arin.net/reference/tools/testing/) to include clear instructions about how to create and maintain separate API keys for use in OT&E.? This provides organizations the option to maintain different API keys if they wish to do so without impacting those organizations that wish to use the same key for both OT&E and production. Because this option is now clearly documented, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. 4. ACSP 2017.24: Allow NET objects of Simple Reassignments to hold POC objects https://www.arin.net/participate/community/acsp/suggestions/2017/2017-24/ Response: Thank you for your suggestion, numbered 2017.24 on confirmed receipt, asking that ARIN allow customers to specify abuse handling on Simple Reassignments. In the time since you submitted this suggestion, the ARIN community has adopted policy 2018-5: Disallow Third-party Organization Record Creation (https://www.arin.net/vault/policy/proposals/2018_5.html) and 2017-12: POC Notification and Validation Upon Reassignment or Reallocation (https://www.arin.net/vault/policy/proposals/2017_12.html). Because these policies require your downstream customers to create their own Org ID and POCs, your suggestion cannot be implemented. Furthermore, using the Detailed Reassignment allows you to reassign to your downstream customer and for them to have their own POCs listed, including an Abuse POC. Because this work cannot be completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. 5. ACSP 2017.25: Allow Changes to Org Handle in a Detailed Reassignment Without Requiring Deletion https://www.arin.net/participate/community/acsp/suggestions/2017/2017-25/ Response: Thank you for your suggestion, numbered 2017.25 on confirmed receipt, asking that ARIN allow users to change the Org handle in a detailed reassignment without deleting the record. In the time since you submitted this suggestion, the ARIN community has adopted policy 2018-5: Disallow Third-party Organization Record Creation (https://www.arin.net/vault/policy/proposals/2018_5.html) and 2017-12: POC Notification and Validation Upon Reassignment or Reallocation (https://www.arin.net/vault/policy/proposals/2017_12.html). Because of these policies, your suggestion cannot be implemented. Furthermore, simply changing the Org ID on a reassignment would be further hindered by having invalid POC objects listed on the Org ID. Creation of a new Org ID by the downstream customer will ensure both policies are being met. Because this work cannot be completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. Regards, The American Registry for Internet Numbers (ARIN) -------------- next part -------------- An HTML attachment was scrubbed... URL: