Return-Path: 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 3811C10BD8616; Wed, 1 Jul 2026 13:30:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1782937801; bh=zmK1hDWnI3+B/B0J8A9xqNvMj/+0LYs4kWv+m0LGKHU=; h=Date:From:To:Cc:In-Reply-To:References:Subject; b=Mh9sUnd+LeIfgtiOOvG8ZE/npf0ue0/eKVWMM686s4V8vf9wfkHET20AgxRLRx49H VwGp29ww+2DQj5z5B8100IzbLVZkE27imCgvzfi/b7xcuW9bTffNU/qqZ/YOLNWgO6 c3yl9n1U24atO4ZvH1dwy6DmB1dWuGS1GHSxK5R4= X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -2.797 X-Spam-Level: X-Spam-Status: No, score=-2.797 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_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 XdD2Zti8sAra; Wed, 1 Jul 2026 13:29:59 -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 3F1F210BD58E9; Wed, 1 Jul 2026 13:27:09 -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 4BB14781D5E1; Wed, 1 Jul 2026 15:27:02 -0500 (CDT) Received: from zmcc-3.zmailcloud.com (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTPS id 27F4DA00E323; Wed, 1 Jul 2026 15:27:02 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by zmcc-3-mta-1.zmailcloud.com (Postfix) with ESMTP id 0CBC6A00E339; Wed, 1 Jul 2026 15:27:02 -0500 (CDT) DKIM-Filter: OpenDKIM Filter v2.10.3 zmcc-3-mta-1.zmailcloud.com 0CBC6A00E339 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=peachymango.org; s=8CB80586-E3FE-11EB-B0E7-C1E0928D69D1; t=1782937622; bh=zmK1hDWnI3+B/B0J8A9xqNvMj/+0LYs4kWv+m0LGKHU=; h=Date:From:To:Message-ID:MIME-Version; b=Sb6jfbXZOXm5IyALNCt9U/GCweHizk9S8wULJE+Bq+Ad7UosXZueXSU4DcqgD8iSg EfnXGy29bslYCB2hj7y6SX5awf7lz+Bj8d2ITagywWMgM2myRAs1+cu6vRjJM61Oc7 OeOKBzkvGoXxZGItBgxVi587AambEO1H9G57I9F2aZ+3DNP3Y6qgyqB7ILh5myhO4h rvwLMj9C1rr6LW4dlbrg4mJjR7yhxDtMERYnQczsEPYSQvozsAMZ8swRh4/oTjSuCt wrcQMBbQdgSY1zXTWvQU25UvXFgAF+d6f/9eLnGpttgJwHmvpOfqWpxmqHrZjJZFHC sxij5NXCGp/4w== 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 kjy8QBEDeL2C; Wed, 1 Jul 2026 15:27:01 -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 C8CF3A00E323; Wed, 1 Jul 2026 15:27:01 -0500 (CDT) Date: Wed, 1 Jul 2026 15:27:01 -0500 (CDT) From: Franck Martin To: Mirja Kuehlewind Message-ID: <1789666940.33457565.1782937621585.JavaMail.zimbra@peachymango.org> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_ad900016-1891-4ece-93e9-77e29d3e7079" X-Mailer: Zimbra 10.1.18_GA_4890 (ZimbraWebClient - SAF26.5 (Mac)/10.1.17_GA_4873) Thread-Topic: draft-martin-retry-over-ipv6-02 requesting review/additional comments Thread-Index: AQHdCTbWDviWoiUMW0m8cQKtlG14evIyVrrn Message-ID-Hash: B7UF5IA33MIK7UTBDPASEGX2EPPAU7IR X-Message-ID-Hash: B7UF5IA33MIK7UTBDPASEGX2EPPAU7IR X-MailFrom: franck@peachymango.org 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: v6ops , witarea , ietf-http-wg@w3.org X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BWitarea=5D_Re=3A_draft-martin-retry-over-ipv6-02_requesting_rev?= =?utf-8?q?iew/additional_comments?= List-Id: "Web and Internet Transport (WIT) Area" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=_ad900016-1891-4ece-93e9-77e29d3e7079 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Mirja,=20 Good suggestion.=20 Folks on httpbis,=20 This is about [ https://datatracker.ietf.org/doc/draft-martin-retry-over-ip= v6/ | draft-martin-retry-over-ipv6. ]=20 It is about helping the retirement of IPv4 by providing some transition mec= hanisms. This is part of v6ops but it really needs some http expertise.=20 I'm not tied to a particular error code. I have tried to figure out which c= lass would be best, between 4xx and 5xx. Some folks even suggested using 3x= x, but I'm worried about infinite loops.=20 It may help to understand this draft by placing it into a bigger context, w= hich is described in [ https://datatracker.ietf.org/doc/draft-martin-deploy= ing-ipv6-data-center/ | draft-martin-deploying-ipv6-data-center. ]=20 There is also a short discussion on Reddit: [ https://www.reddit.com/r/ipv6= /s/lBQCFI4ucI | https://www.reddit.com/r/ipv6/s/lBQCFI4ucI ]=20 and some past thread on v6ops/witarea=20 Franck Martin=20 [ https://www.peachymango.org/ | https://www.peachymango.org/ ]=20 From: "Mirja Kuehlewind" =20 To: "Franck Martin" , "v6ops" , "wi= tarea" =20 Sent: Wednesday, July 1, 2026 1:51:41 AM=20 Subject: Re: [Witarea] draft-martin-retry-over-ipv6-02 requesting review/ad= ditional comments=20 Hi Franck,=20 you should probably also send this to the httpbis list.=20 Mirja=20 From: Franck Martin on behalf of Franck Martin =20 Date: Tuesday, 30. June 2026 at 20:49=20 To: v6ops , witarea =20 Subject: [Witarea] draft-martin-retry-over-ipv6-02 requesting review/additi= onal comments=20 Hi all,=20 Some suggested that a 4xx code could be better, so I checked the pros and c= ons and added language in this draft on the various aspects of 566 vs 466. = Also checked if there is any current behavior for common software for retry= ing after any HTTP error code.=20 Spolier alert: 566 still seems better.it is not an error on the client part= , It is the server that refuses to honor the connection.=20 This new draft has this added language:=20 [ https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ | https://= datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ ]=20 To be noted, I implemented this draft on my site: [ https://pacific.ipv6for= um.com/ | https://pacific.ipv6forum.com/ ] so that on the 6th of every mont= h, IPv4 is not served. I had some implementation nits that prevented me fro= m getting good logs. I hope this time I will have better logs, therefore be= tter reports to share with folks.=20 In a couple of days, the site will show a banner announcing the IPv4 outage= .=20 At the moment, I have not convinced a WG to formally =E2=80=9Chost=E2=80=9D= the discussion. I won=E2=80=99t be able to attend IETF Vienna as to gather= more support, but appreciate if some folks could be a proxy.=20 Franck Martin=20 [ https://www.peachymango.org/ | https://www.peachymango.org ]=20 --=_ad900016-1891-4ece-93e9-77e29d3e7079 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Hi Mirja,


Good suggestion.


=

Folks on httpbis,


This is about draf= t-martin-retry-over-ipv6.


It is about helping th= e retirement of IPv4 by providing some transition mechanisms. This is part = of v6ops but it really needs some http expertise.


<= /p>

I'm not tied to = a particular error code. I have tried to figure out which class would be be= st, between 4xx and 5xx. Some folks even suggested using 3xx, but I'm worri= ed about infinite loops.


It may help to understand this draft by p= lacing it into a bigger context, which is described in draft-martin-deploy= ing-ipv6-data-center.


There is also a short discussion on Red= dit: https://www.reddit.com/r/ipv6/s/lBQCFI4ucI=


=
and some past thread on v6ops/witarea

Franck Martin

From: = "Mirja Kuehlewind" <mirja.kuehlewind@ericsson.com>
To: = "Franck Martin" <franck@peachymango.org>, "v6ops" <v6ops@ietf.org&= gt;, "witarea" <witarea@ietf.org>
Sent: Wednesday, July 1, = 2026 1:51:41 AM
Subject: Re: [Witarea] draft-martin-retry-over-ip= v6-02 requesting review/additional comments

Hi Franck= ,

you sh= ould probably also send this to the httpbis list.

Mirja<= /span>

From: F= ranck Martin <franck@peachymango.org> on behalf of Franck Martin <= franck@peachymango.org>
Date: Tuesday, 30. June 2026 at 20:49
To: v6ops <v6ops@ietf.org>, witarea <witarea@ietf.org> Subject: [Witarea] draft-martin-retry-over-ipv6-02 requesting review= /additional comments 

Hi all, 

Some suggested that a 4xx= code could be better, so I checked the pros and cons and added language in= this draft on the various aspects of 566 vs 466. Also checked if there is = any current behavior for common software for retrying after any HTTP error code.

Spolier alert: 566 still = seems better.it is not an error on the client part, It is the server that r= efuses to honor the connection.

This new draft has this a= dded language: 

https://datatracker.ietf.org/doc/draft-martin= -retry-over-ipv6/ 

To be noted, I implemente= d this draft on my site: https://pacific.ipv6fo= rum.com/ so that on the 6th of every month, IPv4 is not served. I had s= ome implementation nits that prevented me from getting good logs. I hope this time I will have bet= ter logs, therefore better reports to share with folks.

In a couple of days, the = site will show a banner announcing the IPv4 outage.

At the moment, I have not= convinced a WG to formally =E2=80=9Chost=E2=80=9D the discussion. I won=E2= =80=99t be able to attend IETF Vienna as to gather more support, but apprec= iate if some folks could be a proxy.

Franck Martin


--=_ad900016-1891-4ece-93e9-77e29d3e7079--