Whenever a transfer of IPv4 is taking place within the APNIC region, the recipient needs to demonstrate the "need" for the IPv4 space they intend to transfer.
Companies transferring IPv4 space to their pool do this in ordcer to enable further growth in their network, since the space is not coming from the free public pool, regular policies that are intended to protect the limited pool of IPv4 space can be removed in transfers.
2. Objective of policy change -----------------------------
Simplify transfer of IPv4 space between resource holders. Ease some administration on APNIC staff, increase database accuracy.
3. Situation in other regions -----------------------------
RIPE region has an all around no need policy in IPv4, even for first allocation, transfers do not require the recipient to demonstrate their intended use of the resources.
ARIN, need base for both transfers and resources issued by ARIN.
AFRINIC, need based policy on transfers (not active yet) and resource request from AFRINIC based on needs.
LACNIC, no transfers, need based request.
Out of all these RIR, only ARIN and RIPE NCC have inter-RIR transfer policies, ARIN has made clear in the past that the "no need" policy from the RIPE region would break inter-RIR transfers from ARIN to RIPE region.
Simply copy the RIPE policy to solve the ARIN transfer incompatibility:
- APNIC shall accept all transfers of Internet number resources to its service region, provided that they comply with the policies relating to transfers within its service region.
- For transfers from RIR regions that require the receiving region to have needs-based policies, recipients must provide a plan to the APNIC for the use of at least 50% of the transferred resources within 5 years.
- When transferring Internet number resources to another RIR, the APNIC will follow the transfer policies that apply within its own service region. The APNIC will also comply with the commitments imposed by the receiving RIR in order to facilitate the transfer.
- Harmonisation with RIPE region. - Makes transfer simpler and smoother within APNIC and between APNIC and RIPE. - Maintains a compatibility with ARIN. - Removes the uncertainty that a transfer may be rejected based on potentially badly documented needs. - Lowers the overall administrative burden on APNIC staff.
6. Impact on resource holders -----------------------------