<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" 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="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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",serif;}
span.gmail-
{mso-style-name:gmail-;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Hi Kevin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Thanks for the email and insights. A few comments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Firstly – one of the things we also need to realize, is that much of the IPv6 push has been towards provided and academia. If we truly want v6 adoption,
I’d argue we are going about it the wrong way, we have to promote it into the corporate and home user market. Only when these markets start demanding IPv6 will we get true movement from the majority of providers. End of the day, what matters to providers
is the bottom line, and if we can get the corporates to start to select their ISP’s based on IPv6 availability, the ISP’s WILL follow. So, that is where the outreach has to be focused.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">For years we have sort the proverbial IPv6 business case – it doesn’t exist in the sense that people were looking for, because those who were trying
to find it, were looking at IPv6 as a revenue making opportunity. If we attempt to sell V6 as a way to make money, we’ll never succeed. The trick to promoting IPv6 is to prove that it is not about revenue generation, it is about revenue retention. If you
can make the case that the lack of IPv6 will eventually hurt the entity you are promoting to on their bottom line, you will get uptake. That case isn’t actually all that hard to make, considering that corporates rely on the Internet in almost everything they
do, and when you can prove near imminent depletion of v4, it’s not hard to make this case.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">With regards to policies and procedures – I have long taken the (admittedly controversial) view that the only real policy within the address allocation
sector that will promote v6, is the one that promotes the depletion of IPv4. As Africa sits with unused v4 inside its registry, V6 growth will be slow. We will continue to be a dumping ground for legacy hardware that does not support V6, and we will fall
further and further behind the rest of the world. There is substantial evidence of the fact that V4 depletion does promote the growth of V6. I point to the Google IPv6 penetration map at
<a href="https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption">
https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption&tab=per-country-ipv6-adoption</a> as case in point.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">On this map, you will see there are only two countries in Africa that have in excess of half a percent v6 penetration levels. One is Sudan, and
one in Zimbabwe. Zimbabwe currently runs at 4.76% penetration and climbing – beyond that the rest of Africa has effectively no real penetration. Now, compare that to the rest of the world where v4 is depleted, and you see a vastly different picture. The
global average deployment rate is sitting at 12% and climbing, whereas all it took to *<b>double</b>* the aggregate penetration rate in Africa was the v6 enabling of 10 or 15 thousand FTTH users in Zimbabwe. This speaks volumes, we have v4, and its slowing
us down in getting v6 deployed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">This is in line with what you said here:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><i><u><span style="font-family:"Arial",sans-serif;color:#0B5394">a) The cost of getting IPv4 addresses becomes un-bearable (as would be if they have to be acquired from the Transfer market) </span></u></i><u><o:p></o:p></u></b></p>
<p class="MsoNormal"><b><i><u><span style="font-family:"Arial",sans-serif;color:#0B5394">b) There are no IPv4 addresses to be gotten, anywhere (even if you have money to buy them)</span></u></i><u><o:p></o:p></u></b></p>
<p class="MsoNormal"><b><i><u><span style="font-family:"Arial",sans-serif;color:#0B5394">c) The network's owners have this blinding insight of the obvious that the IPv4 game is an un-winable one and IPv6 is the only sustainable way</span></u></i><u><o:p></o:p></u></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">This is why in the policy proposals before AfriNIC at the moment, there is a policy that is designed to effectively repeal most of the aspects of
the IPv4 soft landing policy. Because to do anything else, and to extend the life of v4, is not helping the continent, it is hurting us, and it is leaving us further and further behind the rest of the world – the proof is plain to see on the global IPv6 adoption
maps, and cannot be disputed.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">There are those that would argue that preserving some v4 for new comers is the “fair” thing to do, I would argue that let the v4 be used by those
who can use it today, to enable their customers, and when it runs out, let us progress forward. For people who argue that holding v4 space back for some unknown future when people will be ready to use it, is simply not a valid argument, especially when there
are entities who can use the remaining v4 to actually get rid of NAT and service end users. To extend the soft landing policies and artificially slow the depletion of v4 at this stage may help some ISP’s in the future – but it damages the continent and it
damages Internet deployment going forward – in short, in my view it is drastically short sighted.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">For reference purposes, the following blog which was published by AfriNIC based on content from my facebook page may be of interest:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><a href="http://www.afrinic.net/blog/159-getting-africa-s-ipv6-deployment-on-track">http://www.afrinic.net/blog/159-getting-africa-s-ipv6-deployment-on-track</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">With regards to the policy about depletion of v4 space, I refer to the following URL. This is the policy that is still under discussion as authorised
by myself, Kris Seeburn, Mark Elkins, Michele McCann and John Walubengo. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><a href="http://www.afrinic.net/en/community/policy-development/policy-proposals/1623-soft-landing-overhaul">http://www.afrinic.net/en/community/policy-development/policy-proposals/1623-soft-landing-overhaul</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Anyway – happy to continue the discussion.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Kevin Kamonye [mailto:kevin.kamonye@gmail.com]
<br>
<b>Sent:</b> 11 October 2016 15:17<br>
<b>To:</b> KICTAnet ICT Policy Discussions <kictanet@lists.kictanet.or.ke><br>
<b>Cc:</b> General Discussions of AFRINIC <community-discuss@afrinic.net>; Barrack Otieno <otieno.barrack@gmail.com><br>
<b>Subject:</b> [Community-Discuss] IPv6 Chapter 254<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">As always, thanks Ali and team for breathing some life into this one.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">My story with IPv6 started much longer than I can remember. The key moment, however, came in 2010/2011 when the hype hit its peak due to the then projected exhaustion of IANA's
central pool (officially announced in 3/02/2011). I was working at KDN at the time and being the largest IP transit provider in the region, a decision was agreed by all that we had to move quick - I think mostly to avoid potential embarrassment :) Our then
HOD David W. K., and I sincerely applaud him for the work he has put into building the Telecom Industry in the region, got wind of an Afrinic IPv6 Workshop in Ghana and 13 days later another very commendable colleague and myself were in that class and it all
went superbly well.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">The problem for me started a few weeks after I got back because I realised that there really wasn't a particular motivation for us to get the other providers to respond (though
the hard-core techies like us did some 'test' peering here and there). We even conducted a major upgrade on KDN's infrastructure at KIXP to ensure that all ISPs could get at least 1Gbps capacity ( though this was mostly driven by the Google Youtube Cache that
we deployed to handle the post-Seacom Internet traffic explosion in 254 and region). We also pursued ISPs in the region through forums such as AfPIF, ISOC etc. but the matter collapsed mostly due to natural causes.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">In short, I would say that there will never be a major crisis as regards to IPv4 exhaustion. Techies will do their thing of patching networks until they can't do it anymore and
then they will switch the rest of the population to IPv6. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">What we can do for now is to follow in the example of formulating the policies, which I can volunteer some of my time as would be needed.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">Lastly, I will quote from <a href="https://www.linkedin.com/pulse/ipv4-exhaustion-5-implications-africa-running-out-last-mukom-tamon">this</a> article by one of the guys that led
us through the training at NIITA back in 2011 (and I advise going it through in full if you want to learn more of IPv6 in Africa)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">Implication #3: Driving Complacency in Africa Towards IPv6 Adoption</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394"><img border="0" width="544" height="259" style="width:5.6666in;height:2.6979in" id="_x0000_i1025" src="cid:image002.png@01D22492.9AA55F80" alt="Inline images 1"></span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">So long as it is still possible and easy to get IPv4 addresses, 95% of network operators will do so; humans (and the organisations that they make up) don't change easily. Particularly,
organisations fixated on short term results will fail to realise that using every every single IPv4 address available to AFRINIC is not enough for us to catch up with the rest of the world. Not being able to look beyond a the proverbial tree to the forest,
it is easy to totally be blind to drastic change in resource availability that will result if one of Africa's large mobile telecommunications companies (say MTN) decides to remove NAT on their mobile networks and give each mobile user a true Internet access
experience using public IP addresses (I didn't think it was possible until experienced it for myself in Dar es Salaam last year with Airtel).</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">Networks will move to deploy IPv6 under the following influences:</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">a) The cost of getting IPv4 addresses becomes un-bearable (as would be if they have to be acquired from the Transfer market) </span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">b) There are no IPv4 addresses to be gotten, anywhere (even if you have money to buy them)</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">c) The network's owners have this blinding insight of the obvious that the IPv4 game is an un-winable one and IPv6 is the only sustainable way</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">d) Some powerful entity forces them (by mandates or by incentives) to deploy IPv6 (like gov't IT regulators)</span></i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif;color:#0B5394">For most African companies, scenarios (a & b) are unlikely to happen in next 2 – 3 years (unless the shell companies increase and succeed in getting addresses which depletes
AFRINIC's current space). Only a few network operators to my knowledge pay anything other that lip service to scenario (c) and the only party that can make scenario (d) happen (gov't regulators) still largely don't know how to go about it (if you are an African
gov't IT leader and need help with this, I might be able to help). Therefore, we have ourselves an IPv4 address resource curse!</span></i><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394">Good afternoon,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#0B5394">Kevin K.<o:p></o:p></span></b></p>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#0B5394"> K.<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Arial",sans-serif;color:#0B5394">+254720789158</span></b><span style="font-family:"Arial",sans-serif;color:#0B5394"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 10 October 2016 at 14:42, Barrack Otieno via kictanet <<a href="mailto:kictanet@lists.kictanet.or.ke" target="_blank">kictanet@lists.kictanet.or.ke</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">
<p class="MsoNormal">Dear Andrew,<br>
<br>
Many thanks for the feedback and for sharing the policy which i<br>
believe is a good starting point. Maybe we need a couple of town hall<br>
meetings with the business/corporate communicate and policy makers to<br>
break the resistance.<br>
<br>
Best Regards<br>
<br>
On 10/10/16, Andrew Alston <<a href="mailto:Andrew.Alston@liquidtelecom.com">Andrew.Alston@liquidtelecom.com</a>> wrote:<br>
> Hi Barrack,<br>
><br>
> We are also running native v6 on our FTTH network and continuing to deploy.<br>
> We plan to also shortly enable our public wifi networks in Kenya and are<br>
> working towards this (couple of vendor related issues that are being worked<br>
> on in this regard)<br>
><br>
> We are in a position to roll out IPv6 to any corporate customer and IP<br>
> transit customer who wishes it as well, and have some IPT customers actively<br>
> using IPv6 - Basically the entire Liquid network, irrespective of which<br>
> country we operate in, is fully V6 ready.<br>
><br>
> The reason the percentage point indicators in the stats I've given haven't<br>
> moved that much though is because convincing corporate customers to take<br>
> IPv6 is slightly more challenging, and our consumer rollouts in Kenya are<br>
> still relatively new (and as a result not yet large enough to seriously move<br>
> the penetration figures for the entire country). We are however working<br>
> with our customers to continue to increase the penetration percentages and<br>
> get the v6 adopted by the customers.<br>
><br>
> Thanks<br>
><br>
> Andrew<br>
<span class="gmail-">></span><br>
<span class="gmail-">></span><br>
<span class="gmail-">> -----Original Message-----</span><br>
<span class="gmail-">> From: Barrack Otieno [mailto:<a href="mailto:otieno.barrack@gmail.com">otieno.barrack@gmail.com</a>]</span><br>
<span class="gmail-">> Sent: 10 October 2016 14:29</span><br>
<span class="gmail-">> To: Walubengo J <<a href="mailto:jwalu@yahoo.com">jwalu@yahoo.com</a>>; KICTAnet ICT Policy Discussions</span><br>
<span class="gmail-">> <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>></span><br>
<span class="gmail-">> Cc: General Discussions of AFRINIC <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a>></span><br>
<span class="gmail-">> Subject: Re: [Community-Discuss] [kictanet] Liquid Telecom warns of looming</span><br>
<span class="gmail-">> address shortage - Daily Nation</span><br>
<span class="gmail-">></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">> Dear Walu et al?<br>
><br>
> Liquid has been on Zimbabwean Media over successfull V6 deployment.<br>
> Andrew , what is impeding deployment of the same in Kenya?<br>
><br>
> Regards<br>
><br>
> On 10/10/16, Walubengo J via kictanet <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>><br>
> wrote:<br>
>> @Mwendwa,>>><br>
>> What can you do?<br>
>> - Government Organizations: Coordinate with industry to support and<br>
>> promote awareness and educational activities. Adopt regulatory and<br>
>> economic incentives to encourage IPv6 adoption. Require IPv6<br>
>> compatibility in procurement procedures. Officially adopt IPv6 within<br>
>> your government agencies.<br>
>>>>>The above text is what we were looking for to include in our revised<br>
>>>>>.KE ICT Policy. How I wish you had shared this earlier :-)<br>
>> walu.<br>
>><br>
>> From: Mwendwa Kivuva via kictanet<br>
>> <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>><br>
>> To: <a href="mailto:jwalu@yahoo.com">jwalu@yahoo.com</a><br>
>> Cc: Mwendwa Kivuva <<a href="mailto:Kivuva@transworldafrica.com">Kivuva@transworldafrica.com</a>>; General Discussions<br>
>> of AFRINIC <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a>><br>
>> Sent: Monday, October 10, 2016 11:55 AM<br>
>> Subject: Re: [kictanet] [Community-Discuss] Liquid Telecom warns of<br>
>> looming address shortage - Daily Nation<br>
>><br>
>> This is an extremely important debate for the continent. Thank you Ali<br>
>> for that.<br>
>> Some of these issues have been debated thoroughly in several forums.<br>
>> It's very important we continue debating them until we see an<br>
>> exponential growth of IPv6 in the continent.To answer a few questions,<br>
>> there is a clear justification on why it is necessary to migrate to IPv6.<br>
>> Among them:<br>
>> - There are no enough IPv4 remaining for everyone. There are more<br>
>> devices, and people on earth than IPv4. Maximum IPv4 addresses are<br>
>> 4billion.<br>
>> Population of Earth is 7.3Billion. Maximum IPv6 address 3.4×10 38<br>
>> - Migration will not happen overnight since the recommended<br>
>> implementation is dual-stacking; that is, running IPv4 and IPv6 in<br>
>> parallel.<br>
>> We are not telling people to do away with IPv4, but to run the two<br>
>> protocols in parallel.<br>
>> - To be a producer of information, you cannot use a shared IP, you<br>
>> need a dedicated IP. This has been a big challenge in the continent.<br>
>> We have stifled innovation by using shared IPs.<br>
>> - There are many services now around the world which are IPv6 only<br>
>> website and services. If you are not on IPv6, you cannot get to these<br>
>> networks. Africa may get into what I can call "Information dark age"<br>
>> if we cannot acess some parts of the Internet.<br>
>> - IPv6 is necessary for business growth. How? How will your<br>
>> business scale when IPv4 has run out?<br>
>> What has AFRINIC done to bridge the gap?1. Trainings. This year alone,<br>
>> AFRINIC is conducting free IPv6 trainings to over 23 countries across<br>
>> the continent. Kenya was among the beneficiaries. Check this link<br>
>> <a href="http://www.afrinic.net/services/training" target="_blank">http://www.afrinic.net/services/training</a><br>
>> AFRINIC has an extensive training program provides free training to<br>
>> over 600 network engineers per year on Internet Number Resources<br>
>> Management (INRM) and IPv6 Planning and Deployment. Our training<br>
>> courses are always growing to support the technologies related to<br>
>> Internet resources, including DNSSEC & RPKI. AFRINIC's IPv6 course are<br>
>> IPv6 Forum (Gold) Certified and are fully hands-on, making use of<br>
>> extensive IPv6 testbed access which gives participants hands-on<br>
>> experience on real equipment to configure, test and troubleshoot IPv6.<br>
>><br>
>> 2. AFRINIC has a Government Working Group (AfGWG). Here government<br>
>> players are brought together to be sensitized on the need to push for<br>
>> IPv6 adoption, and rollout of IXPs, among other. Here is the link<br>
>> <a href="https://meeting.afrinic.net/afgwg/" target="_blank">https://meeting.afrinic.net/afgwg/</a><br>
>> 3. Issuance of v6 blocks to ISPs. All ISPs have been issued V6 blocks<br>
>> by AFRINIC. What we should be seeing now is clients insisting they<br>
>> want the ISPs to pass the benefits to the end users.<br>
>> What can you do?<br>
>> - Government Organizations: Coordinate with industry to support and<br>
>> promote awareness and educational activities. Adopt regulatory and<br>
>> economic incentives to encourage IPv6 adoption. Require IPv6<br>
>> compatibility in procurement procedures. Officially adopt IPv6 within<br>
>> your government agencies.<br>
>> - Broadband Access Providers: Your customers want access to the<br>
>> entire Internet, and this means IPv4 and IPv6 websites. Offering full<br>
>> access requires running IPv4/IPv6 transition services and is a<br>
>> significant engineering project. Multiple transition technologies are<br>
>> available, and each provider needs to make their own architectural<br>
>> decisions.<br>
>> - Internet Service Providers: Implement a plan that will allow your<br>
>> customers to connect to the Internet via IPv6 and IPv6/IPv4, not just<br>
>> IPv4.<br>
>> Businesses are beginning to ask for IPv6 over their existing Internet<br>
>> connections and for their co-located servers. Communicate with your<br>
>> peers and vendors about IPv6, and confirm their timelines for<br>
>> production IPv6 services.<br>
>> - Internet Content Providers: Content must be reachable to future<br>
>> Internet customers. Plan on serving content via IPv6 in addition to<br>
>> IPv4 as soon as possible.<br>
>> - Enterprise Customers: Email, web, and application servers must be<br>
>> reachable via IPv6 in addition to IPv4. Open a dialogue with your ISP<br>
>> about providing IPv6 services. Each organization must decide on<br>
>> timelines, and investment level will vary.<br>
>><br>
>> What is the role of Internet Service Providers (ISPs) in deploying<br>
>> IPv6?This link<br>
>> <a href="https://lists.afrinic.net/pipermail/afripv6-discuss/attachments/201607" target="_blank">
https://lists.afrinic.net/pipermail/afripv6-discuss/attachments/201607</a><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">>> 10/f7e693ac/attachment-0001.pdf contains some very interesting<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">>> statistics and findings on V6 deployments around the world, shared at<br>
>> the OECD Ministerial Meeting in June2016. One lesson we can learn from<br>
>> this is work very closely with ISPs. That seems to be the solution in<br>
>> the success stories.<br>
>><br>
>> *Some statistics on deployments*Belgium 55.11%,Germany 34.50%,United<br>
>> States 32.83%Greece 28.53%Portugal 25.80%Ecuador 20.8%,Peru<br>
>> 19.35%,Estonia 17,32%Japan 16.61%,Canada 9.83%Norway 6.65%Bolivia<br>
>> 3.8%Italy 0.73%Spain 0.7%Denmark 0.61% Some interesting findings is<br>
>> that deployment depends on the large ISPs uptake of v6 regardless of<br>
>> economic circumstances. e.g Peru has a lower per capita but has more<br>
>> deployment than Norway. Portugal with $22,000/capita and Greece<br>
>> $21,000/capita are outperforming Denmark with $60,000/capita. Canada<br>
>> $45,000/capita is trailing Estonia with $19,000/capita.<br>
>> In the success stories, the majority of the commercial access market<br>
>> products have IPv6 enabled by default, and competing products have<br>
>> matching features.<br>
>><br>
>> Regards<br>
>><br>
>> ______________________<br>
>> Mwendwa Kivuva, Nairobi, Kenya<br>
>> <a href="http://twitter.com/lordmwesh" target="_blank">twitter.com/lordmwesh</a><br>
>><br>
>><br>
>><br>
>> On 10 October 2016 at 11:44, Joseph Mucheru via kictanet<br>
>> <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>> wrote:<br>
>><br>
>> That said, do we have any experts on DOA? I personally believe this is<br>
>> the way forward...<br>
>> <a href="https://www.google.co.kr/url" target="_blank">https://www.google.co.kr/url</a>? sa=t&source=web&rct=j&url=<br>
>> <a href="https://www.itu.int/ITU-D/arb/" target="_blank">https://www.itu.int/ITU-D/arb/</a> ARO/2011/CyberSecurityForum-<br>
>> Eg/Docs/Doc11-Sorene_18-12- 2011.pptx&ved=0ahUKEwjsv8jc3c_<br>
>> PAhUU82MKHeXuALIQFggZMAA&usg= AFQjCNGzWEx4VBdgLQYrceW-<br>
>> eme4GvjaWwThanks On 10 Oct 2016 4:37 PM, "Ali Hussein via kictanet"<br>
>> <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a> > wrote:<br>
>><br>
>> Andrew<br>
>> Thank you so much for that informative response.<br>
>> So let's paint a scenario.<br>
>> Say, v4 exhausts in say 3 years. What are the implications for the<br>
>> continent esp those who will not have migrated?<br>
>> Ali HusseinPrincipalHussein & Associates+254 0713 601113<br>
>> Twitter: @AliHKassimSkype: abu-jomoLinkedIn: <a href="http://ke.linkedin.c" target="_blank">http://ke.linkedin.c</a><br>
>> om/in/alihkassim<br>
>><br>
>> "Discovery consists in seeing what everyone else has seen and thinking<br>
>> what no one else has thought". ~ Albert Szent-Györgyi Sent from my<br>
>> iPad On 10 Oct 2016, at 9:25 AM, Andrew Alston<br>
>> <<a href="mailto:Andrew.Alston@liquidtelecom.c%20om">Andrew.Alston@liquidtelecom.c om</a>><br>
>> wrote:<br>
>><br>
>><br>
>> Hi Ali, If I may respond here. Firstly – I think we need to be<br>
>> careful about referring to blanket transition – what Liquid has said<br>
>> is, we have to be ready with dual-stack networks. As v4 runs out –<br>
>> that dual-stack becomes more and more critical because it will enable<br>
>> the full transition when the time comes for it. How soon that will<br>
>> come is hard to say – but it is coming. What are the major<br>
>> impediments? There are 2 or 3 major points<br>
>> here: a.) Lack of will to actually do it – it takes work, it takes<br>
>> time, it takes effort – and the will power to actually move beyond<br>
>> talking the talk into walking the walk doesn’t seem to be thereb.)<br>
>> Lack of understanding/skill – The fact is that implementing v6 vs<br>
>> implementing v4 – it’s just another protocol, same routing, same<br>
>> everything. But there is a fear factor walking into something that is<br>
>> misunderstood. That lack of understanding that you can build this<br>
>> simultaneously in the same way you build v4, creates the fear factor.<br>
>> The fear of handling addressing plans in hexadecimal is also<br>
>> prohibiting growth. I run into that one a lot – people having issues<br>
>> with the address planning.c.) The last question is the million<br>
>> dollar one – because the reality is – all it takes is will power and a<br>
>> willingness to actually take some action. The simple fact is – we had<br>
>> a relatively small team on this – we committed a bunch of hours – we<br>
>> stuck our heads down and did it. We did not spend money – other than<br>
>> the cost of the time (which is an OPEX cost admittedly). We said<br>
>> ourselves deadlines and we DID it. There are those who propose that<br>
>> setting policies to try and force<br>
>> v6 is workable – it’s not – unless the will is there it will achieve<br>
>> nothing. People have to WANT this. It is a matter of desire and a<br>
>> matter of seeing the benefits – the benefits are future proofing –<br>
>> they are not based on revenue generation, but more revenue retention.<br>
>> And if anyone wants to see just how much impact you can have with a<br>
>> small team that actually has the desire, please see the following<br>
>> stats out of Zimbabwe (our largest consumer market)<br>
>> <a href="http://stats.labs.apnic.net/ip" target="_blank">http://stats.labs.apnic.net/ip</a><br>
>> v6/ZW?b=20161001&d=10<a href="http://stats.labs.apnic.net/ip" target="_blank">http://stats.labs.apnic.net/ip</a><br>
>> v6/AS30969?b=20161001&d=10<a href="http://stats.labs.apnic.net/ip" target="_blank">http://stats.labs.apnic.net/ip</a><br>
>> v6/XB?b=20161001&d=10 (I see things have slightly dropped off today,<br>
>> these stats tend to fluctuate, but fact is – it’s out there and it<br>
>> work’s. Andrew From: Ali Hussein <<a href="mailto:ali@hussein.me.ke">ali@hussein.me.ke</a>><br>
>> Date: Monday, 10 October 2016 at 09:01<br>
>> To: KICTAnet ICT Policy Discussions <<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a> >,<br>
>> General Discussions of AFRINIC <<a href="mailto:community-discuss@afrinic.net">community-discuss@afrinic.net</a> ><br>
>> Subject: [Community-Discuss] Liquid Telecom warns of looming address<br>
>> shortage - Daily Nation Dear listersGreetings and apologies for<br>
>> cross-posting.Internet service provider Liquid Telecom Kenya has<br>
>> warned that Africa is set to run out of Internet Protocol (IP)<br>
>> addresses as early as next year, potentially slowing down digital<br>
>> growth in the continent.Read on:-<a href="http://www.nation.co.ke/busine" target="_blank">http://www.nation.co.ke/busine</a><br>
>> ss/Liquid-Telecom-warns-of-<br>
>> looming-address-shortage/996- 3410850-format-xhtml-aub5sm/<br>
>> index.htmlCouple of questions:-1. How involved are we as a community<br>
>> in ensuring the smooth transition from IPV4 to IPV6?2. What have been<br>
>> the major impediments to the successful migration?3. How can we move<br>
>> the needle faster?Ali Hussein<br>
>> Tel: +254 713 601113<br>
>><br>
>> ______________________________ _________________ kictanet mailing list<br>
>> <a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>
<a href="https://lists.kictanet.or.ke/m" target="_blank">https://lists.kictanet.or.ke/m</a><br>
>> ailman/listinfo/kictanet<br>
>><br>
>> Unsubscribe or change your options at <a href="https://lists.kictanet.or.ke/m" target="_blank">
https://lists.kictanet.or.ke/m</a><br>
>> ailman/options/kictanet/joe%40 <a href="http://mucheru.com" target="_blank">mucheru.com</a><br>
>><br>
>> The Kenya ICT Action Network (KICTANet) is a multi-stakeholder<br>
>> platform for people and institutions interested and involved in ICT<br>
>> policy and regulation. The network aims to act as a catalyst for<br>
>> reform in the ICT sector in support of the national aim of ICT enabled<br>
>> growth and development.<br>
>><br>
>> KICTANetiquette : Adhere to the same standards of acceptable behaviors<br>
>> online that you follow in real life: respect people's times and<br>
>> bandwidth, share knowledge, don't flame or abuse or personalize,<br>
>> respect privacy, do not spam, do not market your wares or qualifications.<br>
>><br>
>><br>
>> ______________________________ _________________ kictanet mailing list<br>
>> <a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>
<a href="https://lists.kictanet.or.ke/" target="_blank">https://lists.kictanet.or.ke/</a><br>
>> mailman/listinfo/kictanet<br>
>><br>
>> Unsubscribe or change your options at <a href="https://lists.kictanet.or.ke/" target="_blank">
https://lists.kictanet.or.ke/</a><br>
>> mailman/options/kictanet/ kivuva%<a href="http://40transworldafrica.com" target="_blank">40transworldafrica.com</a><br>
>><br>
>> The Kenya ICT Action Network (KICTANet) is a multi-stakeholder<br>
>> platform for people and institutions interested and involved in ICT<br>
>> policy and regulation. The network aims to act as a catalyst for<br>
>> reform in the ICT sector in support of the national aim of ICT enabled<br>
>> growth and development.<br>
>><br>
>> KICTANetiquette : Adhere to the same standards of acceptable behaviors<br>
>> online that you follow in real life: respect people's times and<br>
>> bandwidth, share knowledge, don't flame or abuse or personalize,<br>
>> respect privacy, do not spam, do not market your wares or qualifications.<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> kictanet mailing list<br>
>> <a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a><br>
>> <a href="https://lists.kictanet.or.ke/mailman/listinfo/kictanet" target="_blank">
https://lists.kictanet.or.ke/mailman/listinfo/kictanet</a><br>
>><br>
>> Unsubscribe or change your options at<br>
>> <a href="https://lists.kictanet.or.ke/mailman/options/kictanet/jwalu%40yahoo.co" target="_blank">
https://lists.kictanet.or.ke/mailman/options/kictanet/jwalu%40yahoo.co</a><br>
>> m<br>
>><br>
>> The Kenya ICT Action Network (KICTANet) is a multi-stakeholder<br>
>> platform for people and institutions interested and involved in ICT<br>
>> policy and regulation. The network aims to act as a catalyst for<br>
>> reform in the ICT sector in support of the national aim of ICT enabled<br>
>> growth and development.<br>
>><br>
>> KICTANetiquette : Adhere to the same standards of acceptable behaviors<br>
>> online that you follow in real life: respect people's times and<br>
>> bandwidth, share knowledge, don't flame or abuse or personalize,<br>
>> respect privacy, do not spam, do not market your wares or qualifications.<br>
>><br>
>><br>
><br>
><br>
> --<br>
> Barrack O. Otieno<br>
> +254721325277<br>
> +254733206359<br>
> Skype: barrack.otieno<br>
> PGP ID: 0x2611D86A<br>
><br>
> _______________________________________________<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">> Community-Discuss mailing list<br>
> <a href="mailto:Community-Discuss@afrinic.net">Community-Discuss@afrinic.net</a><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/community-discuss" target="_blank">
https://lists.afrinic.net/mailman/listinfo/community-discuss</a><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">><br>
<br>
<br>
--<br>
Barrack O. Otieno<br>
+254721325277<br>
+254733206359<br>
Skype: barrack.otieno<br>
PGP ID: 0x2611D86A<br>
<br>
_______________________________________________<br>
kictanet mailing list<br>
<a href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a><br>
<a href="https://lists.kictanet.or.ke/mailman/listinfo/kictanet" target="_blank">https://lists.kictanet.or.ke/mailman/listinfo/kictanet</a><br>
<br>
Unsubscribe or change your options at <a href="https://lists.kictanet.or.ke/mailman/options/kictanet/kevin.kamonye%40gmail.com" target="_blank">
https://lists.kictanet.or.ke/mailman/options/kictanet/kevin.kamonye%40gmail.com</a><br>
<br>
The Kenya ICT Action Network (KICTANet) is a multi-stakeholder platform for people and institutions interested and involved in ICT policy and regulation. The network aims to act as a catalyst for reform in the ICT sector in support of the national aim of ICT
enabled growth and development.<br>
<br>
KICTANetiquette : Adhere to the same standards of acceptable behaviors online that you follow in real life: respect people's times and bandwidth, share knowledge, don't flame or abuse or personalize, respect privacy, do not spam, do not market your wares or
qualifications.<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>