Search RPD Archives
[rpd] Draft inbound policy
Marcus K. G. Adomey
madomey at hotmail.com
Fri Jun 17 15:11:12 UTC 2016
Hi Andrew,
I wanted to ask you the same question. Are we in the usurpation process where the Board and the board members are assuming, by force, Jobs which are supposed to be carried out by specific staff? Does it mean that you (Andrew) you have no job to do on the board?
Please, answer these questions (EN and mine).
Marcus
Date: Fri, 17 Jun 2016 17:49:24 +0300
From: evelyngeek at gmail.com
To: Andrew.Alston at liquidtelecom.com
CC: rpd at afrinic.net
Subject: Re: [rpd] Draft inbound policy
Hi Andrew,
Isn't it the job of the PDP co-chairs to post policy proposal drafts? Or has it now become a function of board members as well to do so even if they are part of the community?
EN.
Hi All,
The following has been submitted to policy-submission and I am also posting it here for discussion in the mean time.
Thanks
Andrew
Draft Policy Name: Inbound Transfer Policy
Unique Identifier:
Status: Under Discussion
Submission Date: 17 June 2016
Amends: N/A
Author(s):
a. Andrew Alston (andrew.alston at liquidtelecom.com)
b. Christopher Mwangi (Christopher.mwangi at liquidtelecom.com)
1. Introduction:
The AfriNIC Service Region has the lowest amount of IPv4 space of any of the RIR defined regions. As such, when AfriNIC depletes its current space, there will still be a need for further IPv4 addresses on the continent. In addition to this, there may be circumstances where companies wish to use specific v6 resources and ASN’s unavailable on the continent.
While the community has voiced concerns that enacting a transfer policy will result in the flow of resources off the continent, this policy addresses that by purely catering for inbound transfers, without allowing or affecting transfers flowing out of the continent to other RIR service regions.
2. Resources covered under this policy
This policy covers the inbound transfer of all IP resources, including ASN’s, both 16bit and 32bit, IPv4 space and IPv6 space
3. Details of inbound transfer requirements
AfriNIC shall accept all inbound transfers of all resources explicitly referred to in section 2
For transfers into the region, the recipient of IP space (v4 or v6) must provide a plan to AfriNIC for the use of at least 50% of the transferred resource within the next 5 years.
Once received, the space shall form part of the recipient’s normal allocations for the purpose of evaluating the size of the recipient from an AfriNIC membership perspective.
Should a recipient of transferred space apply for further resources from AfriNIC directly, all space received via transfers shall be included in any evaluation done for further resource allocation by AfriNIC.
_______________________________________________
RPD mailing list
RPD at afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
_______________________________________________
RPD mailing list
RPD at afrinic.net
https://lists.afrinic.net/mailman/listinfo/rpd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20160617/8c2384ea/attachment-0001.html>
More information about the RPD
mailing list