From info at arin.net Wed Jul 7 13:31:16 2021 From: info at arin.net (ARIN) Date: Wed, 07 Jul 2021 13:31:16 -0400 Subject: [ARIN-Suggestions] Two new Suggestions to the ACSP Message-ID: <71ADEFA5-9FAB-44F9-B39D-01B2F589B563@arin.net> ARIN has received and responded to two new Suggestions to our ACSP. ACSP Suggestion 2021.13: Allow Reassignment of Multiple Subnets to Same End Customer in ARIN Online https://www.arin.net/participate/community/acsp/suggestions/2021/2021-13/ Submitted On: 01 July 2021 Description: There is currently no ability to Reassign more than one subnet to the same end customer via ARIN Online. Many times large ISPs go back and either clean up Whois records or have a customer with more than one subnet block that need to be updated. Automation via API is not always available. Many times customers have the same exactly information including address and there is only the ability to update one at a time. Being able to do this for up to 5 subnet addresses would be useful as it would significantly cut down on the number of clicks required to add Whois info for the same exact customer on numerous blocks with the same location information Value to Community: Better adoption of ARIN online services as well as WHOIS accuracy Timeframe: Not specified Response: Thank you for your suggestion, numbered 2021.13 upon receipt, requesting that ARIN allow reassignment of multiple subnets to the same end customer in ARIN Online. Upon review of your suggestion, we have determined that it is a duplicate of ACSP 2013.16: Association of Multiple Networks with a customer. We agree that offering this service to customers would be beneficial and the original suggestion, ACSP 2013.16, will remain open for prioritization and inclusion on our future work plan. We will be closing this request as a duplicate and will keep ACSP 2013.16 open, noting that an additional request has been received for this service. Thank you for participating in the ARIN Consultation and Suggestion Process. This suggestion will be closed as a duplicate request. ACSP Suggestion 2021.14: Add Ability to Modify Existing Reassignments in ARIN Online https://www.arin.net/participate/community/acsp/suggestions/2021/2021-14/ Submitted On: 01 July 2021 Description: Add the ability to Modify an existing WHOIS record via ARIN online. Currently, the only way to do a modify on an existing reassign is to do it through the email service. Online, there is only the ability to either delete or add. For historical purposes, deleting a block that has been added 5 years ago could have investigative implications if it is deleted and readded. Modify keeps the history of the block intact. I would suggest on the IP Address reassign area that there be the ability to add or modify existing. Most key fields would remain the same. Value to Community: I believe most in the community are trying their best to use API services or ARIN online and move away from the email updates. Currently, the modify function just isn?t available within ARIN online Timeframe: Not specified Response: Thank you for your suggestion, numbered 2021.14 on confirmed receipt, asking that we add the ability to modify existing reassignments in ARIN Online. We agree this is a beneficial improvement and will prioritize it for future implementation. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Thu Jul 29 09:45:45 2021 From: info at arin.net (ARIN) Date: Thu, 29 Jul 2021 09:45:45 -0400 Subject: [ARIN-Suggestions] ACSP 2020.13: Improve Reverse DNS Security Closed on 29 July Message-ID: <1A7E7A12-0D46-4614-9464-1DB1AD005AB8@arin.net> On 29 July, ARIN closed ACSP 2020.13: Improve Reverse DNS Security with the following response: Thank you for your suggestion, numbered 2020.13 on confirmed receipt, asking that we use SHA-256 keys for xx.in-addr.arpa and ip6.arpa (reverse DNS) zones. We have rolled our key signing keys (KSKs) and zone signing keys (ZSKs) to a stronger algorithm (RSA/SHA256, algorithm 8) per your request and guidance from RFC 8624 (https://datatracker.ietf.org/doc/html/rfc8624#section-3.1). Additionally, we no longer publish DS records using digest type 1 (SHA-1), instead only publishing digest type 2 (SHA-256), per updated recommendations from?RFC 8624 (https://datatracker.ietf.org/doc/html/rfc8624#section-3.3). Because this work is completed, we are closing this suggestion. Thank you for participating in the ARIN Consultation and Suggestion Process. The full text and response of the suggestion can be found at: https://www.arin.net/participate/community/acsp/suggestions/2020/2020-13/ Regards, American Registry for Internet Numbers (ARIN)