[dhcwg] Re: [v6ops] Re: [IPv6]Re: Android now su pports DHCPv6 PD
Mark Smith <[email protected]> Wed, 17 Sep 2025 10:16:48 +1000
| Newsgroups | gmane.ietf.dhc,gmane.ietf.v6ops |
|---|---|
| Message-ID | <CAO42Z2wcDYLB3jR7A6b59mZ+_Pd29DUpXxpw7uF7XerUQEyN8w@mail.gmail.com> |
--===============5714187062915010513== Content-Type: multipart/alternative; boundary="000000000000a56160063ef428a6" --000000000000a56160063ef428a6 Content-Type: text/plain; charset="UTF-8" On Wed, 17 Sept 2025, 01:03 Gert Doering, <[email protected]> wrote: > Hi, > > On Tue, Sep 16, 2025 at 06:04:33PM +0900, Lorenzo Colitti wrote: > > Recommendations for network operators are written in RFC 9663. Some text > > about expected prefix lengths is in section 8 of that RFC. RFC 9762 says > > the prefix must be SLAAC-sized, which currently means it must be a /64 > per > > device. A /48 is fine for a small or medium network, but a campus with > tens > > of thousands of devices on it probably needs more than that. > > 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. IPv6 moving to 128 bits was not because 64 bits wasn't considered big enough. It was to originally to support the GSE proposal, https://datatracker.ietf.org/doc/html/draft-ietf-ipngwg-gseaddr-00 While GSE didn't eventuate, what did eventuate was another 64 bits on the end of addresses, which gave us a simple, one-size fits all default /64 subnet size, iinstead of the error prone, complex, variable and potential need to renumber "right-sized" subnets inherited from IPv4's CIDR - for those who have no choice to do it. Most people do /24s when they can - from within Class A and Bs originally, and then RFC 1918 when that public IPv4 address space became tight - because people used /24s. It has now given us the ability to give each host in networks where it would be useful a /64 each. A /64 per host in a /128 address space is the equivalent of assigning a single address per host in a 64 bit address space. It's more efficient than what would have happened with a 64 bit address space - there would have still been unused IPv6 64 bit addresses in the likely common /56 subnets (i.e. IPv4 /24 equivalents). A 64 bit address space is 4 billion times larger than IPv4's 32 bit address space. Has there been any other time in humanity where when something wasn't big enough the next biggest designed size was 4 billion times larger than the previous size? IPv4 was an experiment and proof of concept that escaped into production. IPv6 is really the first true Internet Protocol for the world wide Internet we have today and in the future. If you're interested in the evolution and history of IP addressing, starting from 1974, I did a presentation on it at NZNOG earlier this year: https://www.youtube.com/watch?v=Q-sPQ7p5n9c&t=11546s Regards, Mark. > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, > Karin Schuler, Sebastian Cler > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > > _______________________________________________ > dhcwg mailing list -- [email protected] > To unsubscribe send an email to [email protected] > --000000000000a56160063ef428a6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"auto"><div><br><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Wed, 17 Sept 2025, 01:03 Gert Doer= ing, <<a href=3D"mailto:[email protected]" rel=3D"noreferrer" target=3D"_bl= ank">[email protected]</a>> wrote:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex">Hi,<br> <br> On Tue, Sep 16, 2025 at 06:04:33PM +0900, Lorenzo Colitti wrote:<br> > Recommendations for network operators are written in RFC 9663. Some te= xt<br> > about expected prefix lengths is in section 8 of that RFC. RFC 9762 sa= ys<br> > the prefix must be SLAAC-sized, which currently means it must be a /64= per<br> > device. A /48 is fine for a small or medium network, but a campus with= tens<br> > of thousands of devices on it probably needs more than that.<br> <br> If but anyone had warned of this outcome before.<br></blockquote></div></di= v><div dir=3D"auto"><br></div><div>If you'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><br></di= v><div>IPv6 moving to 128 bits was not because 64 bits wasn't considere= d=C2=A0big enough. It was to originally to support the GSE proposal,=C2=A0<= /div><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://datat= racker.ietf.org/doc/html/draft-ietf-ipngwg-gseaddr-00">https://datatracker.= ietf.org/doc/html/draft-ietf-ipngwg-gseaddr-00</a><br><br>While GSE didn= 9;t eventuate, what did eventuate was another 64 bits on the end of address= es, which gave us a simple, one-size fits all default /64 subnet size, iins= tead of the error prone, complex, variable and potential need to renumber &= quot;right-sized" subnets inherited from IPv4's CIDR - for those w= ho have no choice to do it. Most people do /24s when they can - from within= Class A and Bs originally, and then RFC 1918 when that public IPv4 address= space became tight - because people used /24s.=C2=A0</div><div dir=3D"auto= "><br></div><div>It has now given us the ability to give each host in netwo= rks where it would be useful a /64 each.</div><div dir=3D"auto"><br></div><= div>A /64 per host in a /128 address space is the equivalent of assigning a= single address per host in a 64 bit address space. It's more efficient= than what would have happened with a 64 bit address space - there would ha= ve still been unused IPv6 64 bit addresses in the likely common /56 subnets= (i.e. IPv4 /24 equivalents).</div><div dir=3D"auto"><br></div><div>A 64 bi= t address space is 4 billion times larger than IPv4's 32 bit address sp= ace. Has there been any other time in humanity where when something wasn= 9;t big enough the next biggest designed size was 4 billion times larger th= an the previous size?</div><div><br></div><div>IPv4 was an experiment and p= roof of concept that escaped into production. IPv6 is really the first true= Internet Protocol for the world wide Internet we have today and in the fut= ure.</div><div><br></div><div>If you're interested in the evolution and= history of IP addressing, starting from 1974, I did a presentation on it a= t NZNOG earlier this year:</div><div><br></div><div><a href=3D"https://www.= youtube.com/watch?v=3DQ-sPQ7p5n9c&t=3D11546s">https://www.youtube.com/w= atch?v=3DQ-sPQ7p5n9c&t=3D11546s</a></div><div><br></div><div>Regards,</= div><div>Mark.</div><div><br></div><div><br></div><div dir=3D"auto"><br></d= iv><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_= quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,= 204);padding-left:1ex"> <br> Gert Doering<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 -- NetMaster<br> -- <br> have you enabled IPv6 on something today...?<br> <br> SpaceNet AG=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 Vorstand: Sebastian v. Bomhard,<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Karin Schuler, Sebastian Cler<br> Joseph-Dollinger-Bogen 14=C2=A0 =C2=A0 =C2=A0 =C2=A0 Aufsichtsratsvors.: A.= Grundner-Culemann<br> D-80807 Muenchen=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0HRB: 136055 (AG Muenchen)<br> Tel: +49 (0)89/32356-444=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0USt-IdNr.: DE8131= 85279<br> <br> _______________________________________________<br> dhcwg mailing list -- <a href=3D"mailto:[email protected]" rel=3D"noreferrer n= oreferrer" target=3D"_blank">[email protected]</a><br> To unsubscribe send an email to <a href=3D"mailto:[email protected]" rel= =3D"noreferrer noreferrer" target=3D"_blank">[email protected]</a><br> </blockquote></div></div></div> </div> --000000000000a56160063ef428a6-- --===============5714187062915010513== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK --===============5714187062915010513==--