[dhcwg] Android now supports DHCPv6 PD

--===============0655835926620299602==
Content-Type: multipart/alternative; boundary="0000000000009e04cb063edf64c8"

--0000000000009e04cb063edf64c8
Content-Type: text/plain; charset="UTF-8"

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

--0000000000009e04cb063edf64c8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">FYI, we announced DHCPv6 PD support on Android today:<div>=
<br></div><div><a href=3D"https://android-developers.googleblog.com/2025/09=
/simplifying-advanced-networking-with.html">https://android-developers.goog=
leblog.com/2025/09/simplifying-advanced-networking-with.html</a></div><div>=
<br></div><div>This change should already be live on most Android devices r=
unning Android 11 and above. Specifically:</div><div><ul><li>RFC 9762: if t=
he P flag is set, the device will ask for a SLAAC-sized prefix, and if it g=
ets it, use it to=C2=A0form 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 downstre=
am devices, wearable devices, VMs, etc.</li><li>Heuristic: if the device ob=
tains 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 suppo=
rt for DHCPv6 address registration (RFC 9686).</div><div><br></div><div>I w=
ould like to thank everyone who=C2=A0contributed to RFC 9663, RFC 9762 and=
=C2=A0RFC 9686. We think that DHCPv6 PD is *better* than=C2=A0either SLAAC =
or IA_NA, because it allows the device to provide end-to-end connectivity t=
o unlimited devices, containers, VMs etc. without scaling load on the netwo=
rk. 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 wi=
ll allow at least some enterprise operators to deploy IPv6 to Android devic=
es.</div><div><br></div></div><div>Cheers,</div><div>Lorenzo</div></div>

--0000000000009e04cb063edf64c8--


--===============0655835926620299602==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============0655835926620299602==--