<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div style="">Good news ! <br>
<br>
Patrick. <br>
NIC CI<br>
<br>
<br>
<br>
GNONKOTO Sent from my Samsung Galaxy smartphone.<br>
</div>
<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Send RPD mailing list submissions to<br>
rpd@afrinic.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
or, via email, send a message with subject or body 'help' to<br>
rpd-request@afrinic.net<br>
<br>
You can reach the person managing the list at<br>
rpd-owner@afrinic.net<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of RPD digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: IPv6 Native Mass Market Deployment arrives in Kenya!<br>
(Andrew Alston)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 15 Aug 2016 11:37:38 +0000<br>
From: Andrew Alston <Andrew.Alston@liquidtelecom.com><br>
To: Tigabu Dagne <tgbdagne@gmail.com>, Lu Heng<br>
<h.lu@anytimechinese.com><br>
Cc: "sm+afrinic@elandsys.com" <sm+afrinic@elandsys.com>, rpd<br>
<rpd@afrinic.net><br>
Subject: Re: [rpd] IPv6 Native Mass Market Deployment arrives in<br>
Kenya!<br>
Message-ID: <BE4CF897-177E-40D8-BFD1-0F099DA85C16@liquidtelecom.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Thanks for all the congrats guys.<br>
<br>
Lu, The home CPE?s DO support IPv6 and any device behind the CPE that supports getting V6 addresses via RA gets their addresses and off they go.<br>
<br>
In addition, while we do push DNS servers via RA on the CPE, we also set other-config-flag and run DHCPv6 with DNS servers only so that in the case of devices NOT supporting DNS via RA, they can get it via DHCP.<br>
<br>
Basically, client applies, client gets CPE from us, client plugs in, and if his device is V6 enabled behind that CPE, it just works ?<br>
<br>
Andrew<br>
<br>
<br>
From: Tigabu Dagne <tgbdagne@gmail.com><br>
Date: Monday, 15 August 2016 at 2:05 PM<br>
To: Lu Heng <h.lu@anytimechinese.com><br>
Cc: "sm+afrinic@elandsys.com" <sm+afrinic@elandsys.com>, rpd <rpd@afrinic.net><br>
Subject: Re: [rpd] IPv6 Native Mass Market Deployment arrives in Kenya!<br>
<br>
congrats!<br>
<br>
<br>
<br>
Thanks and Best regards,<br>
<br>
Tigabu Dagne (MSc Spatial Tech, MSc Info.Sc, MCSE- Private cloud, CCDP, CCNP, MCSA, CCDA, CCNA)<br>
Addis Ababa Institute of Technology<br>
Lecturer, School of Electrical and Computer Engineering<br>
Center for Information Technology and Scientific Computing (ITSC)<br>
Industries Training Coordinator, ITSC<br>
Mobile: +251-962-894496<br>
Addis Ababa, Ethiopia<br>
<br>
<br>
On Mon, Aug 15, 2016 at 1:55 PM, Lu Heng <h.lu@anytimechinese.com<mailto:h.lu@anytimechinese.com>> wrote:<br>
Hi<br>
<br>
Congrats!<br>
<br>
Curious to know how its being done though, if home router does not<br>
support ipv6, how IPv6 being used by end device?<br>
<br>
On Mon, Aug 15, 2016 at 3:39 AM, Kyle Spencer <kyle@stormzero.com<mailto:kyle@stormzero.com>> wrote:<br>
> Congrats!<br>
><br>
><br>
> On Aug 14, 2016 15:36, <sm+afrinic@elandsys.com<mailto:sm%2Bafrinic@elandsys.com>> wrote:<br>
>><br>
>> Hi Andrew,<br>
>> At 02:45 12-08-2016, Andrew Alston wrote:<br>
>>><br>
>>> I thought I'd just share this with all of you because I view it as a<br>
>>> fairly major step in the right direction for the continent.<br>
>>><br>
>>> Yesterday, Liquid Telecom turned on IPv6 to all its Kenyan home users<br>
>>> using GPON and our FTTH / FTTB products. This was done in such a way that<br>
>>> the customers didn't need to configure anything themselves to enable it, it<br>
>>> was just there J<br>
>><br>
>><br>
>> I would like to congratulate you and Liquid Telecom as it may be the first<br>
>> ISP in Africa turning on IPv6 for home users.<br>
>><br>
>> Regards,<br>
>> S. Moonesamy<br>
>><br>
>> _______________________________________________<br>
>> RPD mailing list<br>
>> RPD@afrinic.net<<a href="mailto:RPD@afrinic.net">mailto:RPD@afrinic.net</a>><br>
>> <a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
><br>
> _______________________________________________<br>
> RPD mailing list<br>
> RPD@afrinic.net<<a href="mailto:RPD@afrinic.net">mailto:RPD@afrinic.net</a>><br>
> <a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
><br>
<br>
<br>
--<br>
--<br>
Kind regards.<br>
Lu<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
RPD@afrinic.net<<a href="mailto:RPD@afrinic.net">mailto:RPD@afrinic.net</a>><br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://lists.afrinic.net/pipermail/rpd/attachments/20160815/0089bdfe/attachment-0001.html">https://lists.afrinic.net/pipermail/rpd/attachments/20160815/0089bdfe/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
RPD mailing list<br>
RPD@afrinic.net<br>
<a href="https://lists.afrinic.net/mailman/listinfo/rpd">https://lists.afrinic.net/mailman/listinfo/rpd</a><br>
<br>
<br>
------------------------------<br>
<br>
End of RPD Digest, Vol 119, Issue 11<br>
************************************<br>
Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération, par
conséquent l'ARTCI décline toute responsabilité au titre de ce message s'il a été altèré, déformé ou falsifié.<br>
</div>
</span></font>Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération,
par conséquent l'ARTCI décline toute responsabilité au titre de ce message s'il a été altèré, déformé ou falsifié.
</body>
</html>