<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta content="text/html; charset=utf-8">
</head>
<body>
<div>Evelyn,</div>
<div><br>
</div>
<div>Actually as one the authors I have the right to post the policy to the list. This was how it was confirmed to me by the previous co-chairs when I drafted the last policy, that either they or the authors could post it.</div>
<div><br>
</div>
<div>So, I followed exactly what was said to me by the co-chairs at the time of the authoring of the last policy. </div>
<div><br>
</div>
<div>That is unless you as a community member have suddenly become a co-chair and override what the pdp co chairs have stated to me, another community member?</div>
<div><br>
</div>
<div>Andrew</div>
<div><br>
<div class="acompli_signature">Get <a href="https://aka.ms/o0ukef">Outlook for iOS</a></div>
<br>
</div>
<br>
<br>
<br>
<div class="gmail_quote">On Fri, Jun 17, 2016 at 5:49 PM +0300, "Evelyn Namara" <span dir="ltr">
<<a href="mailto:evelyngeek@gmail.com" target="_blank">evelyngeek@gmail.com</a>></span> wrote:<br>
<br>
</div>
<div>
<p dir="ltr">Hi Andrew,</p>
<p dir="ltr">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?</p>
<p dir="ltr">EN.</p>
<div class="gmail_quot<blockquote class=" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
Hi All,<br>
<br>
The following has been submitted to policy-submission and I am also posting it here for discussion in the mean time.<br>
<br>
Thanks<br>
<br>
Andrew<br>
<br>
Draft Policy Name: Inbound Transfer Policy<br>
Unique Identifier:<br>
Status: Under Discussion<br>
Submission Date: 17 June 2016<br>
Amends: N/A<br>
<br>
Author(s):<br>
a. Andrew Alston (<a href="mailto:andrew.alston@liquidtelecom.com">andrew.alston@liquidtelecom.com</a>)<br>
b. Christopher Mwangi (<a href="mailto:Christopher.mwangi@liquidtelecom.com">Christopher.mwangi@liquidtelecom.com</a>)<br>
<br>
<br>
1. Introduction:<br>
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.<br>
<br>
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.<br>
<br>
2. Resources covered under this policy<br>
This policy covers the inbound transfer of all IP resources, including ASN’s, both 16bit and 32bit, IPv4 space and IPv6 space<br>
<br>
3. Details of inbound transfer requirements<br>
AfriNIC shall accept all inbound transfers of all resources explicitly referred to in section 2<br>
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.<br>
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.<br>
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.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
<a href="mailto:RPD@afrinic.net">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" rel="noreferrer" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
</div>
</div>
</body>
</html>