[Witarea] Re: [v6ops] Re: Re: How to make an elegant IPv4 outage
Phillip Hallam-Baker <[email protected]> Fri, 12 Jun 2026 17:49:51 -0400
| Newsgroups | gmane.ietf.tsv-area,gmane.ietf.general,gmane.ietf.v6ops |
|---|---|
| Message-ID | <CAMm+LwiW85tM_1OzMtRsxMpLZnP=B_kv8fh0KvgGQt6VZAbHxw@mail.gmail.com> |
--===============8873364768694098768== Content-Type: multipart/alternative; boundary="0000000000009fae120654157560" --0000000000009fae120654157560 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 12, 2026 at 5:32=E2=80=AFAM Tim Chown <[email protected]> wr= ote: > 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 po= lite but objective > critique and pointers in the doc to best practice. > > Tim > No, we need the exact opposite. We need branding people can recognize as meaning that an ISP is providing an Internet service that is fit for a particular purpose. So we do an RFC that sets out distinct levels of service with some indication of currency. INET-M-26: Mobile service, provides single dynamic IPv6 plus IPv4 which may be behind a wide-cone NAT. INET-R-26: Residential service, provides dynamic IPv6/64 plus an IPv4 connection that may be behind a wide-cone NAT INET-S-26: Standard hosting service, provides one or more static IPv4 addresses plus a static IPv6/64. INET-H-26: High availability hosting service, routes IPv4 and IPv6 traffic to an ASN held by the end customer. We can tweak names and service levels as people see fit. But the core should be that the end user gets everything they need to interoperate with the old Internet plus full access to the new. --0000000000009fae120654157560 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon= t-size:small">On Fri, Jun 12, 2026 at 5:32=E2=80=AFAM Tim Chown <<a href= =3D"mailto:[email protected]">[email protected]</a>> wrote:</div><= /div><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"= gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20= 4,204,204);padding-left:1ex"> <div> <div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo= nt-size:12pt;color:rgb(0,0,0)"> 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 polit= e but objective critique and pointers in the doc to best practice.</div> <div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo= nt-size:12pt;color:rgb(0,0,0)"> <br> </div> <div style=3D"direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;fo= nt-size:12pt;color:rgb(0,0,0)"> Tim<br></div></div></blockquote><div><br></div><div class=3D"gmail_default"= style=3D""><font size=3D"4">No, we need the exact opposite. We need brandi= ng people can recognize as meaning that an ISP is providing an Internet ser= vice that is fit for a particular purpose.</font></div><div class=3D"gmail_= default" style=3D""><font size=3D"4"><br></font></div><div class=3D"gmail_d= efault" style=3D""><font size=3D"4">So we do an RFC that sets out distinct = levels of service with some indication of currency.</font></div><div class= =3D"gmail_default" style=3D""><font size=3D"4"><br></font></div><div class= =3D"gmail_default" style=3D""><font size=3D"4">INET-M-26: Mobile service, p= rovides single dynamic IPv6 plus IPv4 which may be behind a wide-cone NAT.<= /font></div><div class=3D"gmail_default" style=3D""><font size=3D"4"><br></= font></div><div class=3D"gmail_default" style=3D""><font size=3D"4">INET-R-= 26: Residential service, provides dynamic IPv6/64 plus an IPv4 connection t= hat may be behind a wide-cone NAT=C2=A0</font></div><div class=3D"gmail_def= ault" style=3D""><font size=3D"4"><br></font></div><div class=3D"gmail_defa= ult" style=3D""><font size=3D"4">INET-S-26: Standard hosting service, provi= des one or more static IPv4 addresses plus a static IPv6/64.</font></div><d= iv class=3D"gmail_default" style=3D""><font size=3D"4"><br></font></div><di= v class=3D"gmail_default" style=3D""><span style=3D"font-size:large">INET-H= -26: High availability hosting service, routes IPv4 and IPv6 traffic to an = ASN held by the end customer.</span><font size=3D"4"></font></div><div clas= s=3D"gmail_default" style=3D""><font size=3D"4"><br></font></div><div class= =3D"gmail_default" style=3D""><font size=3D"4">We can tweak names and servi= ce levels as people see fit. But the core should be that the end user gets = everything they need to interoperate with the old Internet plus full access= to the new.</font></div></div></div> --0000000000009fae120654157560-- --===============8873364768694098768== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg== --===============8873364768694098768==--