From info at arin.net Fri Mar 2 15:33:52 2018 From: info at arin.net (ARIN) Date: Fri, 2 Mar 2018 15:33:52 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2018.1: Revision Management System for NRPM Message-ID: On 2 March, we issued the following response to ACSP 2018.1: Revision Management System for NRPM: Thank you for your suggestion, numbered 2018.1 upon confirmed receipt, requesting ARIN provide a github-like interface to facilitate revision research for the Number Resource Policy Manual (NRPM). Although we publish all previous versions of the NRPM complete with full text of the historical documents and change-logs, it is understood the task of comparing previous and current versions of the NRPM can be time-consuming. For those interested in reviewing those changes, we agree a github-like interface would save time and produce more accurate research results. We will investigate the creation of a github-like repository for the current and historical NRPM versions dating back to the first (2004.1) version with a target completion of the work inside Q3 of 2018. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until fully implemented. The full text of the suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2018-1.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Mar 9 15:08:56 2018 From: info at arin.net (ARIN) Date: Fri, 9 Mar 2018 15:08:56 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2018.2: Improvements to Whois Inaccuracy Reporting Message-ID: ARIN has issued a response to the most recent ACSP Suggestion 2018.2: Improvements to Whois Inaccuracy Reporting: Thank you for your suggestion, numbered 2018.2 upon confirmed receipt, requesting ARIN make improvements to Whois inaccuracy reporting. We have reviewed your suggestion and agree that ARIN?s system for Whois inaccuracy reporting can be improved. Specifically, we intend to convert to a ticketed reporting system. Once this suggestion has been added to our work plan, we will propose an implementation plan to the community through a consultation that includes consideration for the different aspects of your suggestion. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We currently intend to add your suggestion to our 2019 work plan. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. *** The full text of the suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2018-2.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Mar 16 13:02:16 2018 From: info at arin.net (ARIN) Date: Fri, 16 Mar 2018 13:02:16 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018.3: Automatically Redirect Whois Queries to Secure URL Message-ID: <101902b4-05d5-eee1-f78d-a69de1c50fe7@arin.net> On 14 March 2018, we received a new ACSP 2018.3: Automatically Redirect Whois Queries to Secure URL. https://www.arin.net/participate/acsp/suggestions/2018-3.html Description: It appears possible to go to the insecure version of ARIN's whois by going to http://whois.arin.net. Would ARIN be willing auto-redirect users to the secure version, https://whois.arin.net, and additionally, consider using HSTS for this site, too? Value to Community: Secures all WHOIS lookups, which could sometimes be potentially sensitive. It's also consistent with what ARIN has done with most of it's other public-facing websites. Timeframe: Not specified ** We are currently evaluating this suggestion, and will provide a response to the community as soon as it is available. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Mar 28 16:24:16 2018 From: info at arin.net (ARIN) Date: Wed, 28 Mar 2018 16:24:16 -0400 Subject: [ARIN-Suggestions] New ACSP 2018.4: Mass Delete of Managed Reassignments Within ARIN Online Message-ID: On 28 March, we received a new suggestion, numbered 2018.4 upon confirmed receipt, requesting that we develop functionality within ARIN Online to allow for mass deletes on managed reassignments. https://www.arin.net/participate/acsp/suggestions/2018-4.html Description: Feature in webportal to do mass deletes on a network range. Say I have a parent big block lets call it a /13. Within that there is a contiguous /19 worth that has 80-100 of reassignments all to different entities, all of which I know are old, unused, and wrong. Rather than having to delete every single one by one could we have an option in the webportal to match on range and after say a 2 or 3 safety clicks are you really sure you want to nuke everything in this confirm blow it away. Value to Community: I've spent the last day clearing out old entries on a /19 worth to repurpose using the search and delete on numerous /29's thru /24's that are all within a contiguous block but I don't want to use the option to clear out the entire parent which has other valid entries. There must be others that don't follow-up on cleanup because of the hassle in getting it done. This could make it easier to clean out large sections of stale whois. ** We are currently reviewing this suggestion, and we will issue our response as soon as it is available. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Wed Mar 28 16:53:16 2018 From: info at arin.net (ARIN) Date: Wed, 28 Mar 2018 16:53:16 -0400 Subject: [ARIN-Suggestions] Response to ACSP 2018.3: Automatically Redirect Whois Queries to Secure URL Message-ID: <2b88ea56-a384-1881-02ae-03f35cb80689@arin.net> On 28 March, we issued our response to ACSP 2018.3: Automatically Redirect Whois Queries to Secure URL: Thank you for your suggestion, numbered 2018.3 upon confirmed receipt, requesting ARIN automatically redirect Whois queries to a secure URL. We have reviewed your suggestion and understand that you are requesting ARIN automatically redirect user queries of Whois made from ?http? to ?https?, and that we also consider the use of HSTS for Whois queries. Noting there is interest from the community on this topic, and that a conversation on the arin-consult mailing list has already begun, we will open a formal community consultation for this suggestion. Feedback received during the consultation will help inform how ARIN will proceed in this area. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until we are able to provide a new update following the closure of the related community consultation. ** The full text of the suggestion is available at: https://www.arin.net/participate/acsp/suggestions/2018-3.html Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Mar 30 09:09:17 2018 From: info at arin.net (ARIN) Date: Fri, 30 Mar 2018 09:09:17 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018.5: Unified RIR Policy Proposal Submission System Message-ID: <2547743d-f88d-a14b-8fd4-3062c6be2c2c@arin.net> On 29 March, we received a new suggestion, numbered 2018.4 upon confirmed receipt, requesting that the five Regional Internet Registries move to a unified policy proposal submission system. https://www.arin.net/participate/acsp/suggestions/2018-5.html Description: After my experience for the round I'd this month submitting my own record of policy proposals (I didn't count them, but I think it is about 15 in total ...), I have a suggestion for all you, if you allow me ... I don't pretend with this to change each PDP, but because in many occasions policies are submitted in different regions (and sometimes the same authors ...) and because the fact that we have also global policies, I believe it will be useful to unify the submission system, which will also facilitate comparative work among you, such as the comparison among policies done by the NRO. I'm not sure if also it will be possible to have the "same" fields in all the RIRs, sometimes you have different views, or it may depend on each specific PDP, but in general I think you're looking for the same info, just with different "field names". Copied also German, not sure if NRO can help on this, if there is interest in coordinating a "unified" submission system ... I also understand that you may need to escalate this, or if I need to send this suggestion to someone else, at each RIR, just let me know! 1) I like the LACNIC form: https://politicas.lacnic.net/politicas/new?language=en. It has a couple of minor mistakes. One is asking for a phone number (mandatory), I think it must not be mandatory, no sense today (I never like to provide my phone number, just email). The other one is that the number of characters it has been too short for one of my actual proposals, but that's easy to sort out. 2) However, I will strongly suggest that it allows also using Word, so we can use track of changes and better "visual" tools (numbering, bullets, etc., which are allowed in both doc and html). What I do for LACNIC right now is preparing my own doc, then copy and paste each "field", which is a non-sense extra work ... I think it will be easy if the form allows you to fill in the text, or upload a file in Word or txt (for those that don't like using Microsoft ...). Towards that, the form should provide and empty Word or txt template. For example, AfriNIC uses internally a two columns template, but they don't publish it, however you get it if you ask to review the policy proposal once submitted ... I've made myself a "version" of that one. 3) One possible improvement to the LACNIC form is to have TWO fields for "actual policy text" (which can be left empty for new text that doesn't exist in actual policies) and "proposed policy text". It can be "further" automated, if the "actual policy text" allows you to "pick" from the actual policy manual what section/sections you are trying to amend. 4) I love the way AfriNIC presents it (example https://www.afrinic.net/en/community/policy-development/policy-proposals/2331-ipv6-pi-update): two columns and two colors. It is close to what RIPE NCC do after the 1st phase (draft document, example https://www.ripe.net/participate/policies/proposals/2018-01/draft), I think, but it is nice to have that since the beginning. The ideal will be to add a button that you can click and presents a "diff". Right now, in complex proposals I prepared my own "online" diff and sent to the list. For example: https://www.diffchecker.com/ly1DaDcb 5) Add to the form a waiver, which only RIPE NCC is asking right now with a mandatory check-box, and you're done! I've copied the actual waiver text from RIPE NCC under my signature, as may be some of you didn't realized the importance of that. 6) LACNIC also send you a "link" (or you can recover it online) once a policy proposal has been submitted, so you can edit new versions, and so on. Again, the only needed change, in my opinion, is to allow uploading a txt or doc file. Do I need to send a global policy proposal for that ? ... I hope not ! Value to Community: Improving the system to submit policy proposals, and making it more "coordinated" across the different RIRs, improving facility to compare them, etc. *** We are currently reviewing this suggestion, and we will issue our response as soon as it is available. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Mar 30 14:37:48 2018 From: info at arin.net (ARIN) Date: Fri, 30 Mar 2018 14:37:48 -0400 Subject: [ARIN-Suggestions] Closing ACSP 2013.22: Sunsetting of RWhois support Message-ID: <1015d632-a6e1-717f-83b1-b01236cebf68@arin.net> On 30 March, we issued our closing statement on ACSP 2013.22: Sunsetting Rwhois Support. https://www.arin.net/participate/acsp/suggestions/2013-22.html Full text below: Thank you for your suggestion, numbered 2013.22 upon confirmed receipt, requesting that we consult with the ARIN community about the possibility of sunsetting support of Rwhois services. ARIN intentionally held back the issuance of a community consultation on this suggestion until after RDAP had been deployed. We then conducted a community consultation on the ?Available Methods of Reporting Network Sub-delegation Information?, which included consideration for SWIP, Rwhois, and RDAP, at the end of 2017. As part of this consultation, we called out the question of continuing support for Rwhois. The full text of the consultation is available at: https://www.arin.net/participate/acsp/community_consult/10-02-2017_rwhois.html Based on the feedback received through the consultation, we have determined that it is the community?s desire that we continue to support Rwhois, at this time. The archive of the discussion is available at: http://lists.arin.net/pipermail/arin-consult/2017-October/thread.html We believe this satisfies your request that ARIN solicit feedback from the community to determine interest in establishing a timeline for the sunsetting of Rwhois. As such, we are closing this suggestion as completed. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)