v1 vs v2 inter-RIR

Created Diff never expires
4 removals
34 lines
28 additions
58 lines
Proposed
Proposed


5.7 IPv4 Resources transfers
5.7 IPv4 Resources transfers


This policy applies to an organization with justified need, for IPv4 resources that cannot be satisfied by AFRINIC.
This policy applies to an organization with justified needs, for IPv4 resources that cannot be satisfied by AFRINIC.


5.7.1 Recognized transfer types
5.7.1 Recognized transfer types


Two types of transfers are recognized:
Two types of transfers are recognized:


a) Intra-RIR. Both parties are within the AFRINIC service region.
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.
b) Inter-RIR. One of the parties is within the AFRINIC service region, while the other is in another RIR service region.




5.7.2 Conditions on the source of the transfer
5.7.2 Conditions on the source of the transfer


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.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.2.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.2 Source entities will not be eligible to receive any further IPv4 address allocations or assignments from AFRINIC.

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.3 Conditions on the recipient of the transfer
5.7.3 Conditions on the recipient of the transfer


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.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.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.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.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:
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 intra-RIR transfers.
• In the case of inter-RIR, when incoming to AFRINIC service region.
• 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.