It would be good if experimental can be dropped. I'm not sure if that is tied to any other features or causes any other unrelated feature changes beyond enabling ip6tables.

The IPv6 docs could be improved too, and not having this extra step is helpful. I'm currently revising IPv6 config docs for a docker focused project since our users often have trouble with official advice and the guidance from third-party resources over time isn't necessary correct or missing some information 😅

I think ip6tables can remain opt-in, and the docs can still express that support for IPv6 itself is still being worked on? Private NAT6 network with ULA subnet seems to be fine and familiar for users though for the most part. That can perhaps be endorsed via docs. GUA subnet is a bit more fragile/variable and affected by the host environment.

It would be good if experimental can be dropped. I'm not sure if that is tied to any other features or causes any other unrelated feature changes beyond enabling ip6tables.

We have since introduced feature flags. I don't think we'll add one for ip6tables, it'd be best to move it out of experimental state.

The IPv6 docs could be improved too

Yeah, the docs page about IPv6 is pretty much all wrong, I need to fix that. It's part of my todo list but I need to work on some other subjects first.