prop-150: ROA/whois object with Private, Reserved and Unallocated (reserved/available) Origin ASN
Proposal text | prop-150-v002 |
---|---|
Objective |
This proposal suggests APNIC restrict an account holder’s right to create ROAs with private, reserved, or unallocated ASNs. The proposal also suggests APNIC notify account holders if the Origin ASN in their ROA is unallocated (reserved/available), and to not automatically renew ROAs with unallocated (reserved/available) ASNs. |
Current status | Implemented |
Authors |
Aftab Siddiqui |
Relevant forum | Policy SIG |
Previous versions | prop-150-v001 |
Secretariat impact assessment |
A similar proposal was presented at the APNIC 52 OPM and was accepted APNIC notes this proposal would restrict an account holder’s ability APNIC must notify the account holder as to why the ASN used to create the APNIC also needs to notify the account holder in case the Origin ASN used This proposal may require changes to APNIC systems and procedures. If this |
Proposal history | |
20 January 2023 |
Version 1 posted to the Policy SIG mailing list for discussion and community development. |
30 January 2023 |
Version 2 posted to the Policy SIG mailing list for discussion and community development. |
02 March 2023 |
Version 2 reached consensus at APNIC 55. |
08 March 2023 |
Final call for comments. |
11 April 2023 | End of final comment period. |
21 April 2023 | Endorsed by APNIC EC |
19 June 2023 | Call for editorial comments |
20 July 2023 | End of editorial comment period. Policy published as apnic-127-v013. |