From info at arin.net Wed Apr 13 12:44:16 2022 From: info at arin.net (ARIN) Date: Wed, 13 Apr 2022 12:44:16 -0400 Subject: [ARIN-Suggestions] New Response for ACSP Suggestion 2022.10 Message-ID: <5BF878F7-502F-4C61-BB49-264B283BFDD9@arin.net> A response from ARIN has been posted for the 2022.10 suggestion. The original suggestion and our response are below: --------- ACSP Suggestion 2022.10: Multilingual PDP, NRPM, and announcements https://www.arin.net/participate/community/acsp/suggestions/2022/2022-10/ Description: Multilingual PDP, NRPM, and announcements - Drive participation and inclusion Value to Community: ARIN has had issues with participation for quite a few years. We are currently looking for new innovative ways to get the community involved. ARIN, while an English-speaking organization first, still services areas in North America including Canada with large French-speaking regions, and the Caribbean Islands which speak Spanish and French. While the language of most businesses is English and ARIN services the English-speaking Caribbean islands, we still have companies with employees where English is not their first language. Studies have shown customers that can read documents and websites in their own language (first language) are more likely to share that information with others where English is not their first language. We have, sometimes, heated discussions over words like ?shall? and ?must? during our in-person meetings. Exact verbiage is important when discussing policy. The current option for anyone reaching out to ARIN is to speak English, read all announcements in English, and to discuss everything in English. While I understand the need to use English first for the majority of what we do, our outreach efforts should at least include French and Spanish. While it would be great to have everything ARIN does in all three languages, an excellent start would be to get the PDP, NRPM, and announcements in all three languages. These three items drive the most discussion within the community. Google translate should not be their only option as this is commonly wrong. Close enough in the case of NRPM and PDP may not be good enough when trying to discuss topics within the region. ARIN has strived for inclusion and higher participation; this would be a great step in that direction Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.10 upon confirmed receipt, requesting that ARIN make the Policy Development Process (PDP), Number Resource Policy Manual (NRPM), and announcements available in French and Spanish to encourage participation from non-English speaking community members. In the past, ARIN has provided translations of documents, but abandoned the practice because they were not utilized and there were significant costs involved in production of the documents. We will conduct a consultation to measure the interest in offering specified content in French and Spanish during the 4th quarter of this year. Prior to the consultation, we will investigate the costs associated with offering content in those two languages. This information will be provided as part of the consultation so the members can decide if there is sufficient value of providing content translation in light of cost and impact on the delivery of other high-value content development projects that are currently in our pipeline. Your suggestion will remain open while we conduct this assessment and consultation. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Fri Apr 15 12:06:18 2022 From: info at arin.net (ARIN) Date: Fri, 15 Apr 2022 12:06:18 -0400 Subject: [ARIN-Suggestions] New ACSP suggestion 2022.11: RESTful API Improvements Message-ID: One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). It is in review and pending response. ---------- ACSP Suggestion 2022.11: RESTful API Improvements https://www.arin.net/participate/community/acsp/suggestions/2022/2022-11/ Author: Anonymous Description: Add support for non-human ?service account? users for programmatic integrations with ARIN?s RESTful API. Value to Community: Feeds automation efforts by community at large. Timeframe: Not specified Status: Confirmed Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Wed Apr 20 11:45:07 2022 From: info at arin.net (ARIN) Date: Wed, 20 Apr 2022 11:45:07 -0400 Subject: [ARIN-Suggestions] New ACSP suggestions 2022.12 and 2022.13 Message-ID: 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) From info at arin.net Tue Apr 26 15:48:32 2022 From: info at arin.net (ARIN) Date: Tue, 26 Apr 2022 15:48:32 -0400 Subject: [ARIN-Suggestions] New Response for ACSP Suggestion 2022.11 Message-ID: <0B951F4B-A5B5-4B94-99A0-755F6BDD8B08@arin.net> A response from ARIN has been posted for the 2022.11 suggestion. Find the original suggestion and our response below: ------------- ACSP Suggestion 2022.11: RESTful API Improvements https://www.arin.net/participate/community/acsp/suggestions/2022/2022-11/ Description: Add support for non-human ?service account? users for programmatic integrations with ARIN?s RESTful API. Value to Community: Feeds automation efforts by community at large. Timeframe: Not specified Response from ARIN: Thank you for your suggestion, numbered 2022.11 upon confirmed receipt, asking that ARIN allow non-human ?service accounts? to be used for programmatic interactions with ARIN?s RESTful API. When ARIN originally deployed the RESTful APIs, there was internal discussion about whether API keys should be managed on an individual basis, or if keys could be assigned to potentially shared role accounts. At the time, there was consensus that it was important to be able to determine which users were making changes via these APIs in the event of problems. We agree that having the ability to use role or service accounts for programmatic interactions would be beneficial to customers, and there is minimal work needed to remove the restrictions in the system to allow this option. We will put this improvement on our list of features for prioritization. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. Regards, American Registry for Internet Numbers (ARIN)