[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>
On Fri, Jun 12, 2026 at 5:32 AM Tim Chown <[email protected]> wrote:

> Perhaps we need to start draft-v6ops-ipv6-dinosaurs and start to name and
> shame such organisations and what they’re doing wrong… 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 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.

-- 
Witarea mailing list -- [email protected]
To unsubscribe send an email to [email protected]