Search RPD Archives
[rpd] New Proposal - "Number Resources Transfer Policy (AFPUB-2015-GEN-001-DRAFT-01)"
otieno.barrack at gmail.com
Wed Nov 4 10:23:33 UTC 2015
I would like to echo Andrews comments and support the Policy (with the
amendments he has pointed out.) purely from a forwad thinking
On 11/4/15, Andrew Alston <Andrew.Alston at liquidtelecom.com> wrote:
> I for one support this policy, albeit with some modifications, for the
> following reasons.
> A.) As space depletion accelerates in Africa, we will get to a point where a
> transfer policy that allows for transfers WITHIN Africa comes necessary.
> Once the space is depleted a transfer policy will be required to stop the
> transfers happening outside of policy and hence outside of any control of
> AfriNIC. Do not doubt they will happen with or without the policy, the only
> difference is that with the policy, the whois databases and the rest at
> least have a vague potential of being kept accurate
> B.) While there will be a counter argument that space in AfriNIC will still
> take an age to deplete, I point out that policy ratification in AfriNIC
> takes a LONG time as we go through the iterations. (I point to the soft
> landing policy which took YEARS to get ratified)
> C.) I do not think that we should base this on African companies expanding
> outwards, I’d be quite happy with a modification to this policy that
> supported transfer of assets WITHIN the African region between African
> players, and prohibits the transfer of space to companies outside of the
> region. Keep in mind, that as we currently stand, there is no policy
> prohibition on using AfriNIC assigned space off continent (while there is a
> proposal under discussion, this has been rejected twice so far), and hence
> if the receiving entity is African, they can still, provided they can
> adequately justify it, use the space where they need to use it.
> I do think that an express prohibition on transfers outside of the region
> (which is NOT the same as a restriction on genuine African entities using
> their space outside the region for their own customers/purposes) may go a
> long way to easing concerns raised so far.
> Just my thoughts.
> Andrew Alston
> Group Head of IP Strategy
> Sameer business Park, Block A, Mombasa Road. Nairobi, Kenya
> T: +254 205000000 - M: +254 733 2222 04 - E:
> andrew.alston at liquidtelecom.com
> From: Seun Ojedeji <seun.ojedeji at gmail.com<mailto:seun.ojedeji at gmail.com>>
> Date: Tuesday, 3 November 2015 at 10:47 AM
> To: rpd <rpd at afrinic.net<mailto:rpd at afrinic.net>>
> Subject: [rpd] New Proposal - "Number Resources Transfer Policy
> Dear Members,
> We have received a new policy Proposal - "Number Resources Transfer Policy
> Number Resources Transfer Policy
> ID: AFPUB-2015-GEN-001-DRAFT-01
> Policy Name: Number Resources Transfer Policy
> Submitted: 29 October 2015
> Status: Under Discussion
> Author: Mark Elkins, mje at posix.co.za<mailto:mje at posix.co.za>, Posix
> 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.
> A. Source entities outside of the AFRINIC region must meet any requirements
> defined by the RIR where the source entity holds the registration.
> B. 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.
> C. 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.
> D. The minimum transfer size is a /24.
> 3.2 - Conditions on recipient of the transfer:
> A. The conditions on a recipient outside of the AFRINIC region will be
> defined by the policies of the receiving RIR.
> B. Recipients within the AFRINIC region will be subject to current AFRINIC
> policies and sign an RSA for the resources being received.
> C. Recipients within the AFRINIC region must demonstrate the need for up to
> a 24-month supply of IPv4 address space.
> D. The minimum transfer size is a /24.
> 4.0 Version History
> 30 Oct 2015 AFPUB-2015-GEN-001-DRAFT-01 posted
> Best Regards
> Relevant Url:
> 1. Policy Development process:
> 2. AFRINIC Public policy meeting site:
> Barry Macharia & Seun Ojedeji
> PDWG Co-Chairs
> Bringing another down does not take you up - think about your action!
Barrack O. Otieno
More information about the RPD