u/FranckMartin

"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?