The Open Policy Meeting (OPM) at the APNIC 58 conference will be held on 6 September 2024. Here is a snapshot of the four policy proposals up for discussion.
prop-157: Temporary IPv4 transfers
Current APNIC policies only allow permanent IPv4 address transfers. This proposal suggests a policy modification that would allow for temporary transfers between account holders (applying for intra-RIR transfers, for example, APNIC and NIR account holders, but not inter-RIR transfers such as APNIC to another RIR).
This proposal also suggests that APNIC maintains a public log of temporary transfers with the initial and final dates of transfers as agreed by the source and recipient, as well as restoring the original registration information in the APNIC Whois Database once the transfer period is over.
prop-159: Reduction of minimum IPv6 allocation size from/32 to /36
This proposal suggests reducing the minimum IPv6 allocation size to a /36. Account holders with an IPv4 allocation would be eligible for a /36 IPv6 address block.
prop-160: Change initial IPv6 assignment to /44 for organizations eligible for /23 IPv4
This proposal suggests assigning a /48 IPv6 block to account holders with a /24 IPv4 assignment, and a /44 IPv6 block to account holders with a /23 IPv4 assignment.
prop-161: Using IPv6 for the Internet of Things (IoT)
This proposal suggests explicitly stating in the policy document that IPv6 addresses can be allocated to IoT objects, including both electrical and non-electrical devices, with a default IPv6 allocation size of /32 for IoT requests.
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. They are developed through an open, transparent, and bottom-up process of consultation and consensus.
Have your say about these policy proposals by subscribing to the Policy SIG mailing list or participating in person or remotely during the APNIC 58 Policy SIG forum.
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.