<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:"Times New Roman \(Cuerpo en alfa";
panose-1:2 2 6 3 5 4 5 2 3 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;}
span.EstiloCorreo18
{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='font-size:12.0pt;mso-fareast-language:EN-US'>Nice!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>For those that are worried about literal addresses, is not so easy to they get broken.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Android devices have a CLAT, so even if the network is providing NAT64+DNS64, actually the device is using 464XLAT.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>Apple devices don’t have a CLAT, but the apps are mandated to support IPv6-only and even if they don’t do, for example you type a literal address, happy eyeballs v2 (RFC8305) uses something similar to bump-in-the-host, that has the same effect (in most of the cases).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>However, if the iOS device is used for tethering, to solve the problem to tethered devices, a CLAT is run for the tethered network.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>There is a lot of information about this in RFC8683, including considerations about using DNS privacy, VPNs, etc.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'>If you’re interested in this topic, I will be presenting a talk about RFC8683 and also a tutorial about IPv6-only with IPv4-as-a-Service in the next APNIC meeting, coincidently in Australia, in a few days:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><a href="https://2020.apricot.net/">https://2020.apricot.net/</a><o:p></o:p></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black'>Regards,<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;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:12.0pt;color:black;mso-fareast-language:EN-US'>@jordipalet<o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:EN-US'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 6/2/20 5:27, "AusNOG en nombre de Russell Langton" <<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a> en nombre de <a href="mailto:russell3901@gmail.com">russell3901@gmail.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><div><div><div><p class=MsoNormal style='margin-left:35.4pt'>Hi AusNOGgers, <o:p></o:p></p></div><div><p class=MsoNormal style='margin-left:35.4pt'><br>Following our dual-stack enablement in Aug 2016, Telstra is proud the announce the second step in our transition to IPv6 - IPv6 Single-Stack deployment on Telstra wireless.<br>This means shortly when you attach your mobile to Telstra.WAP APN it will only get an Ipv6 address NO Ipv4 address.<br> <br> Note that the enablement is currently targeted at both pre and post-paid services.<br> <br>This deployment of Ipv6 Single-Stack is only for Telstra.WAP APN which is primarily used by handsets and tablets.<br>Telstra.internet APN is primary used for dongles, BYOD tablets, modems etc. so this will remain as dual-stack.<br> <br> * timeframe * <br>We are planning to start the deployment on 10/2 and 13/2 in South Australia.<br>Further deployments in other states are planned by the end of Feb and will be advised to the list.<br> <br>* device scope *<br>Any Mobile device that is configured as Dual Stack for Telstra.wap, either default or manually configured.<br>The scope of this change will impact devices that are using the latest version of the operating system, either out of the box or through an OS update.<br>It will also impact Android devices which are configured for Telstra.wap and manually configured for dual-stack.<br> <br> * Things to be aware of *<br>- This is a network based solution, when it receives a dual-stack request it will only allocate a Ipv6 Address.<br>- Services on Telstra.WAP APN will only get a Ipv6 address(No Ipv4)<br>- This solution is using a DNS64+NAT64 setup.<br>- If your website/content/other is advertising a AAAA Ipv6 DNS record, <br> => This may cause problems if your website is not 100% Ipv6<br>- Impact to apps is expected to be limited as all apps submitted to Apple store have been DNS64/NAT64 mandated since June 1 2016.<br> <br> * Basic flow *<br>- If Alice is connecting to a website with a Ipv6 AAAA DNS record, It will be a pure Ipv6 connection.<br>- If Alice is connecting to a website with only a A DNS record, our DNS will spoof the website address with a Well Known Prefix (WKP) so it routes to the NAT64 gateway to Ipv4 internet.<br>- If Alice is connecting to a Ipv4 address literal(x.x.x.x), It may fail.<br> <br> * Why is AusNOG hearing about this now *<br>This is a major step in Telstra's Ipv6 journey, and with all things there will be teething issues when we launch.<br>We are aiming to work with community forums like AusNOG and Whirlpool to ensure this is a smooth transition. <br> <br> *Contacting us* <br>For any assistance, Please refer to;<br>For apps which appear broken, it may not support ipv6 DNS64+NAT64, contact your application support<br>CrowdSupport - <a href="https://crowdsupport.telstra.com.au/t5/Telstra-IPv6-Wireless-Network/bd-p/IPv6" target="_blank">https://crowdsupport.telstra.com.au/t5/Telstra-IPv6-Wireless-Network/bd-p/IPv6</a><br>or reach out directly to Telstra Ipv6 Engineering team - <a href="mailto:ipv6wirelessdeployment@team.telstra.com" target="_blank">ipv6wirelessdeployment@team.telstra.com</a><o:p></o:p></p></div></div></div><p class=MsoNormal style='margin-left:35.4pt'>_______________________________________________ AusNOG mailing list AusNOG@lists.ausnog.net http://lists.ausnog.net/mailman/listinfo/ausnog <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>