u/FranckMartin

Hi all,

Not many changes in that new version.

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

When to send (§): on the public Internet, operators SHOULD prefer emitting 503 + Retry-Over-IPv6 only for human-facing HTML documents and omit typical subresources (images, scripts, stylesheets, fonts); non-interactive clients (e.g. webmail image loads) otherwise see a broken asset with no explanation. Operator-controlled environments MAY still signal all IPv4 requests for fuller measurement. Cross-reference from Intended Deployment.

This change came from my experience when I migrated my mailing list from Mailchimp to my own web server, but noticed that web clients could not load the embedded images in the email as they were on my site.

1. Even GMail which understands IPv6, will prefer IPv4
2. The email looks broken with little idea on the client side, why.

Note: the following websites are implementing the IPv4 outage on the 6th for 24 hours, which should starts very soon:

• ipv6forum.com
• pacific.ipv6forum.com
• caribbean.ipv6forum.com
• whynoipv6.com
• www.peachymango.org

I you want to follow those websites, instructions at:

https://github.com/franckhlmartin/ietf-draft-retry-over-ipv6/tree/main/docs

And please send comments or your feedback in running this experiment. Please open an issue on the github repo or message v6ops at IETF.

Franck

I really like cursor, but I feel it is going downhill since acquired by grok. I like that they have a cheap model, that I can manage by being smart and not run out of tokens. So what alternative for $25month?

May be if they had their scanning bot to prefer IPv6 or their GMail image loader to prefer IPv6 we would see a big improvement on the IPv6 adoption worldwide. I'm sure they have other automations that do not prefer IPv6.

Note for the admins: can we add a flair "Life without IPv4" ?

"You can't fix, what you don't monitor"

After building this site: https://pacific.ipv6forum.com I was requested to build the same but for the Caribbean. I use EEZ because land masses are difficult to see on a map for island countries. It uses the same code base, and it is on Github. It uses data from APNIC for the IPv6 % preference, but also monitor sites for their deployment of IPv6 and measure a couple of extra standards (DNSSEC, DMARC, RPKI,...)

If there are domain names missing or errors, please let me know, or better submit a PR.

Hi all,

The I-D retry-over-ipv6 is stabilizing, so I thought I would make a call for volunteers if you are brave enough to implement a regular IPv4 outage on your web server.

I'm not calling it for any web server, but you know your users and you know if an IPv4 outage is something that would show you being an IPv6 visionary or just damn annoying 😜

Please check the README on: https://github.com/franckhlmartin/ietf-draft-retry-over-ipv6/tree/main/docs

There is an executive call for action and also code snippets on how to implement it.

You will also find a list of sites that are doing this IPv4 outages on a regular basis.

Another dead seal left on the beach next to the stream in Linda Mar.

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/

To be noted, I implemented this draft on my site: 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 IETF 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.

During my IPv4 outage experiment, someone mentioned that it could reach the site over the IPv4 network because it enabled iCloud Private Relay on iOS/MacOS ?

Can you confirm? Are there similar capabilities on other platforms?