Send ARIN-consult mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.arin.net/mailman/listinfo/arin-consult
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-consult digest..."
Today's Topics:
1. Consultation on Reg-RWS Improvements (ARIN)
2. Re: Consultation on Reg-RWS Improvements (William Herrin)
----------------------------------------------------------------------
Message: 1
Date: Tue, 03 Dec 2024 12:40:14 -0500
From: ARIN <[email protected]>
To: ARIN-consult <[email protected]>
Subject: [ARIN-consult] Consultation on Reg-RWS Improvements
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
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 [email protected]. 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/
------------------------------
Message: 2
Date: Tue, 3 Dec 2024 10:20:27 -0800
From: William Herrin <[email protected]>
Cc: ARIN-consult <[email protected]>
Subject: Re: [ARIN-consult] Consultation on Reg-RWS Improvements
Message-ID:
<cap-gugwtsnxcu7yutshxzgyt2m8mzndv46r0sn-2o2-scum...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
On Tue, Dec 3, 2024 at 9:40?AM ARIN <[email protected]> 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
[email protected]
https://bill.herrin.us/
------------------------------
Subject: Digest Footer
_______________________________________________
ARIN-consult mailing list
[email protected]
https://lists.arin.net/mailman/listinfo/arin-consult
------------------------------
End of ARIN-consult Digest, Vol 112, Issue 1
********************************************
