The Open Policy Meeting (OPM) at the APNIC 55 conference will be held on 1 March 2023. Here is a snapshot of the four policy proposals up for discussion.
prop-147: Historical Resources Management
According to the EC resolution of 22 February 2021, historical resource holders in the APNIC region would need to become Members or Non-Members by 1 January 2023 to continue to receive registration services. After this date, historical resource registrations will no longer be published in the APNIC Whois Database, and the resources will be placed in reserved status.
This proposal suggests a process where custodians could claim historical resources that have been marked as reserved within 12 months of the date they were marked as reserved. If no claim is received within 12 months, reserved resources will be placed in the free pool for redelegation.
The proposal also suggests that historical resources marked as reserved and/or reclaimed by APNIC due to account closures will lose their ‘historical’ status and become ‘current’ resources for redelegation.
prop-149: Change of maximum delegation for less than /21 total IPv4 holdings
This proposal suggests increasing the maximum IPv4 delegation size for new APNIC account holders from a /23 to a /22 and, if requested, delegating an additional /23 to APNIC account holders with less than a total of a /21 of IPv4 resources.
Under this proposal, APNIC account holders with a total amount of IPv4 resources equal to or more than a /21 would not be eligible for further IPv4 delegations.
prop-150: ROA/whois object with Private, Reserved and Unallocated (reserved/available) Origin ASNs
This proposal suggests APNIC restrict an account holder’s right to create Route Origin Authorizations (ROAs) with private, reserved, or unallocated Autonomous System Numbers (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.
prop-151: Restricting non-hierarchical AS-SET
This proposal would restrict APNIC account holders from creating a non-hierarchical as-set, and notify all Members who already have a non-hierarchical as-set that it is recommended they move to a hierarchical as-set.
Participate! Have your say
Good policy relies on a range of opinions from people in different parts of the community, so it is important to get involved. Policy is developed through an open, transparent, and bottom-up process of consultation and consensus.
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.