[dhcwg] Re: [v6ops] Re: [IPv6]Re: Android now su pports DHCPv6 PD

--===============4555715667401052140==
Content-Type: multipart/alternative; boundary="00000000000054594d063ef46ef6"

--00000000000054594d063ef46ef6
Content-Type: text/plain; charset="UTF-8"

On Wed, 17 Sept 2025, 09:17 Mark Smith, <[email protected]> wrote:

> If but anyone had warned of this outcome before.
>>
>
> If you're worried about IPv6 address space running out, you might want to
> have a look at the original IPv6 proposal in RFC 8507, which proposed a 64
> bit address space.
>

There's no need to look at history here. We can just observe that all
cellular networks assign two or more /64s to every device by default, all
the time. That is the industry standard and was strongly argued for by the
IETF when mobile operators originally designed the standards to assign only
a single /128 per device.

Why RIPE would have a policy that allows cellular networks to provide
multiple /64s per device but doesn't allow, say, enterprise networks to do
the same seems somewhat arbitrary and unfair. After all, both of these are
IETF-standard deployment models.

>

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

<div dir=3D"auto"><br><br><div class=3D"gmail_quote gmail_quote_container" =
dir=3D"auto"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, 17 Sept 2025, 09=
:17 Mark Smith, &lt;<a href=3D"mailto:[email protected]">markzzzsmith@=
gmail.com</a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div dir=3D"auto"><div><div class=3D"gmail_quote"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">
If but anyone had warned of this outcome before.<br></blockquote></div></di=
v><div dir=3D"auto"><br></div><div>If you&#39;re worried about IPv6 address=
 space running out, you might want to have a look at the original IPv6 prop=
osal in RFC 8507, which proposed a 64 bit address space.</div></div></div><=
/blockquote></div><div dir=3D"auto"><br></div><div dir=3D"auto">There&#39;s=
 no need to look at history here. We can just observe that all cellular net=
works assign two or more /64s to every device by default, all the time. Tha=
t is the industry standard and was strongly argued for by the IETF when mob=
ile operators originally designed the standards to assign only a single /12=
8 per device.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Why RIPE w=
ould have a policy that allows cellular networks to provide multiple /64s p=
er device but doesn&#39;t allow, say, enterprise networks to do the same se=
ems somewhat arbitrary and unfair. After all, both of these are IETF-standa=
rd deployment models.</div><div class=3D"gmail_quote gmail_quote_container"=
 dir=3D"auto"></div><div class=3D"gmail_quote gmail_quote_container" dir=3D=
"auto"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">
</div>
</blockquote></div></div>

--00000000000054594d063ef46ef6--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============4555715667401052140==--