actual vs inter-rir v2
16 removals
27 lines
40 additions
51 lines
Current
Proposed
5.7 IPv4 Resources transfer within the AFRINIC Region
5.7 IPv4 Resources transfers
Like the other Regional Internet Registries, AFRINIC will soon exhaust its IPv4 pool. In order to meet the needs of late resource requestors, a transfer policy for IPv4 resources within the region is needed. The goal of this policy is to define conditions under which transfers must occur. The policy solves the issue of an African organization needing IPv4 number resources after the exhaustion of the AFRINIC IPv4 pool or when AFRINIC can no longer satisfy the needs of such an organization.
This policy applies to an organization with justified needs, for IPv4 resources that cannot be satisfied by AFRINIC.
5.7.1 Summary of the policy
5.7.1 Recognized transfer types
This policy applies to an organization with justified need for IPv4 resources that cannot be satisfied by AFRINIC.
5.7.2 IPv4 resources to be transferred - must be from an existing AFRINIC member's account or from a Legacy Resource Holder in the AFRINIC service region.
Two types of transfers are recognized:
5.7.3. Conditions on the source of the transfer
a) Intra-RIR. Both parties are within the AFRINIC service region.
b) Inter-RIR. One of the parties is within the AFRINIC service region, while the other is in another RIR service region.
5.7.3.1 The source must be the current rightful holder of the IPv4 address resources recognized by AFRINIC, and not be involved in any dispute as to the status of those resources.
5.7.2 Conditions on the source of the transfer
5.7.3.2 Source entities will not be eligible to receive any further IPv4 address allocations or assignments from AFRINIC for a period of 12 months after a transfer approval.
5.7.2.1 The source must be the current rightful holder of the IPv4 address resources in the relevant RIR, and not be involved in any dispute as to the status of those resources.
5.7.3.3 Source entities must not have received a transfer, allocation, or assignment of IPv4 number resources from AFRINIC for the 12 months prior to the approval of transfer request. This restriction excludes mergers and acquisitions transfers.
5.7.2.2 Source entities will not be eligible to receive any further IPv4 address allocations or assignments from AFRINIC.
5.7.4. Conditions on the recipient of the transfer
5.7.2.3 Source entities must not have received a transfer, allocation, or assignment of IPv4 number resources from AFRINIC for the 12 months prior to the approval of transfer request.
5.7.4.1 AFRINIC must approve the recipient's need for the IPv4 number resources. In order for an organization to qualify for receiving a transfer, it must first go through the process of justifying its IPv4 resource needs before AFRINIC. That is to say, the organization must justify and demonstrate before AFRINIC its initial/additional allocation/assignment usage, as applicable, according to the policies in force.
5.7.3 Conditions on the recipient of the transfer
5.7.4.2 The recipient must be an AFRINIC member, subject to current AFRINIC policies and must sign the Registration Services Agreement for resources being received.
5.7.3.1 For an organization within the AFRINIC service region, AFRINIC must approve the recipient's need for the IPv4 number resources, following existing relevant policies.
5.7.4.3 Transferred IPv4 legacy resources will no longer be regarded as legacy resources.
5.7.3.2 For an organization in another RIR service region the relevant criterion will depend on the relevant policies in the destination RIR.
5.7.3.3 The recipient must be a member of the relevant RIR, subjected to its policies and legal documents/service agreements.
5.7.3.4 IPv4 legacy resources will no longer be regarded as legacy resources:
• In the case of intra-RIR transfers.
• In the case of inter-RIR, when incoming to AFRINIC service region.
5.7.4 Provisions for ASN transfers
In case of transfers of the majority of the IPv4 resources from the source, the relevant ASN(s) could also be transferred, if other relevant policies are fulfilled.
5.7.5 Timing for Applicability of Inter-RIR transfers
Inter-RIR transfers will be triggered only once AFRINIC enters into Exhaustion Phase 2 (as defined in 5.4.3.2).
5.7.6 Transparency of Transfers
Each time a transfer is completed, the relevant, non-confidential information will be automatically published in a specific web page, including at least: Date of the transfer, transferred resources, source organization and RIR, destination organization and RIR.
5.7.8 Provisions for Suspensions of Transfers
5.7.8.1 The inter-RIR transfers will be suspended in case the number of outgoing IPv4 addresses exceeds the incoming ones by 6 consecutive months.
5.7.8.2 The staff can provisionally suspend any suspicious operation and request more information to all the parties, so the board can take a decision.