Geert Jan de Groot via ipv6-wg <ipv6-wg@ripe.net> wrote: > In past years, I have used https://test-ipv6.com/ as a quick "sanity test" > when connecting to a network, using a guest network, or to check network > configuration after making changes. I found it very useful for quick tests. Me too, for exactly those reasons too. I didn't know about the retirement. (Sounds like JFESLER will be wrangling children. I wonder if each child get their own /48? ) > Unfortunately, jfesler is announcing sunsetting the project, see > https://retire.test-ipv6.com/. > In the FAQ, it is mentioned "Q: Will I (jfesler) transfer the domain? > A: I’d consider a reputable RIR or NIC organization serving the public > interest taking things over." > I wonder if a RIR or NIC organisation would consider taking over to run the > service. I think it is too useful to just disappear, there are still too many > not-quite-IPv6 networks, and personally I hope I don't lose the service. My impression, having not read the code, that 80% of what it does is in the client in JS. I see that there are a few repos listed that provide feedback for the outside IP address, and for the MTU testing. Those would seem to require a VM on which to run this netfilter daemon. What can we easily maintain if we just have some static v4 and v6 resources? Can the outside IP address be as simple as a one-line PHP script? I could easily provide a VM (v4+v6) in Canada for this, but I'd need help with maintenance. My javascript-fu continues to decline. I don't remember advertising on the page before. It would be awesome if RIPE or another RIR took over this as an official tool. One thing I'd like is the report in JSON format that an end-user could download/attach to their support people. -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide