<div dir="ltr">Hi Jordi,<div><br></div><div>Most of the testing requests that we have received for wired CPEs lately have been MAP based. We are aware of a couple ISPs considering XLAT464, but I'm not aware of it being used in production. </div><div><br></div><div>For wireless XLAT464 makes sense, even for fixed wireless.</div><div><br></div><div>~Tim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 24, 2021 at 12:31 PM JORDI PALET MARTINEZ via ipv6-wg <<a href="mailto:ipv6-wg@ripe.net">ipv6-wg@ripe.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="ES" style="overflow-wrap: break-word;"><div class="gmail-m_-4856629944495144346WordSection1"><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt">Hi Tim,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt">I understand that even if in the IETF we decide not to go for that, as we know that the participation in IETF from operators is not as good as we wish, we as a different community can have a totally different perspective.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt">If we don’t want to have full support of the RFC8585, at least we must mandate the 464XLAT section. The reason is clear: it is the only possible way in mobile, and if you want to support “hybrid CPEs” (those that provide for example a GPON WAN or Ethernet WAN + USB dongle for 3-5G) the easier way is to provide 464XLAT. It is also a matter of subscriber numbers in one technology vs all the others together.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><div><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt;color:black">Regards,<u></u><u></u></span></p><p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US" style="font-size:12pt;color:black">Jordi<u></u><u></u></span></p><p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US" style="font-size:12pt;color:black">@jordipalet<u></u><u></u></span></p><p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US" style="font-size:12pt;color:black"><u></u> <u></u></span></p></div><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><div><div><p class="MsoNormal" style="margin-left:35.4pt">El 24/11/21 18:26, "ipv6-wg en nombre de Timothy Winters" <<a href="mailto:ipv6-wg-bounces@ripe.net" target="_blank">ipv6-wg-bounces@ripe.net</a> en nombre de <a href="mailto:tim@qacafe.com" target="_blank">tim@qacafe.com</a>> escribió:<u></u><u></u></p></div></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">Hi Jordi,<u></u><u></u></p><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">I see you also brought up on the v6ops list. Let's see what the operator community has to say about this topic.<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">I'm not opposed to changing this, but I'm also aware that's CPEs rarely support all the mechanisms listed in that RFC.<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">~Tim<u></u><u></u></p></div></div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p><div><div><p class="MsoNormal" style="margin-left:35.4pt">On Wed, Nov 24, 2021 at 11:58 AM JORDI PALET MARTINEZ via ipv6-wg <<a href="mailto:ipv6-wg@ripe.net" target="_blank">ipv6-wg@ripe.net</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal" style="margin-left:35.4pt">Hi Tim, all,<br><br>I've reviewed the latest version of the document and in general I agree. However, today is unacceptable that a CPE doesn't support IPv6-only + IPv4aaS, so RFC8585 must be a must in this type of document.<br><br>I think there must be a clear statement on that.<br><br>Regards,<br>Jordi<br>@jordipalet<br><br><br><br><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br><a href="http://www.theipv6company.com" target="_blank">http://www.theipv6company.com</a><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><br><br><br>To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://lists.ripe.net/mailman/listinfo/ipv6-wg" target="_blank">https://lists.ripe.net/mailman/listinfo/ipv6-wg</a><u></u><u></u></p></blockquote></div><p class="MsoNormal" style="margin-left:35.4pt">To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://lists.ripe.net/mailman/listinfo/ipv6-wg" target="_blank">https://lists.ripe.net/mailman/listinfo/ipv6-wg</a> <u></u><u></u></p></div><br>**********************************************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com" target="_blank">http://www.theipv6company.com</a><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>
</div>
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://lists.ripe.net/mailman/listinfo/ipv6-wg" rel="noreferrer" target="_blank">https://lists.ripe.net/mailman/listinfo/ipv6-wg</a><br>
</blockquote></div>