[Witarea] Re: draft-martin-retry-over-ipv6-02 requesting review/additional comments

[Franck Martin <[e-mail]>]

Hi Mirja, 




Good suggestion. 




Folks on httpbis, 




This is about [ https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ | draft-martin-retry-over-ipv6. ] 




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




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




It may help to understand this draft by placing it into a bigger context, which is described in [ https://datatracker.ietf.org/doc/draft-martin-deploying-ipv6-data-center/ | draft-martin-deploying-ipv6-data-center. ] 




There is also a short discussion on Reddit: [ https://www.reddit.com/r/ipv6/s/lBQCFI4ucI | https://www.reddit.com/r/ipv6/s/lBQCFI4ucI ] 

and some past thread on v6ops/witarea 

Franck Martin 
[ https://www.peachymango.org/ | https://www.peachymango.org/ ] 


From: "Mirja Kuehlewind" <[e-mail]> 
To: "Franck Martin" <[e-mail]>, "v6ops" <[e-mail]>, "witarea" <[e-mail]> 
Sent: Wednesday, July 1, 2026 1:51:41 AM 
Subject: Re: [Witarea] draft-martin-retry-over-ipv6-02 requesting review/additional comments 


Hi Franck, 

you should probably also send this to the httpbis list. 

Mirja 


From: Franck Martin <[e-mail]> on behalf of Franck Martin <[e-mail]> 
Date: Tuesday, 30. June 2026 at 20:49 
To: v6ops <[e-mail]>, witarea <[e-mail]> 
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 refuses to honor the connection. 


This new draft has this added language: 


[ https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ | https://datatracker.ietf.org/doc/draft-martin-retry-over-ipv6/ ] 


To be noted, I implemented this draft on my site: [ https://pacific.ipv6forum.com/ | https://pacific.ipv6forum.com/ ] so that on the 6th of every month, IPv4 is not served. I had some implementation nits that prevented me from getting good logs. I hope this time I will have better 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 “host” the discussion. I won’t be able to attend IETF Vienna as to gather more support, but appreciate if some folks could be a proxy. 


Franck Martin 


[ https://www.peachymango.org/ | https://www.peachymango.org ]