[lacnog] [IPv6]Android now supports DHCPv6 PD

Mar Sep 16 09:19:46 -03 2025

Hola Jordi!

On 16/9/25 9:07 AM, jordi.palet--- vía LACNOG wrote:
> Ojo que si lo he entendido bien, lo que permite es asignar prefijos 
> (PD), no direcciones individuales.

Si, entiendo. Pero de ahi a poder configurar el propio móvil debería ser 
bastante sencillo.

Es un gran paso en la dirección correcta.

>
> La idea va en el sentido de que cada vez hay mas dispositivos que 
> pueden necesitar múltiples direcciones (ejemplo VMs).
Si, es un caso de uso cada vez más común.
>
> 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.
>
> Con esto Android permite ser utilizado como SO en routers, que hasta 
> ahora no era posible, por la limitación de no aceptar PD.
De acuerdo.
>
> 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).
Ahi ya no es culpa del pobre Androide :-)
>
> Saludos,
> Jordi
>
> @jordipalet
>
>
>> El 16 sept 2025, a las 1:42, Carlos Martinez-Cagnazzo 
>> <carlosm3011 en gmail.com> escribió:
>>
>> Tan solo 10-15 años de discusiones :-) Pero bienvenido sea, más vale 
>> tarde que nunca.
>>
>> On Mon, Sep 15, 2025 at 8:36 PM Alejandro Acosta 
>> <alejandroacostaalamo en gmail.com> wrote:
>>
>>     Interesante..., ¿alguien que se anime a probarlo y nos comente?.
>>
>>
>>     Saludos,
>>
>>
>>
>>
>>     -------- Forwarded Message --------
>>     Subject: 	[IPv6]Android now supports DHCPv6 PD
>>     Date: 	Tue, 16 Sep 2025 08:30:35 +0900
>>     From: 	Lorenzo Colitti <lorenzo=40google.com en dmarc.ietf.org>
>>     <mailto:lorenzo=40google.com en dmarc.ietf.org>
>>     To: 	6man <6man en ietf.org> <mailto:6man en ietf.org>, v6ops en ietf.org
>>     WG <v6ops en ietf.org> <mailto:v6ops en ietf.org>, dhcwg
>>     <dhcwg en ietf.org> <mailto:dhcwg en ietf.org>
>>
>>
>>
>>     FYI, we announced DHCPv6 PD support on Android today:
>>
>>     https://android-developers.googleblog.com/2025/09/simplifying-advanced-networking-with.html
>>
>>     This change should already be live on most Android devices
>>     running Android 11 and above. Specifically:
>>
>>       * 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.
>>       * 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.
>>
>>     Over the next few months we also plan to roll out support for
>>     DHCPv6 address registration (RFC 9686).
>>
>>     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.
>>
>>     Cheers,
>>     Lorenzo
>>     _______________________________________________
>>     LACNOG mailing list
>>     LACNOG en lacnic.net
>>     https://mail.lacnic.net/mailman/listinfo/lacnog
>>     Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>>
>>
>>
>> -- 
>> --
>> =========================
>> Carlos M. Martinez-Cagnazzo
>> h <http://cagnazzo.name/>ttp://cagnazzo.me <http://cagnazzo.me/>
>> =========================
>> _______________________________________________
>> LACNOG mailing list
>> LACNOG en lacnic.net
>> https://mail.lacnic.net/mailman/listinfo/lacnog
>> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> 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.
>
>
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion:https://mail.lacnic.net/mailman/options/lacnog
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20250916/c4caa0aa/attachment.htm>