Policy Archive

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2015-GEN-001-DRAFT-01
  • Submitted:
    29 October 2015
  • Status:
    Withdrawn
  • Author(s):
    - Mark Elkins, mje@posix.co.za, Posix Systems

1.0) Summary of the Problem Being Addressed by this Policy Proposal

AFRINIC is the only Regional Internet Registry without a Transfer policy for the movement of numbering resources - both in and out of the Region. APNIC, RIPE NCC and ARIN have compatible Transfer Policies, so it would seem wise to be compatible with them.

 

2.0) Summary of How this Proposal Addresses the Problem

The Policy solves the issue of an African organisation using space in another Region. This Proposal currently does not attempt to address Legacy Resources (IPv4 and ASN's) - that is resources that are in the AFRINIC Region and were acquired before ARIN existed. Legacy Resources may be moved out of the AFRINIC region and redeployed freely. They may however be subject to the receiving RIR's policies.

 

3.0) Proposal

3.1 The source entity must be the current rights holder of the IPv4 address resources recognized by the RIR responsible for the resources, and not be involved in any dispute as to the status of those resources.

  1. Source entities outside of the AFRINIC region must meet any requirements defined by the RIR where the source entity holds the registration.
  2. Source entities within the AFRINIC region 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, or until the exhaustion of AFRINIC's IPv4 space, whichever occurs first. This restriction is excluded if the Resource is transferred to the same business entity operating in a different region.
  3. Source entities within the AFRINIC region 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 and Transfers to the same business entity in a different region.
  4. The minimum transfer size is a /24.

3.2 - Conditions on recipient of the transfer:

  • The conditions on a recipient outside of the AFRINIC region will be defined by the policies of the receiving RIR.
  • Recipients within the AFRINIC region will be subject to current AFRINIC policies and sign an RSA for the resources being received.
  • Recipients within the AFRINIC region must demonstrate the need for up to a 24-month supply of IPv4 address space.
  • The minimum transfer size is a /24.

4.0 Version History

03 Nov 2015 Version 1 posted to the rpd list
01 Nov 2016 Withdrawn by Authors

Last Modified on -

 

Details
  • Ref. Name:
    AFPUB-2014-GEN-001-DRAFT-04
  • Initial Date:
    03 July 2014
  • Old Ref:
    NA
  • Status:
    Withdrawn
  • Revised:
    13 October 2015
  • Obsoletes:
    None
  • Author(s):
    - Douglas Onyango

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 aspect of number resource management jeopardizes administration by leaving staff to decide arbitrarily how to handle Out-Of-Region requests. The imminent exhaustion of IPv4 aggravates the situation, as it is anticipated that organizations from other regions will have more incentive to exploit this and other loopholes in AFRINIC's policies to acquire resources for sale or use outside the region.

 

2) Summary of How this Proposal Addresses the Problem

  1. This policy tries to be a disincentive to organizations from other regions that want to acquire number resources from AFRINIC for use in ways that are not in the best interests of the AFRINIC community. The policy also provides guidance on how resources allocated and assigned by AFRINIC maybe be used out of region by legitimate AFRINIC members.
  2. For the avoidance of doubt, the author does not seek to prolong the lifespan of IPv4 with this policy; rather, to ensure that number resources allocated and assigned by AFRINIC are used by members from the service region to support their legitimate network operations, regardless of physical location.
  3. For purposes of clarity, this policy in no way promotes Out-Of-Region use of Internet resources. Instead, it is cognizant of the fact that organizations with allocations from AFRINIC may need to use some of their resources outside of the region to support their in-region network operations.

 

3) Proposal

 

  1. 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.
  2. Notwithstanding 3a, the number resources used outside the region at any 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).
  3. Regional Internet Number resources usage will be determined using Whois database information, global routing table announcements, and for purposes of consistency, other criteria prescribed by AFRINIC.
  4. AFRINIC staff shall by use of 3c, carryout due diligence to assess compliance with 3a and 3b.
  5. This policy shall forthwith be part of the acceptable use policy for Internet numbers and any breaches shall be dealt with in accordance with the RSA and other AFRINIC policies.
  6. For the avoidance of doubt, this policy shall not be applied in mutual exclusion, but, shall complement already existing policies and other eligibility criteria prescribed by AFRINIC.
  7. This policy shall apply to past, present and future allocations made by AFRINIC.
  8. This policy shall remain in effect until:
  1. It is directly replaced by another policy or it is superseded by a board resolution.
  2. 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).

4. Version History

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.

13/10/2015 Version AFPUB-2014-GEN-001-DRAFT-04 published:

  • Change last line of Sec. 1 to read: in the AFRINIC community’s best interests. (Change was requested during discussion).
  • Change 3b 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 the staff analysis.
  • Remove the word "assignment" from the policy so that it applies only to allocations.
  • Delete 3.3 (staff’s discretion) to address the issue of completely leaving the policy and its implementation to AFRINIC staff.
  • Add 3c to provide clarity on the definition of Out-Of-Region use and how it will be determined.
  • Add 2c and re-write 2a. “Summary of the Problem” to more clearly articulate the intent of the policy to eliminate the pervasive community confusion around the policy

24/02/2016 Withdrawn by Author

Page 41 of 63