<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Ojo que si lo he entendido bien, lo que permite es asignar prefijos (PD), no direcciones individuales.<div><br></div><div>La idea va en el sentido de que cada vez hay mas dispositivos que pueden necesitar múltiples direcciones (ejemplo VMs).</div><div><br></div><div>Además, esto resuelve uno de los problemas de despliegue de banda ancha por medio de 4G/5G, que con los procedimientos actuales solo permite entregar /64 y no prefijos /48, que es lo que normalmente se debe asignar a un end-site, por mucho que este conectado por celular en lugar de fibra, cable, etc.</div><div><br></div><div>Con esto Android permite ser utilizado como SO en routers, que hasta ahora no era posible, por la limitación de no aceptar PD.</div><div><br></div><div>Aún así, el problema en el caso de celular es que muchos proveedores de infraestructura de 4G/5G, a pesar de ser parte de los estándares el uso de DHCPv6-PD, no lo implementan. Además, por lo visto incluso hay fabricantes de modems celulares (fabricantes de chips), que por defecto filtran los paquetes DHCPv6 - no tengo claro si es un filtrado “físico” o puede ser configurado por medio de firmware (actualización del firmware de radio o similar).<br><div><br id="lineBreakAtBeginningOfMessage"><div>
<div>Saludos,<br>Jordi<br><br>@jordipalet<br><br></div>
</div>
<div><br><blockquote type="cite"><div>El 16 sept 2025, a las 1:42, Carlos Martinez-Cagnazzo <carlosm3011@gmail.com> escribió:</div><br class="Apple-interchange-newline"><div><div dir="ltr">Tan solo 10-15 años de discusiones :-) Pero bienvenido sea, más vale tarde que nunca.</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Sep 15, 2025 at 8:36 PM Alejandro Acosta <<a href="mailto:alejandroacostaalamo@gmail.com">alejandroacostaalamo@gmail.com</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"><u></u>
<div><p>Interesante..., ¿alguien que se anime a probarlo y nos comente?.</p><p><br>
</p><p>Saludos,</p><p><br>
</p>
<div><br>
<br>
-------- Forwarded Message --------
<table cellpadding="0" cellspacing="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">Subject:
</th>
<td>[IPv6]Android now supports DHCPv6 PD</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">Date: </th>
<td>Tue, 16 Sep 2025 08:30:35 +0900</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">From: </th>
<td>Lorenzo Colitti
<a href="mailto:lorenzo=40google.com@dmarc.ietf.org" target="_blank"><lorenzo=40google.com@dmarc.ietf.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="">To: </th>
<td>6man <a href="mailto:6man@ietf.org" target="_blank"><6man@ietf.org></a>, <a href="mailto:v6ops@ietf.org" target="_blank">v6ops@ietf.org</a> WG
<a href="mailto:v6ops@ietf.org" target="_blank"><v6ops@ietf.org></a>, dhcwg <a href="mailto:dhcwg@ietf.org" target="_blank"><dhcwg@ietf.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div dir="ltr">FYI, we announced DHCPv6 PD support on Android
today:
<div><br>
</div>
<div><a href="https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html" target="_blank">https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html</a></div>
<div><br>
</div>
<div>This change should already be live on most Android devices
running Android 11 and above. Specifically:</div>
<div>
<ul>
<li>RFC 9762: if the P flag is set, the device will ask for
a SLAAC-sized prefix, and if it gets it, use it to form
addresses. Some devices will also disable SLAAC as per the
SHOULD in the RFC. Not all devices will support this
because it requires a kernel change which will be rolling
out over the coming months. In future releases, we expect
that the prefix will be shared with downstream devices,
wearable devices, VMs, etc.</li>
<li>Heuristic: if the device obtains a default route but not
PIO, it will ask for a prefix, and if it gets it, use it
to form addresses. This allows DHCPv6-only networks to
support Android devices today without having to upgrade
their routers to set the P flag.</li>
</ul>
<div>Over the next few months we also plan to roll out support
for DHCPv6 address registration (RFC 9686).</div>
<div><br>
</div>
<div>I would like to thank everyone who contributed to RFC
9663, RFC 9762 and RFC 9686. We think that DHCPv6 PD is
*better* than either SLAAC or IA_NA, because it allows the
device to provide end-to-end connectivity to unlimited
devices, containers, VMs etc. without scaling load on the
network. Plus the prefix can be tracked and managed by the
operator, which means that it should be possible to deploy
it in networks that require DHCPv6 or that have scaling
issues dealing with many addresses. We hope that this will
allow at least some enterprise operators to deploy IPv6 to
Android devices.</div>
<div><br>
</div>
</div>
<div>Cheers,</div>
<div>Lorenzo</div>
</div>
</div>
</div>
_______________________________________________<br>
LACNOG mailing list<br>
<a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a><br>
<a href="https://mail.lacnic.net/mailman/listinfo/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a><br>
Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a><br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">--<br>=========================<br>Carlos M. Martinez-Cagnazzo<br><a href="http://cagnazzo.name/" target="_blank">h</a>ttp://<a href="http://cagnazzo.me/" target="_blank">cagnazzo.me</a><br>=========================</div></div>
_______________________________________________<br>LACNOG mailing list<br>LACNOG@lacnic.net<br>https://mail.lacnic.net/mailman/listinfo/lacnog<br>Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog<br></div></blockquote></div><br></div></div></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>