Out-Of-Region Use of AFRINIC Internet Number Resources
03 July 2014
1. Summary of the Problem Being Addressed by this Policy Proposal.
Currently AFRINIC's policies do not explicitly allow or disallow Out-Of-Region use of Internet number resources. This silence on an important facet of number resource management jeopardizes administration by leaving staff to arbitrarily decide how to handle Out-Of-Region requests. The imminent exhaustion of IPv4 aggravates the situation because it is anticipated that organizations from other regions will have more incentive to exploit this, and any other loophole in AFRINIC's polices to acquire resources for sale or use outside the region -- a practice that is not in the best interests of the AFRINIC community.
2. Summary of How this Proposal Addresses the Problem
This policy allows up to 40% of Internet number resources in use by a member to be outside the region. It also tries to be a disincentive for organizations from other regions that want to acquire resources from AFRINIC for use in ways that are not in line with AFRINIC’s policies and best interest.
For the avoidance of doubt, the author does not seek to prolong the lifespan of IPv4 with this policy; rather, he seeks to ensure that number resources allocated/assigned by AFRINIC are used by members from the service region to support their legitimate network operations, regardless of physical location.
- Upon ratification of this policy, out-of-region use of AFRINIC's number resources shall be permitted as long it is preceded by use within the region.
- Notwithstanding (3.a), the number resources used outside the region at any given point in time shall not exceed 40% of the total space in use by a member. Total space in use shall be calculated as follows: if x be the allocation size; and y the amount of space in use at time z, then 40% of y shall be the ceiling).
- AFRINIC staff shall at their discretion, and using whatever means are available, assess compliance with 3.a/b.
- This policy shall forthwith be part of the acceptable use policy for Internet numbers any breaches shall be dealt with in accordance with the RSA other AFRINIC policies.
- For the avoidance of doubt, this policy shall not be applied in mutual exclusion, but rather complement already existing policies and other eligibility criteria prescribed by AFRINIC.
- This policy shall apply to present and future allocations made by AFRINIC.
- This policy shall remain in effect until i) it is mooted by another policy or it is superseded by a board resolution. ii) Until section 3.8 of the IPv4 Softanding Policy kicks in. (Use of IPv4 space from the last /8 outside the region shall be only to facilitate connectivity back to the region).
- 03/07/2014: Version AFPUB-2014-GEN-001-DRAFT-01 posted to the mailing list.
- 20/10/2014: Version AFPUB-2014-GEN-001-DRAFT-02 published. Sentence in 3(b) changed from “Total space in use shall be calculated as follows: if x be the allocation/assignment size; and x-y the amount of space in use at time z, then 40% of (x-y) shall be the ceiling)” to “Total space in use shall be calculated as follows: if x be the allocation/assignment size; and y the amount of space in use at time z, then 40% of y shall be the ceiling)”
- 27/05/2015: Version AFPUB-2014-GEN-001-DRAFT-03 published:
- Remove “past” from 3.f. This is to solve the issue of applying the policy retrospectively
- Change last like of 1 to read: in the AFRINIC community’s best interest. Change requested during discussion
- Change 3.b to read Total space in use shall be calculated as follows: if x be the allocation size; and y the amount of space in use at time z. This is to resolve the issue with definition of y brought up during staff analysis.
- Remove the word "assignment" from the policy so that it applies only to allocations.
Discussions are taking place on the policy working group mailing list if you want to subscribe to the mailing send your subscription request to rpd-request [at] afrinic.net with 'Subscribe' as subject line
Mailing list archives can be found at https://lists.afrinic.net/pipermail/rpd