[ARIN-Suggestions] New Responses from ARIN for Suggestions 2017.21, 2024.2, and 2024.3

[ARIN]

New responses from ARIN have been posted for suggestions 2017.21: Display Account Type of Org IDs, 2024.2: RPKI Service Improvement - ROA Analyze, and 2024.3: RPKI Service Improvement - Auto-IRR Route/6 Objects during ROA Creation. Suggestion 2017.2 is now closed, and 2024.2 and 2024.3 are now open. You may find the original suggestions and the responses from ARIN below. 

Regards, 

American Registry for Internet Numbers (ARIN) 

---------- 
ACSP Suggestion 2017.21: Display Account Type of Org IDs
https://www.arin.net/participate/community/acsp/suggestions/2017/2017-21/

Author: Paul Emmons   

Description: In ARIN Online under Your Account – Organization Identifiers show the organizations account type, i.e. End user or Registration Services Plan or Legacy

Value to Community: When a user is associated with multiple organizations it would be helpful to know which charging mechanism is in play.

Status: Closed   

ARIN Response: Thank you for your suggestion, numbered 2017.21 upon confirmed receipt, asking that ARIN add information to the organization screen in ARIN Online to better identify if the account is considered end user, subscription services plan, or legacy. Over the last few years, ARIN has implemented a new fee schedule which included moving end users into the Registration Services Plan (RSP) and added information to show if an organization has an ARIN agreement or not.

Because the information you suggested is now displayed in ARIN Online, we are closing your suggestion as completed. Thank you for participating in the ARIN Consultation and Suggestion Process.

----------
2024.2: RPKI Service Improvement - ROA Analyze
https://www.arin.net/participate/community/acsp/suggestions/2024/2024-02/

Author: Anonymous   

Description: ARIN RPKI ROA Web UI Management Tools - ROA Analyze

Value to Community: This will help all creating ROAs via ARIN Hosted to analyze any negative and potentially unexpected results of creating a ROA. A feature in Krill to “Analyze my ROAs” which actively analyzes prefixes and status is exceptionally helpful in assessing the current state of ROAs and impact on announcements. We would like to see this feature added to ARIN Hosted. Additionally, we would like to see an option to download or export the list of candidate prefixes/ASNs in CSV format so we can perform further analysis prior to committing changes.

Status: Open   

ARIN Response: Thank you for your suggestion, numbered 2024.02 upon confirmed receipt, asking that ARIN add a feature to our RPKI web interface to analyze any negative and potentially unexpected results of creating a ROA, as well as an option to download or export the list of candidate prefixes/ASNs in a CSV format for additional analysis prior to committing changes. There is a similar web UI feature to what you describe in our development pipeline awaiting prioritization and scheduling. The suggestion for a downloadable report will be reviewed for potential prioritization. Both of these suggestions will remain open pending implementation of these features.

Thank you for participating in ARIN’s Consultation and Suggestion Process.

----------
2024.3: RPKI Service Improvement - Auto-IRR Route/6 Objects during ROA Creation
https://www.arin.net/participate/community/acsp/suggestions/2024/2024-03/

Author: Anonymous   

Description: ARIN RPKI ROA Web UI Management Tools - Auto-IRR Route/6 Objects during ROA Creation

Value to Community: As many INET peers use route/6 objects to build import policies, still, it would be helpful to have those route/6 objects auto-created to ensure an INET peer will accept an annoucment. Re-enable auto-IRR route object creation at ROA creation. If there is a question about allowing an opt-in/out selection, have it default to opt-in, and do it at the ORGID level.

Status: Open   

ARIN Response: Thank you for your suggestion, numbered 2024.03 upon confirmed receipt, asking that ARIN re-enable auto-IRR route object creation at ROA creation. As you note, this previously implemented feature was disabled for additional development to make it an opt-in feature. Similar functionality to what you describe is currently in our development pipeline awaiting prioritization and scheduling. This suggestion will remain open pending implementation.

Thank you for participating in ARIN’s Consultation and Suggestion Process.