From info at arin.net Thu Aug 2 12:01:43 2018 From: info at arin.net (ARIN) Date: Thu, 2 Aug 2018 12:01:43 -0400 Subject: [ARIN-Suggestions] New ACSP Suggestions 2018.16 & 2018.17 Message-ID: On 2 August we received two new suggestions numbered 2018.16 and 2018.17 upon confirmed receipt. We are reviewing these suggestions and will issue our response as soon as it is available. ACSP Suggestion 2018.16: Add delete/list ROAs Endpoints to the RESTful API https://www.arin.net/participate/acsp/suggestions/2018-16.html Description: Add delete/list ROAs endpoints to the API. Value to Community: We are automating a lot our ROA pipeline and have a lot of prefixes to sign. ACSP Suggestion 2018.17: Exempt ROA from Ticketing System https://www.arin.net/participate/acsp/suggestions/2018-17.html Description: Do not use ticket system for ROA Allow automatic addition/removal of org certificate Value to Community: For the people signing with a lot of prefixes, the mailbox ends up being spammed. Also being able to enable/disable RPKI without human intervention would be great. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Aug 3 11:24:52 2018 From: info at arin.net (ARIN) Date: Fri, 3 Aug 2018 11:24:52 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018.18: Make Whowas Reports Viewable in ARIN Online Message-ID: On 3 August we received a new suggestion, numbered 2018.18 upon confirmed receipt, requesting that ARIN make Whowas reports viewable in ARIN Online. This suggestion is in review and we will issue a response as soon as it is available. ACSP Suggestion 2018.18: Make Whowas Reports Viewable in ARIN Online https://www.arin.net/participate/acsp/suggestions/2018-18.html Description: Make Whowas reports viewable in ARIN online For example, create a page to display the report where each existing TSV file name would be represented by a selectable TAB at the top and each TAB would contain the TSV data represented as a simple HTML table. Alternatively simply create a single page with a series of tables for the user to scroll through. Ideally allow the user to select which of the above formats of report is preferred. Value to Community: While a ZIP file full of TSVs might be a useful format for programatic processing by bulk users of whowas, it's not a particularly wonderful format for humans doing occasional research. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Mon Aug 6 15:41:23 2018 From: info at arin.net (ARIN) Date: Mon, 6 Aug 2018 15:41:23 -0400 Subject: [ARIN-Suggestions] NEW ACSP 2018.19: ARIN Online Improvements for Display of POCs and OrgIDs Message-ID: On 6 August we received a new suggestion, numbered 2018.19 upon confirmed receipt, requesting improved functionality to viewing and updating POCs and Org IDs in ARIN Online. https://www.arin.net/participate/acsp/suggestions/2018-19.html Description: Show my orphaned POCs and OrgIds. Show my non-validated POCs. For a given ARIN Online Web account, find: ??? *? all linked POCs ??? * all associated orgIds ??? * all POCs of associated OrgIDs ??? * all POCs of resources held by associated OrgIDs Report which POCs are not validated Report which POCs are orphaned Report which OrgIds are orphaned Provide a button to review and validate POCs. Provide a button to review orphaned POCs and OrgIDs and request their removal or continuance. Removal requests should be held for some time and if no other linked accounts contradicts the request, should then be removed. Value to Community: Will help to highlight the problem of out of date records in the public registry. Will draw attention to the out of date problem to the parties responsible who can help to clean it up. Will support policy changes that aim to clean up the public database. ***** We will be issuing our response to this suggestion soon. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Aug 10 13:27:23 2018 From: info at arin.net (ARIN) Date: Fri, 10 Aug 2018 13:27:23 -0400 Subject: [ARIN-Suggestions] Responses issued on five recent ACSP Suggestions Message-ID: <65654732-fe64-72b0-89f0-24de6358e1f1@arin.net> We have issued our initial responses to suggestions 2018.13, 2018.14, 2018.15, 2018.16, and 2018.17. All remain open, and the suggestion title, url, and the complete text of each response can be found below. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) 1. ACSP Suggestion 2018.13: RPKI-based BGP Origin Validation https://www.arin.net/participate/acsp/suggestions/2018-13.html Response: Thank you for your suggestion, numbered 2018.13 upon confirmed receipt, requesting ARIN enable RPKI based BGP origin validation in ARIN's own Autonomous Systems and reject "invalid" route announcements. We have reviewed your suggestion and note we would need to implement it with careful consideration given to minimizing impact for customers who may encounter situations that require they query and fix their ROAs managed inside ARIN?s hosted RPKI solution in circumstances where they are experiencing their own RPKI-based operational issues. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We will consider this suggestion, together with other RPKI-related community suggestions, for inclusion into our 2019 work plan. 2. ACSP Suggestion 2018.14: Support RRDP for RPKI Publication https://www.arin.net/participate/acsp/suggestions/2018-14.html Thank you for your suggestion, numbered 2018.14 upon confirmed receipt, requesting ARIN support the RRDP protocol (RFC8182) for RPKI publication. We have reviewed your suggestion and confirm that it is possible for ARIN to support RRDP, as you suggest. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We will consider this suggestion, together with other RPKI-related community suggestions, for inclusion into our 2019 work plan. 3. ACSP Suggestion 2018.15: Add "Routing" and "DNS" Points of Contact https://www.arin.net/participate/acsp/suggestions/2018-15.html Thank you for your suggestion, numbered 2018.15 upon confirmed receipt, requesting ARIN add two new Point of Contact types ? Routing and DNS. This suggestion is well timed with the start of ARIN?s new Internet Routing Registry (IRR) development. We agree with your suggestion to include a new ?Routing? point of contact type and have also received suggestions from customers over recent years through customer service interactions that we also add a ?DNS? point of contact type. These new additions will be included in our IRR-related development work that runs this year through the first quarters of 2019. 4. ACSP Suggestion 2018.16: Add delete/list ROAs Endpoints to the RESTful API https://www.arin.net/participate/acsp/suggestions/2018-16.html Thank you for your suggestion, numbered 2018.16 upon confirmed receipt, requesting ARIN add delete/list ROAs endpoints to the API. We have reviewed your suggestion and note that it is possible to implement it alongside other community suggestions that also ask for modifications to ARIN?s API. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We will consider this suggestion, together with other RPKI-related community suggestions, for inclusion into our 2019 work plan. 5. ACSP Suggestion 2018.17: Exempt ROA from Ticketing System https://www.arin.net/participate/acsp/suggestions/2018-17.html Thank you for your suggestion, numbered 2018.17 upon confirmed receipt, requesting ARIN allow automated removal and addition of certain RPKI-related objects without reliance on the ARIN ticketing system. We have reviewed your suggestion and note that it is possible to implement it alongside other RPKI-related community suggestions. Our development schedule for the 2018 year is currently filled by previously submitted community suggestions and other system improvements. We will consider this suggestion, together with other RPKI-related community suggestions, for inclusion into our 2019 work plan. From info at arin.net Fri Aug 10 14:52:17 2018 From: info at arin.net (ARIN) Date: Fri, 10 Aug 2018 14:52:17 -0400 Subject: [ARIN-Suggestions] Two new Suggestions received to ACSP Message-ID: We have received two new suggestions, numbered 2018.20 and 2018.21 upon confirmed receipt.? Both are in review and we will be issuing our official response soon. ACSP Suggestion 2018.20: Change Requirements for STLS Facilitators https://www.arin.net/participate/acsp/suggestions/2018-20.html Description: This suggestion upgrades and clarifies the requirements for entities and individuals to qualify and register as approved facilitators for transfers of number resources. Submitter will send, via email, two accompanying documents, both in .doc and .pdf format. Value to Community: Many ARIN members rely upon the facilitator list for access to additional resources but these "agents" act as if they are approved by ARIN which has led numerous entities to waste valuable time, money and effort. (attachments are available at the url above) ACSP Suggestion 2018.21: Change in Wording in NRPM 8.3 and 8.4 https://www.arin.net/participate/acsp/suggestions/2018-21.html Description: Slight change to the language in 8.3 and 8.4 for clarity. Both have a sentence excepting "M&A" transfers from the 12 month waiting period. But "M&A" is neither a defined term, nor does it encompass all the eventualities covered in an 8.2 transfer (like a reorganization). I suggest the sentences refer to 8.2 transfers rather than "M&A" transfers. Value to Community: Enhanced clarity, I have had a few customers get agitated over this. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) From info at arin.net Fri Aug 10 15:43:45 2018 From: info at arin.net (ARIN) Date: Fri, 10 Aug 2018 15:43:45 -0400 Subject: [ARIN-Suggestions] =?utf-8?q?Now_CLOSED_=E2=80=93_ACSP_2017=2E11?= =?utf-8?q?=3A_Mailing_List_support_for_DMARC?= Message-ID: <1e8262a7-c98d-d0d0-4c5a-3b4c3c2c05d2@arin.net> After reviewing implementation options with the community, we deployed our solution to provide DMARC support for ARIN mailing lists, allowing subscribers from DMARC-enabled domains to participate in mailing list discussions. Having completed the work, we are now closing this suggestion. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) ref: https://www.arin.net/participate/acsp/suggestions/2017-11.html From info at arin.net Wed Aug 15 10:28:41 2018 From: info at arin.net (ARIN) Date: Wed, 15 Aug 2018 10:28:41 -0400 Subject: [ARIN-Suggestions] Response issued to ACSP 2018.21: Change in Wording in NRPM 8.3 and 8.4 and Suggestion Closed Message-ID: We have issued our initial response to Suggestion 2018.21 and at the same time closed the suggestion. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN) # # # Thank you for your suggestion, numbered 2018.21 upon confirmed receipt, requesting a change to the language of Sections 8.3 and 8.4 of the Number Resource Policy Manual (NRPM) for the purpose of clarity. Please note that this suggestion is outside of the scope of the ARIN Consultation and Suggestion Process, as it concerns Internet number resource policy, not an ARIN service or practice. Should you choose to submit a proposed change to the NRPM, the process to request that change is outlined at the link below. As information, the ARIN Advisory Council has already taken note of your suggestion for consideration as a potential editorial change to the NRPM. https://www.arin.net/policy/pdp.html Thank you for participating in the ARIN Consultation and Suggestion Process. As your suggestion is considered out of scope for this process, it is now closed. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at arin.net Mon Aug 27 10:38:22 2018 From: info at arin.net (ARIN) Date: Mon, 27 Aug 2018 10:38:22 -0400 Subject: [ARIN-Suggestions] Now CLOSED - ACSP 2018.20: Change Requirements for STLS Facilitators Message-ID: <9066e207-339b-140d-5c6d-67694f3dbfbc@arin.net> On 27 August, we closed ACSP 2018.20: Change Requirements for STLS Facilitators. You can view the full suggestion and relevant attachments at: https://www.arin.net/vault/participate/acsp/suggestions/2018-20.html Closing Response: Thank you for your suggestion, numbered 2018.20 upon confirmed receipt, requesting ARIN make changes to the requirements for STLS Facilitators. We have reviewed your suggestion and agree that there is reason to considering improvements to the Facilitators program.? Based on feedback received to date (including your suggestion), we will begin a community consultation on this topic to help determine how we will move forward. The consultation will open in the coming weeks with a closing period before the end of September, 2018. Thank you for participating in the ARIN Consultation and Suggestion Process.? Since your suggestion will be included in the open community consultation, this suggestion will close and remain published in our archive as reference material for the community consultation. Regards, Communications and Member Service American Registry for Internet Numbers (ARIN) From info at arin.net Mon Aug 27 15:51:26 2018 From: info at arin.net (ARIN) Date: Mon, 27 Aug 2018 15:51:26 -0400 Subject: [ARIN-Suggestions] Now Closed - ACSP 2018.12: Request for Board Travel Report Message-ID: On 27 August, we closed ACSP 2018.12: Request for Board Travel Report. You can view the full suggestion at: https://www.arin.net/vault/participate/acsp/suggestions/2018-12.html Closing Response: Thank you for your suggestion, numbered 2018.12 upon confirmed receipt, requesting a detailed quarterly reporting of the ARIN travel spending, as was originally requested in suggestion 2017.20. There are many reasons that ARIN staff, ARIN Board, and ARIN community members travel on behalf of ARIN, and there are also many members of the ARIN community who travel to Internet community events who are not on ARIN funding at the time but on behalf of their employer or other organizations. To improve community visibility into ARIN?s travel costs, we have begun publishing quarterly reports of ARIN-paid travel costs to significant Internet events. These reports include the date, event, location, and the total travel costs paid by ARIN (i.e. all ARIN staff, Board, or community member travel included). https://www.arin.net/about_us/corp_docs/quarterly_travel.html We are closing your suggestion with the publishing of these reports. Thank you for your participation in the ARIN Consultation and Suggestion Process. Regards, Communications and Member Services American Registry for Internet Numbers (ARIN)