[Witarea] Re: [v6ops] Re: Re: How to make an elegant IPv4 outage
Ole Trøan <[email protected]> Fri, 12 Jun 2026 12:54:16 +0200
| Newsgroups | gmane.ietf.tsv-area,gmane.ietf.general,gmane.ietf.v6ops |
|---|---|
| Message-ID | <[email protected]> |
--===============7339607852774489678== Content-Type: multipart/alternative; boundary=Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Transfer-Encoding: 7bit --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Tim, =EF=BB=BF > Well, that=E2=80=99s 6man, this is v6ops. If bad operational procedures a= re followed, we should highlight those with pointers to the good. Doesn=E2=80= =99t have to name names I suppose. You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD lifetimes wa= s recommended to mirror the lifetime of the customer contract. But then you g= ot into issues with state maintenance on intermediate routers, and ended up w= ith short lifetimes, so RR has no visibility into the actual lifetime of the= prefix.=20 Then providers raised the issue of rebalancing customers between eg CMTSs, w= here maintaining the same prefix has a cost. And I am sure a desire for tiered products.=20 A combination of ipv6 protocols, business practices and operational reality.= Ole >=20 > On 12/06/2026, 10:48, "Ole Tr=C3=B8an" <[email protected]> wrote: >=20 >=20 > Perhaps we need to start draft-v6ops-ipv6-dinosaurs and start to name and s= hame such organisations and what they=E2=80=99re doing wrong=E2=80=A6 polite= but objective critique and pointers in the doc to best practice. >=20 > It may produce a better outcome if we instead focus on fixing the gaps in i= pv6. =20 >=20 > Ole >=20 >=20 >=20 > On 11/06/2026, 21:03, "Phillip Hallam-Baker" <[email protected]> wrote= : >=20 > Just got off the phone with a very large ISP after a failed attempt to get= an IPv6 address. >=20 > Turns out that I can have IPv6 but only dynamic and only if I am on dynami= c IPv4. I cannot get IPv6 for my service with static IPv4 addresses. >=20 > Seems to me that we are still a long way away from being able to shutter I= Pv4 completely. >=20 > What I have not yet tried but should is trying to use the IPv6 mapping of m= y IPv4 addresses. > _______________________________________________ > v6ops mailing list -- [email protected] > To unsubscribe send an email to [email protected] --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi= v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D= "auto"><div dir=3D"ltr"></div><div dir=3D"ltr">Tim,</div><div dir=3D"ltr">=EF= =BB=BF</div><blockquote type=3D"cite"><div dir=3D"ltr"><div style=3D"directi= on: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; c= olor: rgb(0, 0, 0);"> Well, that=E2=80=99s 6man, this is v6ops. If bad operational procedure= s are followed, we should highlight those with pointers to the good. D= oesn=E2=80=99t have to name names I suppose.</div></div></blockquote><div><b= r></div><div>You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD= lifetimes was recommended to mirror the lifetime of the customer contract. B= ut then you got into issues with state maintenance on intermediate routers, a= nd ended up with short lifetimes, so RR has no visibility into the actual li= fetime of the prefix. </div><div>Then providers raised the issue of reb= alancing customers between eg CMTSs, where maintaining the same prefix has a= cost.</div><div>And I am sure a desire for tiered products. </div><div= >A combination of ipv6 protocols, business practices and operational reality= .</div><div><br></div><div>Ole</div><div><br></div><br><blockquote type=3D"c= ite"><div dir=3D"ltr"> <div style=3D"direction: ltr; font-family: Aptos, Arial, Helvetica, sans-ser= if; font-size: 12pt; color: rgb(0, 0, 0);"> <br> </div> <div id=3D"mail-editor-reference-message-container"> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing">On 12/06/202= 6, 10:48, "Ole Tr=C3=B8an" <[email protected]> wrote:</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <blockquote> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12= pt; color: rgb(0, 0, 0);"> Perhaps we need to start draft-v6ops-ipv6-dinosaurs and start to name and sh= ame such organisations and what they=E2=80=99re doing wrong=E2=80=A6 polite b= ut objective critique and pointers in the doc to best practice.</div> </blockquote> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing">It may produ= ce a better outcome if we instead focus on fixing the gaps in ipv6. </= div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing">Ole</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <blockquote> <div id=3D"mail-editor-reference-message-container"> <div class=3D"ms-outlook-mobile-reference-message skipProofing">On 11/06/202= 6, 21:03, "Phillip Hallam-Baker" <[email protected]> wrote:</div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> <br> </div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;">Ju= st got off the phone with a very large ISP after a failed attempt to get an I= Pv6 address.</div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;"><b= r> </div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;">Tu= rns out that I can have IPv6 but only dynamic and only if I am on dynamic IP= v4. I cannot get IPv6 for my service with static IPv4 addresses.</div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;"><b= r> </div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;">Se= ems to me that we are still a long way away from being able to shutter IPv4 c= ompletely.</div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;"><b= r> </div> <div class=3D"gmail_default" style=3D"direction: ltr; font-size: 9.75pt;">Wh= at I have not yet tried but should is trying to use the IPv6 mapping of my I= Pv4 addresses.</div> </div> <div class=3D"ms-outlook-mobile-reference-message skipProofing" style=3D"dir= ection: ltr;"> _______________________________________________<br> v6ops mailing list -- [email protected]<br> To unsubscribe send an email to [email protected]</div> </blockquote> </div> </div></blockquote></body></html>= --Apple-Mail-83CDE0C6-80B6-4879-9A66-073D051BCA3C-- --===============7339607852774489678== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg== --===============7339607852774489678==--