<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Hi Guys,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">While I realize that some people are less interested in discussing policy than in discussing procedure, I will let the co-chair’s respond on this issue. I am not a co-chair, I do not speak
for them, I merely follow exactly what I was told by them during the last policy submission.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">If I have some how violated the process by posting a draft to the list before it got a unique ID from the PDWG co-chair’s, and by following the instructions of the co-chairs, I humbly get
on my knees and beg your forgiveness, I am sure that a unique ID will follow shortly however and we can get back to doing what this list is for, discussing policy, as proposed by community members.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Timothy Ola Akinfenwa <akin.akinfenwa@uniosun.edu.ng><br>
<b>Date: </b>Friday, 17 June 2016 at 6:19 PM<br>
<b>To: </b>Andrew Alston <Andrew.Alston@liquidtelecom.com><br>
<b>Cc: </b>rpd List <rpd@afrinic.net>, Evelyn Namara <evelyngeek@gmail.com><br>
<b>Subject: </b>Re: [rpd] Draft inbound policy<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p>Andrew, please pardon my curiosity. Was thinking what exactly the law says (if there is any for a situation like this).<o:p></o:p></p>
<p>Guess the community would be better informed should there be a next time. Or should we now rely solely on whatever comes out from the co-chairs?<o:p></o:p></p>
<p>Timothy<o:p></o:p></p>
<div>
<p class="MsoNormal">On 17 Jun 2016 4:08 p.m., "Andrew Alston" <<a href="mailto:Andrew.Alston@liquidtelecom.com">Andrew.Alston@liquidtelecom.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal">Evelyn,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So, I followed exactly what was said to me by the co-chairs at the time of the authoring of the last policy. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">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?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Andrew<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Get <a href="https://aka.ms/o0ukef" target="_blank">Outlook for iOS</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">On Fri, Jun 17, 2016 at 5:49 PM +0300, "Evelyn Namara" <<a href="mailto:evelyngeek@gmail.com" target="_blank">evelyngeek@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<p>Hi Andrew,<o:p></o:p></p>
<p>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?<o:p></o:p></p>
<p>EN.<o:p></o:p></p>
<div style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt">
<p class="MsoNormal">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" target="_blank">andrew.alston@liquidtelecom.com</a>)<br>
b. Christopher Mwangi (<a href="mailto:Christopher.mwangi@liquidtelecom.com" target="_blank">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.<span style="font-family:MingLiU"><br>
<br>
</span>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<span style="font-family:MingLiU"><br>
<br>
</span>3. Details of inbound transfer requirements<span style="font-family:MingLiU"><br>
</span>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.<span style="font-family:MingLiU"><br>
</span>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" target="_blank">RPD@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><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" target="_blank">https://lists.afrinic.net/mailman/listinfo/rpd</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>