[ARIN-Suggestions] Four New ACSP Suggestions and One Response

[ARIN]

Four new suggestions have been received (2023.15, 2023.16, 2023.17, and 2023.18), and a response from ARIN has been posted for 2023.15. You may find the new suggestions and latest response from ARIN in full below. 
 

Regards, 

American Registry for Internet Numbers (ARIN)

-------

ACSP Suggestion 2023.15: Allow Specified Description of API Keys
https://www.arin.net/participate/community/acsp/suggestions/2023/2023-15/

Author: Marcus Jackson   
Submitted On: 25 October 2023

Description: Please allow users to specify a description of API keys.

Value to Community: In the absence of fine grained permissions, and named service roles (already a suggestion) a way to specify the intended use of a key would be extremely helpful for key management. It would be even more useful to specify exactly what functionality is allowed by that key, as it would allow us to create applications with a smaller blast radius.

Timeframe: Not specified | Status: Open   

ARIN Comment: Thank you for your suggestion, numbered 2023.15 upon confirmed receipt, asking that ARIN provide the ability to allow users to specify a description of an API key to make it easier to track the functionality of each key. ARIN agrees that this would be a useful for customers who have multiple API keys.

We will add this to our deployment schedule and prioritize it along with other development initiatives. Your suggestion will remain open until implemented.

Thank you for participating in the ARIN Consultation and Suggestion Process.

-------

ACSP Suggestion 2023.16: Give Voting Rights to Qualified Facilitators
https://www.arin.net/participate/community/acsp/suggestions/2023/2023-16/

Author: Mike Burns   
Submitted On: 26 October 2023

Description: Give Qualified Facilitators voting rights

Value to Community: Qualified Facilitators have greater exposure to ARIN people and policies than most resource holders and their votes would be presumably well-informed.

Timeframe: Not specified | Status: Confirmed   

-------

ACSP Suggestion 2023.17: Allow Third-Party ROA Creation by Block
https://www.arin.net/participate/community/acsp/suggestions/2023/2023-17/

Author: Mike Burns   
Submitted On: 26 October 2023

Description: Allow third-party ROA creation by block, not by Organization. Currently an organization can allow a third-party to create ROAs, but that authority extends to all the organization’s blocks. Some organizations may wish to enable this capability but only for a subset of their resources.

Value to Community: The community sees the good in RPKI growth, and this is an impediment in circumstances where a portion of an organization’s resources are leased-out and a lease manager seeks to automate ROA actions, which can only happen if blanket authority is granted to the lease manager to create ROAs for all the registrant organization’s resources.

Timeframe: Not specified | Status: Confirmed   

-------


ACSP Suggestion 2023.18: Expand Fraud Reporting to Include Leasing of 4.10 Space
https://www.arin.net/participate/community/acsp/suggestions/2023/2023-18/

Author: Anonymous   
Submitted On: 27 October 2023

Description: Widen scope of ARIN fraud reporting tool to include NRPM 4.10 leasing or offer a similar submission mechanism for this purpose.

Value to Community: NRPM 4.10 space is extremely valuable for new startups. We might not exist without it. There are numerous organizations who acquire NRPM 4.10 prefixes and then lease them out in the leasing market fur purposes other than IPv6 transition. The current fraud reporting tool seems geared towards outright theft by way of illegal transfers or the creation of organizations fake documentation. There needs to be a way to report NRPM 4.10 prefixes that are being leased out.

Timeframe: Not specified | Status: Confirmed