<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: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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (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:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Congratulations are in order Andrew! My pleasure associating with yourself and Liquid Telecom Kenya!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Rgds,<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif""><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Dan Kwach – </span></b><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">General Manager</span><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica","sans-serif"">Sameer Industrial Park, Junction Mombasa and Enterprise Road, Nairobi.</span><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D">T:</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D"> +254 732 199 002
</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D">D:</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D"> +254 732 199 617</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D">M:</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#0D0D0D"> +254 736 373 662</span><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">E</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">: </span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#7030A0"><a href="mailto:dan.kwach@eastafricadatacentre.com"><span style="color:blue">dan.kwach@eastafricadatacentre.com</span></a> </span><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Arial","sans-serif""><img border="0" width="200" height="83" id="Picture_x0020_1" src="cid:image001.png@01D1F4AF.DA4823B0" alt="cid:0150B269-C46E-4A30-A05B-2FA21DDE639A"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">W:
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif""><a href="http://www.eastafricadatacentre.com/"><span style="color:blue">www.eastafricadatacentre.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> afnog [mailto:afnog-bounces@afnog.org]
<b>On Behalf Of </b>Andrew Alston<br>
<b>Sent:</b> Friday, August 12, 2016 1:32 PM<br>
<b>To:</b> Mark Tinka; afnog@afnog.org<br>
<b>Subject:</b> Re: [afnog] IPv6 Native Mass Market Deployment arrives in Kenya!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Hi Mark,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">There have been some interesting challenges along the way to getting this working, but for the most part it was surprisingly smooth.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">A few caveats that we found along the way.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Firstly, we by default allocate a /48 per customer. We do this because I strongly subscribe to the belief that if there is a possibility that someone may want to subnet, they should get at minimum
a /56, and if they are an enterprise, a /48 is kinda bare minimum. It was therefore simply easier to stick to a single prefix length size and go /48 all the way.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">The next issue was, enabling the SLAAC to the customer (since that only works on /64s), and to do this, we’re pushing config to the CPE’s that takes a /64 out of the /48 that’s routed and automagically
puts it on the LAN interface with SLAAC enabled. This works perfectly with the CPE’s we are using, and we’re testing it with other CPE’s to have more variety of choice of CPE as well.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Sadly, the CPE’s we’ve seen did NOT do this straight out of the box so we have to push a config on installation when a new customer connects.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">The next biggest issue was customers who for some bizarre reason wanted to run CPE’s behind the CPE’s supplied (effectively doing dual-NAT on the v4), and if those don’t support v6 or aren’t configured
for it, there isn’t a huge amount we can do.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">With regards to actual machines picking up the v6 where the above scenario isn’t happening, zero problems, and we’re actively seeing a large number of V6 DNS requests to our DNS servers coming from
the customers and we’ve seen a massive increase in our V6 traffic levels since enabling this – so we know for a fact customers are actually using the v6 in fairly large volumes. In particular I see a LOT of v6 to Google, Facebook, Amazon AWS, and various
other sites.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">So far so good though, but we’re constantly monitoring and hopefully in the next few weeks once we have collected a lot more statistics I’ll be able to share those as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext;mso-fareast-language:EN-GB">From:</span></b><span style="color:windowtext;mso-fareast-language:EN-GB"> Mark Tinka [<a href="mailto:mark.tinka@seacom.mu">mailto:mark.tinka@seacom.mu</a>]
<br>
<b>Sent:</b> 12 August 2016 13:07<br>
<b>To:</b> Andrew Alston <<a href="mailto:Andrew.Alston@liquidtelecom.com">Andrew.Alston@liquidtelecom.com</a>>;
<a href="mailto:afnog@afnog.org">afnog@afnog.org</a><br>
<b>Subject:</b> Re: [afnog] IPv6 Native Mass Market Deployment arrives in Kenya!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="EN-GB" style="font-family:"Tahoma","sans-serif"">Hi Andrew.<br>
<br>
Many congratulations. This is, indeed, a major step, and for me, the first of its kind in eastern and southern Africa (mostly because I'm not sure how far this is going in northern and western Africa - otherwise I'd say the whole of Africa).<br>
<br>
I've been challenging a number of broadband ISP's and MNO's in Africa in recent years to put a lot more focus and energy in getting consumers IPv6-enabled, so to hear that Liquid have succeeded in doing this in Kenya is very good news, indeed!<br>
<br>
It would be good to hear of challenges specifically around customer devices picking up IPv6 addresses, and potentially running into Happy Eyeball issues if at all. If you can share that as your experience grows, it would tell a good story.<br>
<br>
Once again, good work, Andrew and your team! I'm quite impressed to hear this!<br>
<br>
Mark.</span><span lang="EN-GB" style="font-size:12.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Tahoma","sans-serif"">On 12/Aug/16 11:45, Andrew Alston wrote:<o:p></o:p></span></p>
</div>
<blockquote style="margin-left:1.5pt;margin-top:6.0pt;margin-right:1.5pt;margin-bottom:6.0pt;background-color:null !important;color:null !important">
<p class="MsoNormal"><span lang="EN-GB">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">I thought I’d just share this with all of you because I view it as a fairly major step in the right direction for the continent.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Yesterday, Liquid Telecom turned on IPv6 to all its Kenyan home users using GPON and our FTTH / FTTB products. This was done in such a way that the customers didn’t need to configure anything themselves to enable it,
it was just there </span><span lang="EN-GB" style="font-family:Wingdings">J</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">The CPE’s are all pushed a configuration as well to SLAAC enable the LAN facing interface and doing v6 DNS distribution via ND (though we also have v6 DHCP serving V6 DNS and other-config-flag set on the ND, so it can
get the v6 DNS via either method if it doesn’t honor the other-config-flag)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Though, this is now a challenge to all the other ISP’s offering home user mass market products – v6 works – it’s time to start seeing more deployment
</span><span lang="EN-GB" style="font-family:Wingdings">J</span><span lang="EN-GB"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">We hope to have the v6 turned up shortly in Zimbabwe and other markets in the next few weeks as well.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"> <o:p></o:p></span></p>
</blockquote>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:12.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:EN-GB"><o:p> </o:p></span></p>
</div>
</body>
</html>