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

S Moonesamy <sm+ietf@elandsys.com> Sat, 13 June 2026 01:52 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: witarea@mail2.ietf.org
Delivered-To: witarea@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 33AA11008DD65; Fri, 12 Jun 2026 18:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1781315576; bh=aIBnHbHeiajs4OCy1J3jpfJlav/hJ10E6mM4RJ93LKk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=StnO4b/BRmx+lS68or8BkhRhDL4WFdaYrVxtO/3w+bcG02H8QtBM9j0aqr3312xw3 I8tAE5ADRWo+rsgz+GfZ1Kw3sN2Fs9/iCA72a5IwKPMmg0Rppmmxbm/XSq3dc1zzZA VCmRvrhAIGiTps+3wC4TvrD8/n1BbBxXHZies4Xw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LS2MVmDv9GIv; Fri, 12 Jun 2026 18:52:54 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mail2.ietf.org (Postfix) with ESMTP id 4F62D1008CC32; Fri, 12 Jun 2026 18:51:35 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.117.159.127]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 65D1ojxQ004015 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jun 2026 18:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elandsys.com; s=mail; t=1781315466; x=1781401866; i=@elandsys.com; bh=aIBnHbHeiajs4OCy1J3jpfJlav/hJ10E6mM4RJ93LKk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0p442LQky3lcAzw89TgCR0zsXYB6D912Df1kcnCkhKnL8ypEa26OsXCFtY3t61nS7 Rf4dcaqcKqMQgqR3CxpStDK2GUu/db2yj3oWl3AKTiKAKYFLMHdY1PuNVtDow/oyGZ LHMlavX6T3Z4pK5eKei6+LFT7c47jPxwYtF4A/cY=
Message-Id: <6.2.5.6.2.20260612175136.10f64da0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 12 Jun 2026 18:45:59 -0700
To: Phillip Hallam-Baker <phill@hallambaker.com>, Tim Chown <Tim.Chown@jisc.ac.uk>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <CAMm+LwiW85tM_1OzMtRsxMpLZnP=B_kv8fh0KvgGQt6VZAbHxw@mail.g mail.com>
References: <456388925.296572478.1780511571678.JavaMail.zimbra@zmcc-3-mailbox-1.zmailcloud.com> <109008554.300485918.1780530680809.JavaMail.zimbra@zmcc-3-mailbox-1.zmailcloud.com> <d6b326b3615c41bd971fe98c4362a7d5@huawei.com> <CACMsEX9pHnVgG3dp2CyYmeYHPGNQWySoxOaOFiotQzT+oJMfBg@mail.gmail.com> <1019057082.341169112.1780857528310.JavaMail.zimbra@peachymango.org> <CACMsEX-SYkbZJ-Vy8NyROFRo=e=u-v-PUf5OTJejT=_NwBDHjw@mail.gmail.com> <1017721185.1093683.1781050032923.JavaMail.zimbra@peachymango.org> <9667FF77-69FE-4B19-8289-C968E89EB37B@in-panik.de> <1956566503.19748422.1781200506163.JavaMail.zimbra@peachymango.org> <CAMm+LwiAZ==Wqt208ZDoh7vQtfrciYEBe8KkWM+JSKumZ3pK+Q@mail.gmail.com> <DB9PR07MB7771083D3FE8E2D189F479E6D6182@DB9PR07MB7771.eurprd07.prod.outlook.com> <CAMm+LwiW85tM_1OzMtRsxMpLZnP=B_kv8fh0KvgGQt6VZAbHxw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: IPBOIVODZ6I36AA3H5LD7A2TX7EITCDD
X-Message-ID-Hash: IPBOIVODZ6I36AA3H5LD7A2TX7EITCDD
X-MailFrom: sm@elandsys.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Franck Martin <franck@peachymango.org>, Philipp Tiesel <phils@in-panik.de>, Xipengxiao <xipengxiao=40huawei.com@dmarc.ietf.org>, witarea@ietf.org, v6ops@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Witarea] Re: [v6ops] Re: Re: How to make an elegant IPv4 outage
List-Id: "Web and Internet Transport (WIT) Area" <witarea.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/witarea/qIgfzjc08ihiVl85AMATNnD8Bjk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/witarea>
List-Help: <mailto:witarea-request@ietf.org?subject=help>
List-Owner: <mailto:witarea-owner@ietf.org>
List-Post: <mailto:witarea@ietf.org>
List-Subscribe: <mailto:witarea-join@ietf.org>
List-Unsubscribe: <mailto:witarea-leave@ietf.org>

Hi Phillip, Tim,
At 02:49 PM 12-06-2026, Phillip Hallam-Baker wrote:
>On Fri, Jun 12, 2026 at 5:32 AM Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>Perhaps we need to start 
>draft-v6ops-ipv6-dinosaurs and start to name and 
>shame such organisations and what they're doing 
>wrong… politte 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.

The was a discussion on the deepspace mailing 
list about whether the policies for IPv6 was 
better suited for communities external to the 
IETF.  The "level of service" discussion would 
also be suited for those communities if they are 
drawing up the policies.  As for what 
organizations are doing wrong, I would have to 
look into their constraints to be able to say anything about that.

The requirement for interoperability may be 
relevant to this community.  I am not sure 
whether there is such a requirement 
externally.  My guess is that non-technical 
people expect things which were working yesterday 
should work today.  A person generally does not 
have to bother with the addressing aspect as 
there is a device which handles that automatically.

Regards,
S. Moonesamy