<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=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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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:11.0pt;
font-family:"Calibri",sans-serif;}
span.EstiloCorreo18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EstiloCorreo19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>I will strongly suggest not going to “only” NAT64/DNS64, but instead using 464XLAT, and even not using DNS64 in that case.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>If you just use NAT64/DNS64, you have the problems you mention when some apps use literals, old APIs, etc, and you may break DNSSEC. Those problems vanish with 464XLAT.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Recommended reading:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-nat64-deployment/</a><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>and also:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/">https://datatracker.ietf.org/doc/draft-ietf-v6ops-transition-ipv4aas/</a><o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:10.5pt;color:black'><br>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:10.5pt;color:black;mso-fareast-language:EN-US'>Jordi<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:10.5pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><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 style='margin-left:35.4pt'><b><span style='font-size:12.0pt;color:black'>De: </span></b><span style='font-size:12.0pt;color:black'>Mark Tinka <mark.tinka@seacom.mu><br><b>Fecha: </b>lunes, 3 de diciembre de 2018, 9:42<br><b>Para: </b>JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Diarmuid O Briain <diarmuid@obriain.com>, UIXP Techies <techies@uixp.co.ug>, <afnog@afnog.org><br><b>Asunto: </b>Re: [afnog] IPv6 transition mechanism used by ISP<o:p></o:p></span></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:35.4pt'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:35.4pt'>On 3/Dec/18 09:56, JORDI PALET MARTINEZ wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>The list is made from information provided by ISPs or publicly available, so that why there are no many more ISPs (not just in Africa, in other countries).</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US style='mso-fareast-language:EN-US'>I think in Africa, dual-stack is being used up to know as you still have sufficient IPv4 addresses … but of course this will change in the next few months.</span><o:p></o:p></p></blockquote><p class=MsoNormal style='margin-left:35.4pt'><br><span style='font-family:"Tahoma",sans-serif'>I can't speak to other ISP's, but I know that from the last ZAPF meeting in Cape Town last month, Ben (Workonline) had the whole meeting running on NAT64/DNS64. I only noticed because my VPN wasn't happy, but all other things worked perfectly, i.e., e-mail, WhatsApp, Instagram, iMessage, e.t.c. Most folk didn't even know it was an IPv6-only conference network.<br><br>As SEACOM, we've had NAT64/DNS64 as our transition mechanism since 2014. We deployed a bunch of translators across the entire backbone, in all of our major PoP's (Africa and Europe). These are running on Cisco ASR1006 routers, in production for close to 5 years now. But as you mention, because of the prevalence of IPv4 in Africa, we haven't yet seen anything pushing us hard to fire up any real traffic toward our translators. That said, when the day comes, we will be ready.<br><br>I am sure Andrew (Liquid) already has a plan, and I'm certain there are a ton of other ISP's in Africa that either have a plan or are working toward the same.<br><br>Mark.</span><br><br><o:p></o:p></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
http://www.theipv6company.com<br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</body></html>