From info at arin.net Mon Nov 4 11:11:54 2019 From: info at arin.net (ARIN) Date: Mon, 4 Nov 2019 11:11:54 -0500 Subject: [ARIN-Suggestions] NEW ACSP 2019.20: Download All ROAs for an OrgID Message-ID: <353f1814-45b7-58e7-5ab2-b7e1221fde4b@arin.net> On 31 October, we received a new suggestion, numbered 2019.20 upon confirmed receipt, that ARIN permit users to download all ROAs for their Org-ID to a .cvs file. 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-20/ *** Description: I would like the ability to download ROAs for your ORG-ID, to a .cvs file. Currently the ROAs are parsed at 10 records at time. You don?t have the ability to View All or download the ROAs. Value to Community: This would allow ORGs to easily audit the records to ensure they are correct. Timeframe: Not specified *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Nov 8 15:14:56 2019 From: info at arin.net (ARIN) Date: Fri, 8 Nov 2019 15:14:56 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2019.20: Download all ROAs for an OrgID Message-ID: <0b19321d-f1f8-db26-c9aa-9a8525393bce@arin.net> On 8 November, we issued the following response to ACSP 2019.20: Thank you for your suggestion, numbered 2019.20 on confirmed receipt, asking that we provide the ability for a customer to download a .csv file that contains all the ROAs associated with their Org ID. We agree that this would be a useful feature for customers and have added this feature to the list of improvements to be included in RPKI service update work that is currently underway. This suggestion will remain open until implemented. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) Suggestion: https://www.arin.net/participate/community/acsp/suggestions/2019-20/ Description: I would like the ability to download ROAs for your ORG-ID, to a .cvs file. Currently the ROAs are parsed at 10 records at time. You don?t have the ability to View All or download the ROAs. Value to Community: This would allow ORGs to easily audit the records to ensure they are correct. From info at arin.net Wed Nov 20 15:06:29 2019 From: info at arin.net (ARIN) Date: Wed, 20 Nov 2019 15:06:29 -0500 Subject: [ARIN-Suggestions] Two new ACSP Suggestions Message-ID: On 19 November, we received? two new suggestions, numbered 2019.21 and 2019.22 upon confirmed receipt. Staff is reviewing these suggestions and will issue formal responses once analysis is complete. The full text of the suggestions may be found below or at the corresponding urls. 2019.21: Invoice Improvement https://www.arin.net/participate/community/acsp/suggestions/2019-21/ *** Description: ARIN should make its invoice process more compatible with Safari Credit Card Autofill Value to Community: Easier to pay invoices *** 2019.22: Alternative to reCaptcha https://www.arin.net/participate/community/acsp/suggestions/2019-22/ *** 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. *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Nov 22 07:59:33 2019 From: info at arin.net (ARIN) Date: Fri, 22 Nov 2019 07:59:33 -0500 Subject: [ARIN-Suggestions] New ACSP 2019.23: Smart Cursor in Multi-factor Authentication Message-ID: <3305d3a7-63f6-5712-078a-c26d0364b3c7@arin.net> On 31 October, we received a new suggestion, numbered 2019.23 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-23/ *** Description: ARIN should consider cursor placement when authenticating multi-factor users. Put the cursor in the filed that needs to receive the data please, instead of making me click in the field while trying to read the code. Value to Community: Makes multi-factor authentication a bit less annoying Timeframe: Not specified *** Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)