[dhcwg] Re: [v6ops] Re: [IPv6]Re: Android now su pports DHCPv6 PD
Tim Chown <[email protected]> Wed, 17 Sep 2025 14:41:15 +0000
| Newsgroups | gmane.ietf.dhc,gmane.ietf.v6ops |
|---|---|
| Message-ID | <PAXPR07MB77735B7BB2A5B344B3A32789D617A@PAXPR07MB7773.eurprd07.prod.outlook.com> |
--===============9124530445756792975== Content-Language: en-GB Content-Type: multipart/alternative; boundary="_000_PAXPR07MB77735B7BB2A5B344B3A32789D617APAXPR07MB7773eurp_" --_000_PAXPR07MB77735B7BB2A5B344B3A32789D617APAXPR07MB7773eurp_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable On 17/09/2025, 01:36, "Lorenzo Colitti" <[email protected]> wrote: On Wed, 17 Sept 2025, 09:17 Mark Smith, <[email protected]<mailto:mark= [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 h= ave a look at the original IPv6 proposal in RFC 8507, which proposed a 64 b= it address space. There's no need to look at history here. We can just observe that all cellu= lar networks assign two or more /64s to every device by default, all the ti= me. That is the industry standard and was strongly argued for by the IETF w= hen mobile operators originally designed the standards to assign only a sin= gle /128 per device. Why RIPE would have a policy that allows cellular networks to provide multi= ple /64s per device but doesn't allow, say, enterprise networks to do the s= ame seems somewhat arbitrary and unfair. After all, both of these are IETF-= standard deployment models. Well, =93RIPE=94 is just a community of people, that could redefine/clarify= that policy to reflect modern reality. As an NREN advocating campuses deploy IPv6, we have to justify giving more = than a /48 to an organisation, and if DHCP-PD isn=92t acceptable then those= organisations will need to look at LIR status. That=92s not currently an = expensive proposition, in the grand scheme of university finances. An NREN= can route such LIR space alongside assignments from its own space, as we d= o. Tim --_000_PAXPR07MB77735B7BB2A5B344B3A32789D617APAXPR07MB7773eurp_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc= hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of= fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Aptos; panose-1:2 11 0 4 2 2 2 2 2 4;} @font-face {font-family:"Times New Roman \(Body CS\)"; panose-1:2 11 6 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:"Aptos",sans-serif; color:windowtext; font-weight:normal; font-style:normal;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style> </head> <body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea= k-word"> <div class=3D"WordSection1"> <div id=3D"mail-editor-reference-message-container"> <div> <div> <div> <p class=3D"MsoNormal">On 17/09/2025, 01:36, "Lorenzo Colitti" &l= t;[email protected]> wrote:<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p> </o:p></p> <div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">On Wed, 17 Sept 2025, 0= 9:17 Mark Smith, <<a href=3D"mailto:[email protected]">markzzzsmith= @gmail.com</a>> wrote:<o:p></o:p></p> </div> <blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c= m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <div> <div> <div> <div> <blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c= m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">If but anyone had warne= d of this outcome before.<o:p></o:p></p> </blockquote> </div> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">If you're worried about= IPv6 address space running out, you might want to have a look at the origi= nal IPv6 proposal in RFC 8507, which proposed a 64 bit address space.<o:p><= /o:p></p> </div> </div> </div> </blockquote> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">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 industr= y standard and was strongly argued for by the IETF when mobile operators originally designed the standards to ass= ign only a single /128 per device.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt"><o:p> </o:p></p> </div> <div> <p class=3D"MsoNormal" style=3D"margin-left:36.0pt">Why RIPE would have a p= olicy that allows cellular networks to provide multiple /64s per device but= doesn't allow, say, enterprise networks to do the same seems somewhat arbi= trary and unfair. After all, both of these are IETF-standard deployment models.<o:p></o:p></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Well, =93RIPE=94 is= just a community of people, that could redefine/clarify that policy to ref= lect modern reality.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">As an NREN advocati= ng campuses deploy IPv6, we have to justify giving more than a /48 to an or= ganisation, and if DHCP-PD isn=92t acceptable then those organisations will= need to look at LIR status. That=92s not currently an expensive proposition, in the grand scheme of university fina= nces. An NREN can route such LIR space alongside assignments from its= own space, as we do.<o:p></o:p></span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt"><o:p> </o:p></= span></p> <p class=3D"MsoNormal"><span style=3D"font-size:11.0pt">Tim<o:p></o:p></spa= n></p> </div> </div> </div> </div> </div> </div> </body> </html> --_000_PAXPR07MB77735B7BB2A5B344B3A32789D617APAXPR07MB7773eurp_-- --===============9124530445756792975== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK --===============9124530445756792975==--