<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Interesante..., ¿alguien que se anime a probarlo y nos comente?.</p>
<p><br>
</p>
<p>Saludos,</p>
<p><br>
</p>
<div class="moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table cellpadding="0" cellspacing="0" border="0"
class="moz-email-headers-table">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject:
</th>
<td>[IPv6]Android now supports DHCPv6 PD</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Tue, 16 Sep 2025 08:30:35 +0900</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Lorenzo Colitti
<a class="moz-txt-link-rfc2396E" href="mailto:lorenzo=40google.com@dmarc.ietf.org"><lorenzo=40google.com@dmarc.ietf.org></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td>6man <a class="moz-txt-link-rfc2396E" href="mailto:6man@ietf.org"><6man@ietf.org></a>, <a class="moz-txt-link-abbreviated" href="mailto:v6ops@ietf.org">v6ops@ietf.org</a> WG
<a class="moz-txt-link-rfc2396E" href="mailto:v6ops@ietf.org"><v6ops@ietf.org></a>, dhcwg <a class="moz-txt-link-rfc2396E" href="mailto:dhcwg@ietf.org"><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"
moz-do-not-send="true" class="moz-txt-link-freetext">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>
</body>
</html>