<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;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.msipfooter3b88511e, li.msipfooter3b88511e, div.msipfooter3b88511e
{mso-style-name:msipfooter3b88511e;
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.EstiloCorreo20
{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:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=ES link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>My view on the 2<sup>nd</sup> one: I think SLAAC is sufficient!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'>I guess unless Android change their mind and develops/enables DHCPv6, this will not be useful.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:black;mso-fareast-language:ES-TRAD'>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'>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'>@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'><o:p> </o:p></span></p></div><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt'><o:p> </o:p></span></p><div><div><p class=MsoNormal style='margin-left:35.4pt'>El 14/5/20 13:59, "ipv6-wg en nombre de Jetten Raymond" <<a href="mailto:ipv6-wg-bounces@ripe.net">ipv6-wg-bounces@ripe.net</a> en nombre de <a href="mailto:raymond.jetten@elisa.fi">raymond.jetten@elisa.fi</a>> escribió:<span style='mso-fareast-language:ES-TRAD'><o:p></o:p></span></p></div></div><div><p class=MsoNormal style='margin-left:35.4pt'><o:p> </o:p></p></div><p class=MsoNormal style='margin-left:35.4pt'>Hello All,<o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>Thank you all for watching the IPv6 WG virtually, </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>at the latest minutes of Wilhelms presentation Q&A his dsl connection unfortunately went down,</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>there were still some questions in the buffer, could you Wilhelm comment yet on these ?</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>Any tips to get app developers on board to develop IPv6 enabled apps? It’s not uncommon for companies to exclude IPv6 from minimum viable product as its “too hard”</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>Could disabling SLAAC and better DHCPv6 support (eg in mobile devices) help the deployment? It would help with some migrations from IPv4 to IPv6 I think. (Mark Scholten / asking for myself)</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>Rgds,</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US>Ray</span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span lang=EN-US> </span><o:p></o:p></p><p class=MsoNormal style='margin-left:35.4pt'><span style='mso-fareast-language:ES-TRAD'><o:p> </o:p></span></p><p class=msipfooter3b88511e style='mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:35.4pt;margin-bottom:.0001pt'><span style='font-size:10.0pt;color:black'>For Internal Use Only</span><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>