From info at arin.net Mon Jun 3 16:15:27 2024 From: info at arin.net (ARIN) Date: Mon, 03 Jun 2024 16:15:27 -0400 Subject: [ARIN-Suggestions] Two New Suggestions Received Message-ID: <50E181D8-D880-41B6-A79B-667A1FC7BDC7@arin.net> Two new suggestions have been received (2024.9 and 2024.10). You may find the new suggestions and links in full below. Regards, American Registry for Internet Numbers (ARIN) -------- ACSP Suggestion 2024.9: Provide Machine-Readable Versions of ARIN Micro-allocations https://www.arin.net/participate/community/acsp/suggestions/2024/2024-09/ Author: Matt Peterson Description: ARIN should expose machine-readable versions of ARIN Micro-allocations (Internal, Exchange, and Critical Infrastructure). These should be published in a well-known location and offered in a format usable for scripting languages, such as JSON or CSV encoding. Of particular interest would be the allocation type, assignment date, and the prefix. Additionally, annotating this in whois output would also be useful as another way to signal specific prefixes which were allocated under NRPM 4.4. Value to Community: Researchers and network operators often need to perform analysis on which ?special? allocations, such as exchange points - are present in the DFZ table or not. Those who are tracking the effectiveness and utilization of ARIN policies may find this information useful as well. Timeframe: Not specified Status: Confirmed ------------ ACSP Suggestion 2024.10: Add Optional "Geofeed" field to Whois https://www.arin.net/participate/community/acsp/suggestions/2024/2024-10/ Author: Guanzhong Chen Description: Add an optional ?Geofeed? attribute on Network objects in the ARIN Whois database to serve as a standardized, canonical source for Geofeed URLs. Value to Community: Currently, APNIC and RIPE has a standardized ?geofeed? attribute on their inetnum and inet6num objects, which enables resource holders to declare a canonical source for Geofeed URLs, whereas in ARIN, we are forced to resort to ad hoc solutions like ?Comment: Geofeed [url]?. It is of great benefit to all ARIN resource holders and geolocation providers to have a standardized method of communicating IP geolocation information instead of relying on fragile and error-prone solutions of parsing public comments. To be clear, a similar proposal was made in ACSP Suggestion 2022.15, but that proposal was rejected because there was no interest in adding inetnum into the ARIN IRR. I agree that the ARIN IRR isn?t the right place for this sort of thing, especially since it would require introducing a new object type. However, all network ranges are expected to be correctly documented in a database per NRPM sections 3.2, 4.2.3.7.1, and 6.5.5.1, and the easiest solution to accomplish this has always been with the ARIN Whois database. Per the relevant sections of NRPM, address information, which is intrinsically linked with geolocation, should be documented in the Whois database. Therefore, adding a ?Geofeed? attribute to ARIN Whois database will make documenting and transmitting this aspect of the ARIN resources easier for resource holders. Status: Confirmed From info at arin.net Mon Jun 3 16:15:32 2024 From: info at arin.net (ARIN) Date: Mon, 03 Jun 2024 16:15:32 -0400 Subject: [ARIN-Suggestions] New Response from ARIN for Suggestion 2024.8 Message-ID: A new response from ARIN has been posted for Suggestion 2024.8. Find the original suggestion and latest response from ARIN below. Regards, American Registry for Internet Numbers (ARIN) ----------- ACSP Suggestion 2024.8: Increase Length Limit on IRR Remarks Field https://www.arin.net/participate/community/acsp/suggestions/2024/2024-08/ Author: Dale Carder Description: Increase IRR ?Remarks:? field length limit, and/or allow multiple ?Remarks:? fields Value to Community: When we were trying to migrate our AS-SET records from a 3rd party non-authoritative registry to the ARIN IRR, we found there appears to be a length limit of 1024 on the remarks field. Our motivating use case for this is primarily that Lumen (Level3) AS3356?s filtergen system can not do cross-registry lookups, so they implement a proprietary ?Remarks: Level3 members:? syntax to explicitly enable specification of member objects prefixed with the registry they are located in. This field then overrides the standard RPSL ?members:? field in an AS-SET. As the majority of our downstream customers are in 3rd party non-authoritative registries and that we want to facilitate them moving their data to authoritative registries, particularly the ARIN IRR, this means that we end up with a fairly large set of remarks we need to include as well as duplicates for any ASN that may records in multiple databases. It would be straightforward to maintain this amount of data in one object as we previously did on the other IRR server that supported multiple remarks fields. At present, we have had to chain together multiple AS-SET records to overcome this length limitation in ARIN?s IRR. Additionally, it is often seen that networks document other items such as routing policies, supported bgp communities, and other items relevant to BGP peering in the remarks field. These also are often found to exceed 1024 characters. As we want to facilitate networks migrating to authoritative IRR servers, the ARIN community may increasingly need feature parity. Status: Open ARIN Comment: Thank you for your suggestion, numbered 2024.8 upon confirmed receipt, asking that we increase the length limit on the IRR remarks field. We agree that this would be a useful improvement that would assist in the transition to ARIN?s authenticated IRR from another third-party IRR. ARIN will consider your suggestion in conjunction with other IRR improvements that are in our development pipeline. Your suggestion will remain open until a decision is made on when the features you have requested can be developed. Thank you for participating in the ARIN Consultation and Suggestion Process. From info at arin.net Fri Jun 7 10:16:11 2024 From: info at arin.net (ARIN) Date: Fri, 07 Jun 2024 10:16:11 -0400 Subject: [ARIN-Suggestions] Suggestion 2024.10 is now open Message-ID: A new response from ARIN has been posted for suggestion 2024.10: Add Optional "Geofeed" Field to Whois and this suggestion is now open. You may find the original suggestion and the response from ARIN below.? Regards,? American Registry for Internet Numbers (ARIN)? ------- ACSP Suggestion 2024.10: Add Optional "Geofeed" Field to Whois http://localhost:1313/participate/community/acsp/suggestions/2024/2024-10/ Author: Guanzhong Chen??? Description: Add an optional ?Geofeed? attribute on Network objects in the ARIN Whois database to serve as a standardized, canonical source for Geofeed URLs. Value to Community: Currently, APNIC and RIPE has a standardized ?geofeed? attribute on their inetnum and inet6num objects, which enables resource holders to declare a canonical source for Geofeed URLs, whereas in ARIN, we are forced to resort to ad hoc solutions like ?Comment: Geofeed [url]?. It is of great benefit to all ARIN resource holders and geolocation providers to have a standardized method of communicating IP geolocation information instead of relying on fragile and error-prone solutions of parsing public comments. To be clear, a similar proposal was made in ACSP Suggestion 2022.15, but that proposal was rejected because there was no interest in adding inetnum into the ARIN IRR. I agree that the ARIN IRR isn?t the right place for this sort of thing, especially since it would require introducing a new object type. However, all network ranges are expected to be correctly documented in a database per NRPM sections 3.2, 4.2.3.7.1, and 6.5.5.1, and the easiest solution to accomplish this has always been with the ARIN Whois database. Per the relevant sections of NRPM, address information, which is intrinsically linked with geolocation, should be documented in the Whois database. Therefore, adding a ?Geofeed? attribute to ARIN Whois database will make documenting and transmitting this aspect of the ARIN resources easier for resource holders. Status: Open ARIN Response: Thank you for your suggestion, numbered 2024.10 upon confirmed receipt, requesting ARIN add an optional attribute to the Whois database for customers to publish and share their Geofeed URL. The five Regional Internet Registries (RIRs) are collaborating and working within the Internet Engineering Task Force (IETF) on a standard Registry Data Access Protocol (RDAP) extension for Geofeed data (https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/). When the standard is accepted, ARIN will implement this change to RDAP and add the necessary functionality to ARIN Online and Reg-RWS to support this improvement. The other RIRs will also be implementing this change, which will result in a globally consistent method to publish Geofeed information in RDAP. Additionally, the RIRs are working to develop a bulk RDAP download format to provide network operators with better access to this data that is consistent between the RIRs. Your suggestion will remain open until this new functionality is developed and deployed. Thank you for participating in ARIN?s Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Wed Jun 12 16:20:51 2024 From: info at arin.net (ARIN) Date: Wed, 12 Jun 2024 16:20:51 -0400 Subject: [ARIN-Suggestions] Suggestion 2024.9 is now closed Message-ID: <6B97AD14-0A10-4D6F-81F7-727363819B69@arin.net> A new response from ARIN has been posted for suggestion 2024.9: Provide Machine-Readable Versions of ARIN Micro-allocations and this suggestion is now closed. You may find the original suggestion and the response from ARIN below.? Regards,? American Registry for Internet Numbers (ARIN)? ------- ACSP Suggestion 2024.9: Provide Machine-Readable Versions of ARIN Micro-allocations http://www.arin.net/participate/community/acsp/suggestions/2024/2024-09/ Author: Matt Peterson??? Description: ARIN should expose machine-readable versions of ARIN Micro-allocations (Internal, Exchange, and Critical Infrastructure). These should be published in a well-known location and offered in a format usable for scripting languages, such as JSON or CSV encoding. Of particular interest would be the allocation type, assignment date, and the prefix. Additionally, annotating this in whois output would also be useful as another way to signal specific prefixes which were allocated under NRPM 4.4. Value to Community: Researchers and network operators often need to perform analysis on which ?special? allocations, such as exchange points - are present in the DFZ table or not. Those who are tracking the effectiveness and utilization of ARIN policies may find this information useful as well. Status: Closed ARIN Response: Thank you for your suggestion, numbered 2024.9 on confirmed receipt, asking ARIN to publish machine-readable micro-allocations lists. There is another open suggestion (https://www.arin.net/participate/community/acsp/suggestions/2019/2019-24/) to investigate automating this reporting to publish this data in JSON format, so we are closing your suggestion and retaining the current one for tracking until a definitive course of action is determined. Thank you for participating in ARIN?s Consultation and Suggestion Process. Regards, American Registry for Internet Numbers (ARIN) From info at arin.net Mon Jun 24 11:50:41 2024 From: info at arin.net (ARIN) Date: Mon, 24 Jun 2024 11:50:41 -0400 Subject: [ARIN-Suggestions] Two New Suggestions Recieved Message-ID: Two new suggestions have been received (2024.11 & 2024.12). You may find the new suggestions and links in full below. Regards, American Registry for Internet Numbers (ARIN) ----- ACSP Suggestion 2024.11: Add Change Notification Feature https://www.arin.net/participate/community/acsp/suggestions/2024/2024-11/ Author: Anonymous Description: ARIN should create a mechanism that allows resource holders to be notified of any changes to resources or accounts they manage. Resource holders can then tie these instant reports into change management processes. AFRINIC, APNIC, and RIPE NCC already allow something similar using the RPSL ?notify:? attribute in object maintainers. ARIN could implement equivalent functionality using modern technology instead of e-mail. Value to Community: IP addresses are valuable both in monetary terms and in terms of the functionality they provide to all kinds of organization. Valuable resources are deserve strong change management controls. When organizations get instant notifications of changes they can either evidence and close change management processes quickly, or take action to revert flawed changes straight away. This means that ARIN?s database should become more accurate over time. Status: Confirmed ----- ACSP Suggestion 2024.12: Create IRR and RPKI-only Point of Contact https://www.arin.net/participate/community/acsp/suggestions/2024/2024-12/ Author: Anthony Delacruz Description: Create a ?routing security? POC that ONLY has the ability to change IRR and RPKI items. Value to Community: There are folks we would like to have the ability to add ROA?s or IRR items but not be able to change some of the things that the new ?routing poc? can change like details on network ranges or ASNs or update anything else in whois. We want them to do ROA/IRR and that is pretty much it nothing else please. Status: Confirmed