[Witarea] Re: [v6ops] Re: Re: How to make an elegant IPv4 outage
"Ted Lemon" <[email protected]> Fri, 12 Jun 2026 13:42:45 +0200
| Newsgroups | gmane.ietf.tsv-area,gmane.ietf.general,gmane.ietf.v6ops |
|---|---|
| Message-ID | <[email protected]> |
--===============6736241536647116978== Content-Type: multipart/alternative; boundary=f983c5e51084ff41be6f2e043d734182fb382b33 --f983c5e51084ff41be6f2e043d734182fb382b33 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sounds like dhcp needs a zone refresh timer.=20 On Fri, Jun 12, 2026, at 12:54 PM, Ole Tr=C3=B8an wrote: >=20 > Tim, > =EF=BB=BF >> Well, that=E2=80=99s 6man, this is v6ops. If bad operational procedu= res are followed, we should highlight those with pointers to the good. = Doesn=E2=80=99t have to name names I suppose. >=20 > You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD lifeti= mes was recommended to mirror the lifetime of the customer contract. But= then you got into issues with state maintenance on intermediate routers= , and ended up with short lifetimes, so RR has no visibility into the ac= tual lifetime of the prefix.=20 > Then providers raised the issue of rebalancing customers between eg CM= TSs, where 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 re= ality. >=20 > Ole >=20 >=20 >>=20 >>=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 nam= e and shame such organisations and what they=E2=80=99re doing wrong=E2=80= =A6 polite but objective critique and pointers in the doc to best practi= ce. >>=20 >> It may produce a better outcome if we instead focus on fixing the gap= s in ipv6. =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 = dynamic IPv4. I cannot get IPv6 for my service with static IPv4 addresse= s. >>>=20 >>> Seems to me that we are still a long way away from being able to shu= tter IPv4 completely. >>>=20 >>> What I have not yet tried but should is trying to use the IPv6 mappi= ng of my IPv4 addresses. >>> _______________________________________________ >>> v6ops mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] > _______________________________________________ > v6ops mailing list -- [email protected] > To unsubscribe send an email to [email protected] >=20 --f983c5e51084ff41be6f2e043d734182fb382b33 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title></head><body><div>Sounds like = dhcp needs a zone refresh timer. </div><div><br></div><div>On Fri, = Jun 12, 2026, at 12:54 PM, Ole Tr=C3=B8an wrote:</div><blockquote type=3D= "cite" id=3D"qt" style=3D""><div dir=3D"ltr"><br></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"direction:ltr;font-family:Aptos, Arial, Helve= tica, sans-serif;font-size:12pt;color:rgb(0, 0, 0);">Well, that=E2=80=99= s 6man, this is v6ops. If bad operational procedures are followed,= we should highlight those with pointers to the good. Doesn=E2=80=99= t have to name names I suppose.</div></div></blockquote><div><br></div><= div>You could. But it=E2=80=99s a world of inconsistency. DHCPv6 PD life= times was recommended to mirror the lifetime of the customer contract. B= ut then you got into issues with state maintenance on intermediate route= rs, and ended up with short lifetimes, so RR has no visibility into the = actual lifetime of the prefix. </div><div>Then providers raised the= issue of rebalancing customers between eg CMTSs, where maintaining the = same prefix has a cost.</div><div>And I am sure a desire for tiered prod= ucts. </div><div>A combination of ipv6 protocols, business practice= s and operational reality.</div><div><br></div><div>Ole</div><div><br></= div><div><br></div><blockquote type=3D"cite"><div dir=3D"ltr"><div style= =3D"direction:ltr;font-family:Aptos, Arial, Helvetica, sans-serif;font-s= ize:12pt;color:rgb(0, 0, 0);"><br></div><div id=3D"qt-mail-editor-refere= nce-message-container"><div class=3D"qt-ms-outlook-mobile-reference-mess= age qt-skipProofing" style=3D"direction:ltr;"><br></div><div class=3D"qt= -ms-outlook-mobile-reference-message qt-skipProofing">On 12/06/2026, 10:= 48, "Ole Tr=C3=B8an" <[email protected]> wrote:</div><div clas= s=3D"qt-ms-outlook-mobile-reference-message qt-skipProofing" style=3D"di= rection:ltr;"><br></div><div class=3D"qt-ms-outlook-mobile-reference-mes= sage qt-skipProofing" style=3D"direction:ltr;"><br></div><blockquote><di= v class=3D"qt-ms-outlook-mobile-reference-message qt-skipProofing" style= =3D"direction:ltr;font-family:Aptos, Arial, Helvetica, sans-serif;font-s= ize:12pt;color:rgb(0, 0, 0);">Perhaps we need to start draft-v6ops-ipv6-= dinosaurs and start to name and shame 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.</div></blockquote><div class=3D"qt-ms-outl= ook-mobile-reference-message qt-skipProofing" style=3D"direction:ltr;"><= br></div><div class=3D"qt-ms-outlook-mobile-reference-message qt-skipPro= ofing">It may produce a better outcome if we instead focus on fixing the= gaps in ipv6. </div><div class=3D"qt-ms-outlook-mobile-reference-= message qt-skipProofing" style=3D"direction:ltr;"><br></div><div class=3D= "qt-ms-outlook-mobile-reference-message qt-skipProofing">Ole</div><div c= lass=3D"qt-ms-outlook-mobile-reference-message qt-skipProofing" style=3D= "direction:ltr;"><br></div><div class=3D"qt-ms-outlook-mobile-reference-= message qt-skipProofing" style=3D"direction:ltr;"><br></div><div class=3D= "qt-ms-outlook-mobile-reference-message qt-skipProofing" style=3D"direct= ion:ltr;"><br></div><blockquote><div id=3D"qt-mail-editor-reference-mess= age-container"><div class=3D"qt-ms-outlook-mobile-reference-message qt-s= kipProofing">On 11/06/2026, 21:03, "Phillip Hallam-Baker" <phill@hall= ambaker.com> wrote:</div><div class=3D"qt-ms-outlook-mobile-reference= -message qt-skipProofing" style=3D"direction:ltr;"><br></div><div class=3D= "qt-gmail_default" style=3D"direction:ltr;font-size:9.75pt;">Just got of= f the phone with a very large ISP after a failed attempt to get an IPv6 = address.</div><div class=3D"qt-gmail_default" style=3D"direction:ltr;fon= t-size:9.75pt;"><br></div><div class=3D"qt-gmail_default" style=3D"direc= tion:ltr;font-size:9.75pt;">Turns out that I can have IPv6 but only dyna= mic and only if I am on dynamic IPv4. I cannot get IPv6 for my service w= ith static IPv4 addresses.</div><div class=3D"qt-gmail_default" style=3D= "direction:ltr;font-size:9.75pt;"><br></div><div class=3D"qt-gmail_defau= lt" style=3D"direction:ltr;font-size:9.75pt;">Seems to me that we are st= ill a long way away from being able to shutter IPv4 completely.</div><di= v class=3D"qt-gmail_default" style=3D"direction:ltr;font-size:9.75pt;"><= br></div><div class=3D"qt-gmail_default" style=3D"direction:ltr;font-siz= e:9.75pt;">What I have not yet tried but should is trying to use the IPv= 6 mapping of my IPv4 addresses.</div></div><div class=3D"qt-ms-outlook-m= obile-reference-message qt-skipProofing" style=3D"direction:ltr;"><div>_= ______________________________________________</div><div> v6ops mailing = list -- [email protected]</div><div> To unsubscribe send an email to v6ops-= [email protected]</div></div></blockquote></div></div></blockquote><div>___= ____________________________________________</div><div>v6ops mailing lis= t -- <a href=3D"mailto:[email protected]">[email protected]</a></div><div= >To unsubscribe send an email to <a href=3D"mailto:v6ops-leave@ietf= .org">[email protected]</a></div><div><br></div></blockquote><div><br= ></div></body></html> --f983c5e51084ff41be6f2e043d734182fb382b33-- --===============6736241536647116978== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg== --===============6736241536647116978==--