Two new suggestions were recently submitted to ARIN’s Consultation and 
Suggestion Process (ACSP). They are both in review and pending response.

-----------

ACSP Suggestion 2022.12: Publish RSA/LRSA Status in Whois/RDAP
https://www.arin.net/participate/community/acsp/suggestions/2022/2022-12/

Author: Anonymous  

Description: ARIN should include the registration services contract status of 
each number resource block in the public registry (visible via Whois/RDAP) - No 
agreement, RSA, or LRSA (i.e. entered into an LRSA/RSA as a legacy number 
resource)

Value to Community: There is an increasing amount of effort in securing 
Internet routing that has dependency on ARIN services (e.g. RPKI), and 
consistent data analysis of the progress and barriers to deployment is not 
possible without this information being publicly available. (It is acceptable 
for ARIN to redact this information from publication if necessary due to legal 
circumstances, for example disputes or litigation.)

Timeframe: Not specified

Status: Confirmed  

-----------

ACSP Suggestion 2022.13: Extend REST API to check Whois data
https://www.arin.net/participate/community/acsp/suggestions/2022/2022-13/

Author: Edvinas Rackauskas  

Description: Extend RestAPI to check whois data, for not only resources you own 
or got reallocated, but everything else as well.

For example, if someone reallocated /16 to my org I want to check who did it 
(in case I do not know, or just need for other purpose) I use NET parent handle 
and check it.

Currently as Parent is not managed by my org I get 401 unauthorized, funny 
thing is that the same information can be collected using whois query and ARIN 
portal, but via API not, it forced us to use additional resources, services to 
receive needed information.

Value to Community: By “opening” RestAPI to check such things as parent of NET, 
etc, we community can easier find responsible organisations in case of hijacks, 
abuse contact. Find “connection” between Organisation which reallocated the 
networks and who is using it. RIPE has open API, for some calls, I believe ARIN 
can do it as well.

Timeframe: Not specified

Status: Confirmed

-----------

Regards,

The American Registry for Internet Numbers (ARIN)


_______________________________________________
arin-suggestions mailing list
[email protected]
https://lists.arin.net/mailman/listinfo/arin-suggestions

Reply via email to