From info at arin.net  Tue Dec  3 12:40:14 2024
From: info at arin.net (ARIN)
Date: Tue, 03 Dec 2024 12:40:14 -0500
Subject: [ARIN-consult] Consultation on Reg-RWS Improvements
Message-ID: <FE508CEA-0453-41F4-BCD3-7796610FB286@arin.net>

ARIN is seeking feedback from the community (https://www.arin.net/participate/community/acsp/consultations/2024/2024-7/) on a potential improvement to the RESTful API used to manage registration records, known as Reg-RWS. Specifically, we received a community suggestion to create a RESTful API method to determine the most specific NET object for a range.

The stated benefit of this potential improvement is that it would allow a user to bootstrap functionality based on knowing a problematic IP address and learning more about it (delegation, Points of Contact, etc.).

ARIN has two distinct RESTful web services, Reg-RWS and Whois-RWS. Currently, there is a most specific network query available using Whois-RWS.

(https://www.arin.net/resources/registry/whois/rws/api/#ip-addresses-and-networks)

We are seeking community input on whether the existing services meet community needs, or if ARIN should spend resources to duplicate the functionality from Whois-RWS into Reg-RWS.

Please provide comments to arin-consult at arin.net. You can subscribe to this mailing list at https://lists.arin.net/mailman/listinfo/arin-consult.

This consultation will remain open until 5:00 PM ET on 20 December 2024. ARIN seeks clear direction through community input, so your feedback is important.

Thank you for your continued support to improve ARIN?s services.

Regards,

John Curran	
President and CEO
American Registry for Internet Numbers (ARIN)


-----
ACSP Consultation 2024.7: Consultation on Reg-RWS Improvements
https://www.arin.net/participate/community/acsp/consultations/2024/2024-7/






From bill at herrin.us  Tue Dec  3 13:20:27 2024
From: bill at herrin.us (William Herrin)
Date: Tue, 3 Dec 2024 10:20:27 -0800
Subject: [ARIN-consult] Consultation on Reg-RWS Improvements
In-Reply-To: <FE508CEA-0453-41F4-BCD3-7796610FB286@arin.net>
References: <FE508CEA-0453-41F4-BCD3-7796610FB286@arin.net>
Message-ID: <CAP-guGWtsnxcU7yUTSHXzGYt2m8mznDv46R0sn-2o2-ScuM+DQ@mail.gmail.com>

On Tue, Dec 3, 2024 at 9:40?AM ARIN <info at arin.net> wrote:
> ARIN is seeking feedback from the community (https://www.arin.net/participate/community/acsp/consultations/2024/2024-7/) on a potential improvement to the RESTful API used to manage registration records, known as Reg-RWS. Specifically, we received a community suggestion to create a RESTful API method to determine the most specific NET object for a range.
>
> The stated benefit of this potential improvement is that it would allow a user to bootstrap functionality based on knowing a problematic IP address and learning more about it (delegation, Points of Contact, etc.).

Howdy,

Before spending the money, I'd like to see more thought given to the
automation this is meant to support. ISP abuse contacts are already
swamped with false reports where the complainant has misconstrued
innocent or forged packets, and with inactionable reports where the
problem is genuine but the complainant has left out detail critical to
solving it. Making automation of such false and inactionable reporting
even easier could cause further deterioration in that highly-manual
downstream process. Would it be worth facilitating automation of the
downstream abuse reporting process first, so that the recipients can
sift them with effective automation too?

Regards,
Bill Herrin


-- 
William Herrin
bill at herrin.us
https://bill.herrin.us/


From info at arin.net  Fri Dec 13 10:51:36 2024
From: info at arin.net (ARIN)
Date: Fri, 13 Dec 2024 10:51:36 -0500
Subject: [ARIN-consult] Reminder on ARIN Consultation on Reg-RWS Improvements
Message-ID: <6FF40B31-A455-4345-BB60-8590DF479180@arin.net>

ARIN would like to remind the community about the ongoing consultation focused on a potential improvement to Reg-RWS, the RESTful API used to manage registration records. This consultation is scheduled to close on Friday, 20 December. Please submit your comments to the arin-consult mailing list before then. 

This consultation is based on a community suggestion we received to create a RESTful API to determine the most specific NET object for a range. The stated benefit of this potential improvement is that it would allow a user to bootstrap functionality based on knowing a problematic IP address and learning more about it.

ARIN has two distinct RESTful web services: Reg-RWS and Whois-RWS. Currently, there is a most specific network query available using Whois-RWS.

Read the full text of the consultation at:  https://www.arin.net/participate/community/acsp/consultations/2024/2024-7/ 

As of 13 December, we have received few comments from the community regarding this consultation. If you have feedback you?d like to share with ARIN, please provide it to the arin-consult mailing list via arin-consult at arin.net. ARIN will use the feedback provided to determine whether our existing services meet community needs, or if we should spend resources to duplicate the functionality from Whois-RWS into Reg-RWS.

Thank you for your participation in this community consultation.

Regards,

John Curran
President and CEO
American Registry for Internet Numbers (ARIN)