Return-Path: X-Original-To: ietf@mail2.ietf.org Delivered-To: ietf@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6284DFA3E450 for ; Wed, 3 Jun 2026 11:33:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780511581; bh=cYlyIz/Ym26UrE6Xx6OOlnDOzAEXxClVwxaJwRqofqw=; h=From:Subject:Date:To; b=bWBPWppKvMDJ4/c33YDX+pA0yOumdlTowcbWKni5ThXvw6Ll8BKXgadCrlB+/MJIL hsqCnZTGWxDKjqGGctvVKt2dVIo3qzKTMF2ugJAbhxajNHHXRd0yPyOiYRR3eQYlRo pnquOPF3xpQ5UztkAGCOCmczNYTUfmMvyt17Y//o= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.796 X-Spam-Level: X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=peachymango.org 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 S4R_reNm-xze for ; Wed, 3 Jun 2026 11:33:00 -0700 (PDT) Received: from zmcc-4-mx.zmailcloud.com (zmcc-4-mx.zmailcloud.com [34.203.170.87]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4E4BFFA3E445 for ; Wed, 3 Jun 2026 11:33:00 -0700 (PDT) Received: from zmcc-3.zmailcloud.com (ec2-3-15-255-223.us-east-2.compute.amazonaws.com [3.15.255.223]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by zmcc-4-mx.zmailcloud.com (Postfix) with ESMTPS id 4C94B7801DBE for ; Wed, 3 Jun 2026 13:32:52 -0500 (CDT) Received: from zmcc-3.zmailcloud.com (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTPS id 292F6A00E1A4 for ; Wed, 3 Jun 2026 13:32:52 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTP id 10F4AA00E1A5 for ; Wed, 3 Jun 2026 13:32:52 -0500 (CDT) DKIM-Filter: OpenDKIM Filter v2.10.3 zmcc-3-mta-1.zmailcloud.com 10F4AA00E1A5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peachymango.org; s=8CB80586-E3FE-11EB-B0E7-C1E0928D69D1; t=1780511572; bh=B7RXS3q6XMDi5wADo73cFm+zdCVTEK2TVqOYR3x5Vkw=; h=From:Mime-Version:Message-Id:Date:To; b=oJEdfXjbHl7fwzINz0C/PdRuTFI2j3LYmB3lufWAabLUFqVPal8o7CaoVk2X7Kg63 c/MtT/nIxnVkpg+SNJch74Q5gXPA8LeKtqGLejj1iblZf+JntBh9F+JHZYiqJwl9t8 IbpKz02vEWHVcYGNw6+YancOnwEdQizkLX/O8kSRPlaj8bzO3DzD6rDPBBU3N5DGhD SJCIJSXkYOV6vFr8QYCPDy1f+rQHeOnEm3QK0+pa/KBhE1ZNA4AfigRz+tAUXYrYEy gwuMlBHUqAg1Kjap9x8fLhy+iw6WgCoDfq4vzBYPZWJgt+7lhN6xJl/qRKLJzH5STM uuUltP7UJkNfw== Received: from zmcc-3.zmailcloud.com ([127.0.0.1]) by localhost (zmcc-3-mta-1.zmailcloud.com [127.0.0.1]) (amavis, port 10026) with ESMTP id mh8QSwRswgN6 for ; Wed, 3 Jun 2026 13:32:52 -0500 (CDT) Received: from zmcc-3-mailbox-1.zmailcloud.com (zmcc-3-mailbox-1.zmailcloud.com [172.31.18.168]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTP id E641BA00E1A4 for ; Wed, 3 Jun 2026 13:32:51 -0500 (CDT) From: Franck Martin Content-Type: multipart/alternative; boundary="Apple-Mail=_28121D4A-E527-4DF6-906E-7EEFF1F1EB93" Mime-Version: 1.0 Subject: How to make an elegant IPv4 outage Message-Id: <456388925.296572478.1780511571678.JavaMail.zimbra@zmcc-3-mailbox-1.zmailcloud.com> Date: Wed, 3 Jun 2026 13:32:51 -0500 (CDT) To: ietf@ietf.org X-Mailer: Apple Mail (2.3864.600.51.1.1) X-Mailer: Zimbra 10.1.13_GA_4837 (AppleExchangeWebServices/Mail/) Sender: Franck Martin Thread-Index: +WK3V7FoomUcsreJyduHOQqgBU0B4g== Thread-Topic: How to make an elegant IPv4 outage Message-ID-Hash: 6DFDOHSPNW5M6ATRLW6NOOUXSOPEHWKJ X-Message-ID-Hash: 6DFDOHSPNW5M6ATRLW6NOOUXSOPEHWKJ X-MailFrom: franck@peachymango.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9rc6 Precedence: list List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Apple-Mail=_28121D4A-E527-4DF6-906E-7EEFF1F1EB93 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi all, Today I submitted this Internet Draft (I-D) to the IETF https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ I have been building this site: pacific.ipv6forum.com = and I have been wondering, how could I = do an IPv4 outage on this site on 6/6? I have also seen that Czechoslovakia has mandated the end of IPv4 on = government sites on 6/6/2032, 6 years from now. I also recall (from recent experience) that it is relatively easy to = reach >90% of IPv6 connections to an internal network (think = datacenter), but the remaining last % are difficult to identify (or = discard) because services may misbehave and prefer IPv4 from time to = time: You don't know if they can't really do IPv4 or if they did not = bother to do IPv6. In an enterprise environment, micro-services are made redundant, there = are multiple IPs and have fallback mechanisms when they encounter a 5xx = error on one endpoint.=20 So, I started to work on this Internet Draft. It is ready for the first = round of public comments. I suspect, if successful, it will take 1 or 2 = years to make it a standard. Then an extra 1 or 2 years, before it is = implemented on enough clients (and browsers), we will be just in time = for doing enough IPv4 outages on 6/6 to meet the 6/6/2032 deadline. Oh, and on 6/6 pacific.ipv6forum.com = will have this IPv4 outage, and then on every 6th day of the month. May = be the scraping bots will notice the new error code, and their humans = will do something about it? I may even do the same on peachymango.org I know this is not for everyone, but for the few that want to do this, = let=E2=80=99s offer them some elegant solutions. Now I don=E2=80=99t know which is the best IETF WG to discuss this. It = is an HTTP extension, so likely HTTPBis, but this is about IPv6, so may = be v6ops or 6man? Well if any of this group thinks it is a good idea. Franck= --Apple-Mail=_28121D4A-E527-4DF6-906E-7EEFF1F1EB93 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = all,

Today I submitted this Internet Draft (I-D) to the = IETF
https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/<= span style=3D"font-size: 14px; box-sizing: inherit; margin: = var(--artdeco-reset-base-margin-zero); padding: = var(--artdeco-reset-base-padding-zero); border: = var(--artdeco-reset-base-border-zero); vertical-align: = var(--artdeco-reset-base-vertical-align-baseline); outline: = var(--artdeco-reset-base-outline-zero); caret-color: rgba(0, 0, 0, 0.9); = color: rgba(0, 0, 0, 0.9); line-height: inherit !important;">

I have been building this site: pacific.ipv6forum.com and I have been wondering, how = could I do an IPv4 outage on this site on 6/6?

I have also seen that Czechoslovakia has mandated the end of IPv4 = on government sites on 6/6/2032, 6 years from now.

I also recall (from recent experience) that it is relatively easy = to reach >90% of IPv6 connections to an internal network (think = datacenter), but the remaining last % are difficult to identify (or = discard) because services may misbehave and prefer IPv4 from time to = time: You don't know if they can't really do IPv4 or if they did not = bother to do IPv6.

In an enterprise environment, = micro-services are made redundant, there are multiple IPs and have = fallback mechanisms when they encounter a 5xx error on one = endpoint.

So, I started to work on this Internet Draft. It is ready for the = first round of public comments. I suspect, if successful, it will take 1 = or 2 years to make it a standard. Then an extra 1 or 2 years, before it = is implemented on enough clients (and browsers), we will be just in time = for doing enough IPv4 outages on 6/6 to meet the 6/6/2032 = deadline.

Oh, and on 6/6 pacific.ipv6forum.com&nbs= p;will have this IPv4 outage, and then on every 6th day = of the month. May be the scraping bots will notice the new error code, = and their humans will do something about it?

I may even do the same on peachymango.org

I know = this is not for everyone, but for the few that want to do this, let=E2=80=99= s offer them some elegant solutions.

Now I don=E2=80=99t know which is the best IETF WG to discuss = this. It is an HTTP extension, so likely HTTPBis, but this is about = IPv6, so may be v6ops or 6man? Well if any of this group thinks it = is a good idea.

Franck
= --Apple-Mail=_28121D4A-E527-4DF6-906E-7EEFF1F1EB93--