[dhcwg] Re: [v6ops] Android now supports DHCPv6 PD

--===============0541845186074767261==
Content-Type: multipart/alternative; boundary="000000000000ba02c5063ee17250"

--000000000000ba02c5063ee17250
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Congrats!

On Mon, Sep 15, 2025 at 6:32=E2=80=AFPM Lorenzo Colitti <lorenzo=3D
[email protected]> wrote:

> FYI, we announced DHCPv6 PD support on Android today:
>
>
> https://android-developers.googleblog.com/2025/09/simplifying-advanced-ne=
tworking-with.html
>
> This change should already be live on most Android devices running Androi=
d
> 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 wi=
ll 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. Th=
is
>    allows DHCPv6-only networks to support Android devices today without h=
aving
>    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, whic=
h
> 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
> _______________________________________________
> v6ops mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

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

<div dir=3D"auto">Congrats!</div><div><br><div class=3D"gmail_quote gmail_q=
uote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Sep 15, 2025 =
at 6:32=E2=80=AFPM Lorenzo Colitti &lt;lorenzo=3D<a href=3D"mailto:40google=
[email protected]">[email protected]</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb=
(204,204,204)"><div dir=3D"ltr">FYI, we announced DHCPv6 PD support on Andr=
oid today:<div><br></div><div><a href=3D"https://android-developers.googleb=
log.com/2025/09/simplifying-advanced-networking-with.html" target=3D"_blank=
">https://android-developers.googleblog.com/2025/09/simplifying-advanced-ne=
tworking-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=C2=A0form addresses. Som=
e devices will also disable SLAAC as per the SHOULD in the RFC. Not all dev=
ices will support this because it requires a kernel change which will be ro=
lling out over the coming months. In future releases, we expect that the pr=
efix will be shared with downstream devices, wearable devices, VMs, etc.</l=
i><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 up=
grade their routers to set the P flag.</li></ul><div>Over the next few mont=
hs we also plan to roll out support for DHCPv6 address registration (RFC 96=
86).</div><div><br></div><div>I would like to thank everyone who=C2=A0contr=
ibuted 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 p=
rovide end-to-end connectivity to unlimited devices, containers, VMs etc. w=
ithout scaling load on the network. Plus the prefix can be tracked and mana=
ged 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>
_______________________________________________<br>
v6ops mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank">v=
[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" tar=
get=3D"_blank">[email protected]</a><br>
</blockquote></div></div>

--000000000000ba02c5063ee17250--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============0541845186074767261==--