[Witarea] Re: [v6ops] Re: Re: How to make an elegant IPv4 outage

--===============5399881198025456085==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha512; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Phillip Hallam-Baker <[email protected]> wrote:
    > On Fri, Jun 12, 2026 at 5:32=E2=80=AFAM Tim Chown <[email protected].=
uk> wrote:

    >> 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.
    >>
    >> 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 f=
or
    > a particular purpose.

Yes, it needs to be branding/marketing, and it's not something that IETF do=
es
well, or for which an RFC is particularly useful.

    > So we do an RFC that sets out distinct levels of service with some
    > indication of currency.

I would try to get a conclave of RIRs to do BCOPs on this, perhaps
coordinated via ICANN.  (But, really, ICANN itself should not be involved).
Maybe CableLabs / Broadband Forum are better venues.

    > INET-M-26: Mobile service, provides single dynamic IPv6 plus IPv4 whi=
ch
    > may be behind a wide-cone NAT.

    > INET-R-26: Residential service, provides dynamic IPv6/56 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/56.

Please note that there are two axes here:
1) if your v6 prefix is random/changeable vs deterministic.
2) if your v6 prefix is delivered by DHCPv6 or manually configured.

This is a detail, but it does affect ability to pick up and move ISP, while
retaining the same router.
"Standard hosting service" is the wrong term, and will be confusing to ISP
marketing types.   Because it's not about public facing web sites, even if
it probably involves port 443.

It should be "Small Business with remote security needs" ("hairdresser")

    > INET-H-26: High availability hosting service, routes IPv4 and IPv6
    > traffic to an ASN held by the end customer.

ISPs that can provide this already know what this is, it need only be defin=
ed
so that an ISP can say to the customer, who should be asking for "INET-S-26=
",
if that's really what they wanted.

Having said this, I've dealt with many L1/L2 providers who do not listen to
me when I explain, slowly, and clearly, that I've asked for L3 services,
and that's okay if they don't have that.  I've also regularly had annoying
attempts to upsell me to L3, when I really really wanted L2.

=2D-
Michael Richardson <[email protected]>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-                      *I*LIKE*TRAINS*




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEERK+9HEcJHTJ9UqTMlUzhVv38QpAFAmoxfZQACgkQlUzhVv38
QpDkbQf+LBNz0QWVshmVXQ+W0qWdUV6oWsuisDyi1QMPCPRkqCSbrZu8Kdf4d8Y9
RUKyco8nlXG2DkjQnIA4KQaGbb+cGLzffX/bbGWPIHwbEXJGv4+8eAMvlo74cJDC
lP1HnFi50fiYi3pCEKwPC6ARZrx0Z2gDvs/GNZI4sruIy00XUIrjJq3c/sSbOsmS
alZ2ifSuuC8xiiTJFnTPz88HSaRPQXlH+5vDhmiHSghlNk2GRL7x3zYLJdctG17U
kNSsu/ataso5MJmqtSA2UOtSvGLUtbRC2aR0vYjtIKpNQT1YGA7BmdXj8ro6672m
wS9sYW6cZwi0H+8fmgJAnBhIkXqrmg==
=yCDZ
-----END PGP SIGNATURE-----
--=-=-=--


--===============5399881198025456085==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCldpdGFyZWEgbWFpbGluZyBsaXN0IC0tIHdpdGFyZWFAaWV0Zi5vcmcKVG8gdW5zdWJzY3Jp
YmUgc2VuZCBhbiBlbWFpbCB0byB3aXRhcmVhLWxlYXZlQGlldGYub3JnCg==

--===============5399881198025456085==--