Part 2: IPv4 Policy
¶ 4 Leave a comment on paragraph 4 0 Since Thursday, 28 February 2019, each APNIC account holder is only eligible to receive IPv4 address delegations totaling a maximum /23 from the APNIC 103/8 IPv4 address pool.
¶ 5 Leave a comment on paragraph 5 0 On Tuesday, 2 July 2019, non-103/8 resources waiting list was abolished and only new APNIC account holders are eligible to receive IPv4 delegation from the remaining IPv4 pool.
¶ 6 Leave a comment on paragraph 6 0 Note: A waiting list will be created once APNIC runs out of all IPv4 addresses. Any requests received from the new APNIC account holders for IPv4 resources will be put on this waiting list on a first come first request. APNIC will maintain one IPv4 pool for all recovered as well as IANA delegated address space and this pool will be used to provide IPv4 resources to the waiting list requests.
- ¶ 10 Leave a comment on paragraph 10 0
- IPv4 for LIRs
- IPv4 for multihoming
- IPv4 for critical infrastructure
- IPv4 for Internet Exchange Points
- ¶ 13 Leave a comment on paragraph 13 0
- Have used a /24 from their upstream provider or demonstrate an immediate need for a /24,
- Have complied with applicable policies in managing all address space previously delegated to it (including Historical delegations), and
- Demonstrate a detailed plan for use of at least a /23 within a year
- ¶ 16 Leave a comment on paragraph 16 0
- it is currently multihomed, or
- it is currently using at least a /24 from its upstream provider and intends to be multihomed, or
- it intends to be multihomed, and advertise the prefixes within 6 months
¶ 17 Leave a comment on paragraph 17 0 Organizations requesting a delegation under these terms must demonstrate that they are able to use 25% of the requested addresses immediately and 50% within one year.
- ¶ 20 Leave a comment on paragraph 20 0
- Root domain name system (DNS) server
- Global top level domain (gTLD) nameservers
- Country code TLD (ccTLDs) nameservers
- Regional Internet Registry (RIRs), and
- National Internet Registry (NIRs)
¶ 21 Leave a comment on paragraph 21 0 Delegations to critical infrastructure are available only to the actual operators of the network infrastructure performing such functions. Registrar organizations that do not actually host the network housing the registry infrastructure will not be eligible under this policy.
¶ 23 Leave a comment on paragraph 23 0 Internet Exchange Points (IXP) are eligible to receive a delegation from APNIC to be used exclusively to connect the IXP participant devices to the Exchange Point.
- ¶ 27 Leave a comment on paragraph 27 0
- After receiving an initial LIR delegation, all subsequent delegations will depend on the following:
- The LIR’s verified usage rate (which is the rate at which the LIR made delegations from relevant past address space, including Historical delegations)
- Their documented plans for address space, and
- Their degree of compliance with APNIC policies with respect to relevant past delegations.
¶ 28 Leave a comment on paragraph 28 0 Based on these factors, APNIC and NIRs will delegate address space to meet the LIR’s estimated needs for a period up to one year up to the maximum allowed delegation under Section 6.1.
¶ 29 Leave a comment on paragraph 29 0 If APNIC or the NIR make a delegation based on a period of less than one year, then they must inform the LIR of the length of the period and the reasons for selecting it.
¶ 31 Leave a comment on paragraph 31 0 An LIR is not eligible to receive a subsequent delegation from APNIC until its current customer delegations account for at least eighty percent of the total address space it holds. This is referred to as the “eighty percent rule”.
¶ 36 Leave a comment on paragraph 36 0 IPv4 addresses may be transferred in accordance with the following policies. APNIC does not recognize transfers outside this policy and require organizations holding such transfers to return them to the appropriate IR.
¶ 37 Leave a comment on paragraph 37 0 The goal of the APNIC transfer policy is to help distribute IPv4 addresses from those who no longer need the addresses, to organizations that need the addresses, but cannot obtain them from the free pool.
- ¶ 39 Leave a comment on paragraph 39 0
- Current APNIC account holders
- Current APNIC account holders and organizations in other RIR regions
- Holders of Historical IPv4 addresses without an APNIC account to current APNIC Members
- Organizations through a merger, acquisition, or takeover.
¶ 41 Leave a comment on paragraph 41 0 During that time, if the reason for the original request is no longer valid, the resources must be returned to APNIC as required in Section 4.0. Resource License of this document.
¶ 42 Leave a comment on paragraph 42 0 The policies in this document ensure that all transfers of IPv4 address space are accurately reflected in the APNIC Whois Database. This ensures the integrity of the network and an accurate description of the current state of address distribution.
- ¶ 49 Leave a comment on paragraph 49 0
- In the range of addresses administered by APNIC
- Allocated or assigned to a current APNIC account holder
- The address block will be subject to all current APNIC policies from the time of transfer.
- Addresses delegated from the 103/8 free pool cannot be transferred for a minimum of five years after the original delegation.
- ¶ 56 Leave a comment on paragraph 56 0
- Demonstrate a detailed plan for the use of the transferred resource within 24 months,
- Show past usage rate, and
- Provide evidence of compliance with APNIC policies with respect to past delegations.
¶ 58 Leave a comment on paragraph 58 0 APNIC will process and record inter-RIR IPv4 address transfers only when the counterpart RIR has an inter-RIR transfer policy that permits the transfer of address space between APNIC and its own region.
¶ 59 Leave a comment on paragraph 59 0 APNIC will process and record IPv4 address transfer requests between current APNIC account holders and organizations in other RIR regions subject to the following conditions.
¶ 62 Leave a comment on paragraph 62 0 The IPv4 address space to be transferred should be under the management of the RIR at which the transfer source holds an account and the authentic holder of the space should match with the source without any disputes.
¶ 63 Leave a comment on paragraph 63 0 Some RIRs, including APNIC, have restrictions against the transfer of certain address blocks. APNIC policy does not allow the transfer of addresses delegated from the 103/8 free pool to be transferred for a minimum of five years after the original delegation.
- ¶ 66 Leave a comment on paragraph 66 0
- For transfers from an APNIC source, the source entity must be the currently registered holder of the IPv4 address resources, and not be involved in any dispute as to the status of those resources.
- Where the source is in another region, the conditions on the source as defined in the counterpart RIR’s transfer policy at the time of the transfer will apply.
¶ 70 Leave a comment on paragraph 70 0 Where the recipient is in another region, the conditions on the recipient as defined in the counterpart RIR’s transfer policy at the time of the transfer will apply.
¶ 73 Leave a comment on paragraph 73 0 If Historical resources are transferred to an APNIC Member, there is the option to make the transfer under the conditions described in this policy. Transfers of Internet resources to current APNIC account holders are purely optional.
¶ 75 Leave a comment on paragraph 75 0 All transfers of Historical Internet resources to current APNIC Member account holders made under this policy are recognized and registered by APNIC. APNIC does not require any technical review or approval of the resource’s current use to approve the transfer. In addition, APNIC does not review any agreements between the parties to a transfer and does not exert any control over the type of agreement between the parties.
¶ 76 Leave a comment on paragraph 76 0 If the historical Internet resources are not held under a current APNIC account, the recipient entity must verify they are the legitimate holder of the Internet resources.
¶ 80 Leave a comment on paragraph 80 0 All resources transferred under this policy are subject to the provisions of all normal address management policies. In particular, future address requests from the account holder must document the use of transferred resources as a part of their current resource holdings.
¶ 85 Leave a comment on paragraph 85 0 If an organization changes ownership (due to a merger, sale, or takeover), then the new entity must register any changes to its network usage and contact personnel. If the effect of the ownership change is that the name changes, then the organization must provide relevant legal documentation supporting the name change.
¶ 87 Leave a comment on paragraph 87 0 If an organization changes ownership then the new entity should advise APNIC of the change. APNIC membership is not transferable from one entity to another; however, if the effect of the ownership change is that the organization becomes a subsidiary of another entity, and the infrastructures of the respective entities remain fully independent, then the membership agreement may continue.
¶ 89 Leave a comment on paragraph 89 0 Following a change in ownership, APNIC will review the status of any allocations that are held by the new entity or entities, with regard to the practical effect on their infrastructures.
¶ 90 Leave a comment on paragraph 90 0 If the practical effect of ownership change is that the infrastructures are merged, then APNIC will not continue to make separate allocations to both. This situation will invalidate the membership agreement of the organization that is effectively subsumed.
¶ 91 Leave a comment on paragraph 91 0 When assessing the status of IPv4 delegations, APNIC requires full disclosure of all address space held by all of the entities in question. If full disclosure is not made, then APNIC will consider any delegations to be invalid and will require that they be returned.