From info at arin.net Thu Jun 16 09:51:29 2022 From: info at arin.net (ARIN) Date: Thu, 16 Jun 2022 09:51:29 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion and Response for 2022.15 Message-ID: One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Find the original suggestion and ARIN's response below: ----------- ACSP Suggestion 2022.15: Add Ability to Remark a Geofeed URL https://www.arin.net/participate/community/acsp/suggestions/2022/2022-15/ Author: Anonymous Description: Please add the ability to remark a geofeed URL like other RIR?s allow. A commonly accepted method is to use Regional Internet Registries (RIR) such as AFRINIC, ARIN, APNIC, LACNIC, or RIPE to share geofeed URLs by adding a remarks attribute with value Geofeed (https://your-url.com/geofeed.csv) when you define an inetnum entry. This way, IP geolocation providers such as Ipregistry can discover new geofeeds when they parse Whois databases periodically. Outlined - https://ipregistry.co/blog/geofeeds Value to Community: It would allow for ISPs to update their geolocation details via a geofeed rather than contacting each IP geolocation website. This is offered by other Internet Registry services. Timeframe: Not specified Status: Closed ARIN Comment: Thank you for your suggestion, numbered 2022.15 upon confirmed receipt, requesting that ARIN add the ability to include a geofeed URL using inetnum: objects in the Authenticated. This suggestion is similar to suggestion 2021.27 (https://www.arin.net/participate/community/acsp/suggestions/2021/2021-27/). We investigated the usage of inetnum: objects, prior to the creation of the ARIN authenticated IRR, and found usage of inetnum: was extremely limited, and inclusion of geolocation coordinates was not detected. This factored into our original decision to discontinue support for inetnum: objects when the ARIN authenticated IRR was created. We researched other RIRs, and 3rd party IRR operator databases for inetnum: objects populated with geo coordinates, the count ranged from statistically insignificant to zero. There are several alternatives for publishing this data, including but not limited to, using a remark in an existing route: object and populating it with the link to your Geolocation feed. This mitigates the need to restore support, create and maintain new inetnum: objects. As there are alternative ways available to publish geolocation data that do not necessitate restoring inetnum: to the ARIN IRR, we are not going to pursue development of this suggestion. Thank you for participating in ARIN?s Consultation and Suggestion Process. ----------- Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Fri Jun 24 09:36:42 2022 From: info at arin.net (ARIN) Date: Fri, 24 Jun 2022 09:36:42 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestion 2022.16 Message-ID: One new suggestion was recently submitted to ARIN?s Consultation and Suggestion Process (ACSP). Following review and discussion with the submitter, the suggestion has been closed. Find the original suggestion and response below: ------------- ACSP Suggestion 2022.16: Create Eligible Voters Mailing Distribution List https://www.arin.net/participate/community/acsp/suggestions/2022/2022-16/ Author: Ron da Silva Description: Thinking of last year?s experience? I have a suggestion that will help the process - create an email distribution list including all authorized voting contacts (e.g. the emails/Points of Contact that will be allowed to vote in the election) and make that available to candidates to be able to send a moderated message(s) directly to the electorate (staff to proctor to avoid over communications or spam)? thus the identities of the voting representatives can be preserved but the candidates will have a clear way to communicate directly with the electorate. Value to Community: Improves election process. Timeframe: Not specified Status: Confirmed ------------- RESPONSE Thank you for your suggestion, numbered 2022.16 upon confirmed receipt, asking ARIN to provide an email distribution list of eligible voters for candidate use. We appreciate the desire for candidates to be able to connect directly with ARIN election voters through a moderated messaging method. We have created such a method with the General Member mailing list which is open to all General Members that wish to subscribe and is publicly archived. For the purposes of elections, we will also subscribe all candidates to this list so that they can engage in discussion with potential voters between the time the initial slate is announced and the conclusion of the voting period. This alternative was confirmed to meet the intent of your suggestion in offline discussion. Because this solution satisfies your suggestion, it will be closed. Thank you for participating in the ARIN Consultation and Suggestion process. ------------- Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Thu Jun 30 13:14:27 2022 From: info at arin.net (ARIN) Date: Thu, 30 Jun 2022 13:14:27 -0400 Subject: [ARIN-Suggestions] New Response for ACSP Suggestion 2022.12 Message-ID: <0FEAAF42-D0AD-4CD3-9CBB-6FEC72A26AD4@arin.net> A response from ARIN has been posted for the 2022.12 suggestion. Find the original suggestion and our response below: ----------- ACSP Suggestion 2022.12: Publish RSA/LRSA Status in Whois/RDAP https://www.arin.net/participate/community/acsp/suggestions/2022/2022-12/ 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 ----------- Response from ARIN: Thank you for your suggestion, numbered 2022.12 upon confirmed receipt, asking that ARIN include the registration services contract status of each number resource block in the public registry via Whois/RDAP. There are privacy concerns regarding listing the contract status per network managed under ARIN to Whois/RDAP records. However, we agree that it is operationally relevant to see what ARIN services are provided per network on a bulk basis. To fulfill this need, ARIN will create a daily report that will list the network and the type of service it receives from ARIN, Full Registry services vs Basic Legacy services. This suggestion will remain open until we complete the work to make this report available and announce it to the community. Thank you for participating in the ARIN Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN)