<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px"><div id="yui_3_16_0_ym19_1_1475810623468_259199"><span>@Tony,</span></div><div id="yui_3_16_0_ym19_1_1475810623468_259197"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span id="yui_3_16_0_ym19_1_1475810623468_259105">rather than do a v4 to v6 tunnel, it maybe better (easier) to implement a dual-stack with your upstream provider. </span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span id="yui_3_16_0_ym19_1_1475810623468_259234">That way you manage the transition better. For example, you may opt to leave your old clients on v4 while putting your new clients on v6 as u gain confidence with v6 implementations. Your upstream provider then seamlessly handles both types of traffic since they are running dual-stack system.</span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span id="yui_3_16_0_ym19_1_1475810623468_259217">ditch your upstream provider if they cannot offer your a dual-stack system.</span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span><br></span></div><div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259106"><span id="yui_3_16_0_ym19_1_1475810623468_259253">walu.</span></div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1475810623468_259086" dir="ltr">nb: v6 implementation is going to be (may already be) a big deal sooner, rather than later and we tried to capture this in the new ICT policy. Hope it was retained.<br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1475810623468_259242" style="display: block;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1475810623468_259241"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1475810623468_259240"> <div dir="ltr" id="yui_3_16_0_ym19_1_1475810623468_259239"> <font size="2" face="Arial" id="yui_3_16_0_ym19_1_1475810623468_259238"> <hr size="1" id="yui_3_16_0_ym19_1_1475810623468_259237"> <b><span style="font-weight:bold;">From:</span></b> Tony White via kictanet <kictanet@lists.kictanet.or.ke><br> <b><span style="font-weight: bold;">To:</span></b> jwalu@yahoo.com <br><b><span style="font-weight: bold;">Cc:</span></b> Tony White <tony.mzungu@gmail.com><br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, October 10, 2016 11:08 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [kictanet] Liquid Telecom warns of looming address shortage - Daily Nation<br> </font> </div> <div class="y_msg_container"><br>Ali,<br clear="none"><br clear="none">Short answer: IPv6 is better for clients: our ISPs should all agree to<br clear="none">begin allocating IPv6 subnets to clients.<br clear="none"><br clear="none">TL;DR:<br clear="none"><br clear="none">IPv6 is not compatible with IPv4, but all modern software is IPv6<br clear="none">capable - ie. software implementing IPv6 stacks is incorporated in<br clear="none">both end-user (PCs, tablets, phones, etc.) and network devices<br clear="none">(routers, switches, etc.) - so a transition to IPv6 should be<br clear="none">relatively painless - indeed, even easier than IPv4 as the 'tricks' we<br clear="none">use to extend IPv4 space, such as NAT, are no longer required. DHCP<br clear="none">is also (almost) redundant as the 128 bits of IPv6 addressing neatly<br clear="none">divides into 2 blocks of 64 bits - the first block of 64 bits<br clear="none">describing the subnet (which is allocated to the client by the ISP),<br clear="none">and the second block of 64 bits is the host address space available to<br clear="none">the client - which, by not much coincidence, is the size of the MAC<br clear="none">address space. Phew! - what this means is that a device (PC, etc.)<br clear="none">IPv6 host address can be it's MAC address - no DHCP or ARP requests<br clear="none">required ;)<br clear="none"><br clear="none">So where's the problem? - Well, as the majority of the 'rest of the<br clear="none">internet' is still operating on IPv4 addressing, the ISP (or their<br clear="none">upstream) may need to implement IPv6 to IPv4 translation - and this is<br clear="none">not so simple: if the 'other end' is also an IPv6 address, but there<br clear="none">is no direct IPv6 route between the two, then an IPv6 to IPv4 'tunnel'<br clear="none">is needed to transfer the IPv6 packets through an IPv4 routing. If<br clear="none">the 'other end' is only an IPv4 address, then the ISP needs to use<br clear="none">NAT64 (and other mechanisms) to translate between the two different<br clear="none">addressing schemes.<br clear="none"><br clear="none">Some numbers: 128 bits, split into 2 groups of 64 bits, is<br clear="none">approximately 18,446,744,073,709,600,000 IPv6 subnet prefixes, and<br clear="none">18,446,744,073,709,600,000 hosts per subnet.<br clear="none"><br clear="none">So to reiterate the short answer - IPv6 is a good thing for clients,<br clear="none">but introduces some challenges for ISPs.<br clear="none"><br clear="none">Thanks for waking up my brain this fine Monday morning ;)<br clear="none">Cheers,<br clear="none">Tony<br clear="none"><br clear="none"><br clear="none"><br clear="none">On 10/10/2016, Ali Hussein via kictanet <<a shape="rect" ymailto="mailto:kictanet@lists.kictanet.or.ke" href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a>> wrote:<br clear="none">> Dear listers<br clear="none">><br clear="none">> Greetings and apologies for cross-posting.<br clear="none">><br clear="none">> Internet service provider Liquid Telecom Kenya has warned that Africa is<br clear="none">> set to run out of Internet Protocol (IP) addresses as early as next year,<br clear="none">> potentially slowing down digital growth in the continent.<br clear="none">><br clear="none">> Read on:-<br clear="none">><br clear="none">> <a shape="rect" href="http://www.nation.co.ke/business/Liquid-Telecom-warns-of-looming-address-shortage/996-3410850-format-xhtml-aub5sm/index.html" target="_blank">http://www.nation.co.ke/business/Liquid-Telecom-warns-of-looming-address-shortage/996-3410850-format-xhtml-aub5sm/index.html</a><br clear="none">><br clear="none">> Couple of questions:-<br clear="none">><br clear="none">> 1. How involved are we as a community in ensuring the smooth transition<br clear="none">> from IPV4 to IPV6?<br clear="none">><br clear="none">> 2. What have been the major impediments to the successful migration?<br clear="none">><br clear="none">> 3. How can we move the needle faster?<br clear="none">><br clear="none">> Ali Hussein<br clear="none">> Tel: +254 713 601113<br clear="none">><br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Tony White<div class="yqt3872443005" id="yqtfd08376"><br clear="none"><br clear="none">_______________________________________________<br clear="none">kictanet mailing list<br clear="none"><a shape="rect" ymailto="mailto:kictanet@lists.kictanet.or.ke" href="mailto:kictanet@lists.kictanet.or.ke">kictanet@lists.kictanet.or.ke</a><br clear="none"><a shape="rect" href="https://lists.kictanet.or.ke/mailman/listinfo/kictanet" target="_blank">https://lists.kictanet.or.ke/mailman/listinfo/kictanet</a><br clear="none"><br clear="none">Unsubscribe or change your options at <a shape="rect" href="https://lists.kictanet.or.ke/mailman/options/kictanet/jwalu%40yahoo.com" target="_blank">https://lists.kictanet.or.ke/mailman/options/kictanet/jwalu%40yahoo.com</a><br clear="none"><br clear="none">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 clear="none"><br clear="none">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.<br clear="none"></div><br><br></div> </div> </div> </div></div></body></html>