Compare text

Find the difference between two text files
Real-time diff
Unified diff
Collapse lines
Highlight change
Syntax highlighting
Tools

Untitled diff

Created Diff never expires
4 removals
38 lines
1 addition
35 lines
IPv4 Inter-RIR Legacy Resource Transfers
IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)


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 need, 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.

In the Inter-RIR case, if the source of the resources is located in AFRINIC and the destination is another RIR, only legacy resources can be transferred.





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 for a period of 12 months after a transfer approval.




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.




Saved diffs