[dhcwg] Re: [IPv6]Re: [v6ops] Android now supports DHCPv6 PD
Lorenzo Colitti <[email protected]> Tue, 16 Sep 2025 17:46:05 +0900
| Newsgroups | gmane.ietf.dhc,gmane.ietf.v6ops |
|---|---|
| Message-ID | <CAKD1Yr32GdvEhh7kKCuPT3RGoKo0ojo-W6Kiy-euD1aP9RjpLg@mail.gmail.com> |
--===============9081131031593519139== Content-Type: multipart/alternative; boundary="0000000000003ab4a3063ee7279a" --0000000000003ab4a3063ee7279a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable There was a typo in the original post. It was fixed earlier today; it now says "Android 11 and above" On Tue, Sep 16, 2025 at 3:21=E2=80=AFPM Maciej =C5=BBenczykowski <maze=3D [email protected]> wrote: > There's a reddit thread: > > > https://www.reddit.com/r/Android/comments/1nhzsst/android_developers_blog= _simplifying_advanced/ > > First comment: > > There's a mistake in the page: running Android and above before the > end of the year via a Google Play System Update. > > Which version? > > > On Tue, Sep 16, 2025 at 3:59=E2=80=AFAM Stan Barber <[email protected]> wrot= e: > > > > 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 > 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 al= so > 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 t= he > coming months. In future releases, we expect that the prefix will be shar= ed > 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 allow= s > 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, 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] > > > > -------------------------------------------------------------------- > > IETF IPv6 working group mailing list > > [email protected] > > List Info: https://mailman3.ietf.org/mailman3/lists/[email protected]/ > > -------------------------------------------------------------------- > > -- > Maciej =C5=BBenczykowski, Kernel Networking Developer @ Google > --0000000000003ab4a3063ee7279a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">There was a typo in the original post. It was fixed earlie= r today; it now says "Android 11 and above"</div><br><div class= =3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr= ">On Tue, Sep 16, 2025 at 3:21=E2=80=AFPM Maciej =C5=BBenczykowski <maze= =3D<a href=3D"mailto:[email protected]">[email protected]= rg</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi= n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex= ">There's a reddit thread:<br> <br> <a href=3D"https://www.reddit.com/r/Android/comments/1nhzsst/android_develo= pers_blog_simplifying_advanced/" rel=3D"noreferrer" target=3D"_blank">https= ://www.reddit.com/r/Android/comments/1nhzsst/android_developers_blog_simpli= fying_advanced/</a><br> <br> First comment:<br> <br> There's a mistake in the page: running Android and above before the<br> end of the year via a Google Play System Update.<br> <br> Which version?<br> <br> <br> On Tue, Sep 16, 2025 at 3:59=E2=80=AFAM Stan Barber <<a href=3D"mailto:s= [email protected]" target=3D"_blank">[email protected]</a>> wrote:<br> ><br> > Congrats!<br> ><br> > On Mon, Sep 15, 2025 at 6:32=E2=80=AFPM Lorenzo Colitti <lorenzo=3D= <a href=3D"mailto:[email protected]" target=3D"_blank">40google.c= [email protected]</a>> wrote:<br> >><br> >> FYI, we announced DHCPv6 PD support on Android today:<br> >><br> >> <a href=3D"https://android-developers.googleblog.com/2025/09/simpl= ifying-advanced-networking-with.html" rel=3D"noreferrer" target=3D"_blank">= https://android-developers.googleblog.com/2025/09/simplifying-advanced-netw= orking-with.html</a><br> >><br> >> This change should already be live on most Android devices running= Android 11 and above. Specifically:<br> >><br> >> RFC 9762: if the P flag is set, the device will ask for a SLAAC-si= zed 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 suppo= rt 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 sh= ared with downstream devices, wearable devices, VMs, etc.<br> >> Heuristic: if the device obtains a default route but not PIO, it w= ill ask for a prefix, and if it gets it, use it to form addresses. This all= ows DHCPv6-only networks to support Android devices today without having to= upgrade their routers to set the P flag.<br> >><br> >> Over the next few months we also plan to roll out support for DHCP= v6 address registration (RFC 9686).<br> >><br> >> I would like to thank everyone who contributed to RFC 9663, RFC 97= 62 and RFC 9686. We think that DHCPv6 PD is *better* than either SLAAC or I= A_NA, because it allows the device to provide end-to-end connectivity to un= limited devices, containers, VMs etc. without scaling load on the network. = Plus the prefix can be tracked and managed by the operator, which means tha= t it should be possible to deploy it in networks that require DHCPv6 or tha= t have scaling issues dealing with many addresses. We hope that this will a= llow at least some enterprise operators to deploy IPv6 to Android devices.<= br> >><br> >> Cheers,<br> >> Lorenzo<br> >> _______________________________________________<br> >> v6ops mailing list -- <a href=3D"mailto:[email protected]" target=3D"= _blank">[email protected]</a><br> >> To unsubscribe send an email to <a href=3D"mailto:v6ops-leave@ietf= .org" target=3D"_blank">[email protected]</a><br> ><br> > --------------------------------------------------------------------<b= r> > IETF IPv6 working group mailing list<br> > <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><b= r> > List Info: <a href=3D"https://mailman3.ietf.org/mailman3/lists/ipv6@ie= tf.org/" rel=3D"noreferrer" target=3D"_blank">https://mailman3.ietf.org/mai= lman3/lists/[email protected]/</a><br> > --------------------------------------------------------------------<b= r> <br> --<br> Maciej =C5=BBenczykowski, Kernel Networking Developer @ Google<br> </blockquote></div> --0000000000003ab4a3063ee7279a-- --===============9081131031593519139== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK --===============9081131031593519139==--