From info at arin.net Mon Dec 9 13:06:11 2019 From: info at arin.net (ARIN) Date: Mon, 9 Dec 2019 13:06:11 -0500 Subject: [ARIN-Suggestions] NOW CLOSED - ACSP 2018.14: Support RRDP for RPKI Publication Message-ID: On 9 December, we issued the following closing message for ACSP 2018.14:Support RRDP for RPKI Publication: Thank you for your suggestion, numbered 2018.14 on confirmed receipt, asking that ARIN support the RRDP protocol (RFC8182) for RPKI publication. We have completed this work with our most recent deployment. Because this work has been completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. **** For reference, the suggestion is available at: https://www.arin.net/vault/participate/acsp/suggestions/2018-14.html Description: Support the RRDP protocol (RFC8182) for RPKI publication, just like the RIPE NCC and APNIC already do. Value to Community: Currently, ARIN only makes the RPKI dataset available over rsync, which has several downsides: ??? 1. When RPKI relying party software is used on a client system, it has a dependency on rsync. Different versions and different supported options (such as --contimeout) cause unpredictable results. Furthermore calling rsync is inefficient (additional process, and the output can only be verified by scanning the disk). ??? 2. Scaling becomes more and more problematic as the global RPKI data set grows and more operators download and validate data, as with rsync the server in involved in processing the differences. To overcome these limitations the RRDP protocol was developed, which relies on HTTPS. RRDP was specifically designed for scaling and allows CDNs to participate in serving the RPKI data set globally, at scale. In addition, HTTPS is well supported in programming languages so development of relying party software becomes easier and more robust. Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Wed Dec 18 10:14:54 2019 From: info at arin.net (ARIN) Date: Wed, 18 Dec 2019 10:14:54 -0500 Subject: [ARIN-Suggestions] Response and Closing for ACSP 2019.22: Alternative to reCAPTCHA Message-ID: <9136f2ee-aec3-6d21-b339-818cf63c26b9@arin.net> On 17 December, we closed ACSP Suggestion 2019.22: Alternative to reCAPTCHA with the following response: Thank you for your suggestion, numbered 2019.22 upon confirmed receipt, asking that we replace Google reCAPTCHA with another verification method. We moved from using math problems because they were easy for bots to defeat. In researching our use of math-based responses to mitigate abuse of form-based web submissions, we saw many cases where bots are able to trivially defeat the math-based solution. We found the reCAPTCHA system to be a good match for ARIN's use meeting budgetary, labor, and user expectation requirements. Therefore, ARIN currently has no plans to abandon the use of reCAPTCHA and for this? reason, we are closing your suggestion. We thank you for your participation in ARIN's Consultation and Suggestion Process. The full text of the suggestion is available below, or at: https://www.arin.net/vault/participate/acsp/suggestions/2019-22.html Description: ARIN should stop using it?s customers as free labor to train Google?s AI Value to Community: This is even worse than the traditional model of ?if you?re not paying, you?re the product.? Googles reCAPTCHA means that end-users of web sites which use it have no choice but to participate in training Google?s AI systems without compensation. ARIN should provide a viable alternative (such as returning to the traditional math problem solution previously employed) rather than subsidize Google in this manner. Timeframe: Not specified Regards, The American Registry for Internet Numbers (ARIN) From info at arin.net Fri Dec 27 13:28:01 2019 From: info at arin.net (ARIN) Date: Fri, 27 Dec 2019 13:28:01 -0500 Subject: [ARIN-Suggestions] New ACSP 2019.24: Publish Machine-readable Micro-allocation List Message-ID: On 26 December, we received a new suggestion, numbered 2019.24 upon confirmed receipt. Staff is reviewing this suggestion and will issue a formal response once analysis is complete. The full text of the suggestion may be found below or at: https://www.arin.net/participate/community/acsp/suggestions/2019-24/ *** Description: Publish the ARIN Micro Allocations List in machine-readable formats. Maybe as IRR route-set objects and/or JSON files Value to Community: While this information is already published on a website, at https://www.arin.net/reference/research/statistics/microallocations/. The current format likely requires human intervention to make it operationally useful for network automation or inclusion in routing policy. Making the information available as IRR route-set objects and/or JSON files would make this information more operationally useful. *** Regards, The American Registry for Internet Numbers (ARIN)