Partially. Telekom keeps up the line for months at a time. I guess that is due to telephony being done via VoIP, and they don't want to interrupt your late night calls.
Others, even Congstar (which is a cheap telekom brand), do 24h disconnects with a new v4 address, and no v6 at all.
The DSL I use gives me a fixed v4 and v6 range, but still needs to do the daily disconnects.
Our TV started to complain that the Wifi module was unplugged (which apparently is on the main board). Problem: This happened regularly with a dialog box. 'Solution': Put a Wifi dongle in the USB port.
The TV of my childhood took so long to warm up, you'd be standing there for at least 5 seconds wondering if it had turned on at all before seeing something. Usually it was the click of a relay and the hum of a capacitor soaking up a field that was the real clue.
From my vantage point, it is already. The only parties that don't have IPv6 are my employer (which I maybe need to nag about since we're an ISP and have our own AS), and the customer I'm dealing with.
Practically, my laptop is in some Wifi network and has an IPv6 address, but that isn't accessible from the outside because the Wifi/router box blocks incoming connection. That is a wise decision overall, but unforunately replaces the "can't connect because NAT" by "glorious IPv6, bit still can't connect".
I've had a static IPv4 subnet allocation from AT&T on AT&T U-verse, and tried using it on a couple of consumer routers for the local network. Well, guess what — all these devices from major brands that are called "routers" don't actually route between the interfaces, after all — all they did was NAT between my public IPv4 allocation and the main IPv4 address assigned by DHCP. And disabling the NAT simply disconnected the networks — instead of rounting one interface to the other. I actually opened up a support ticket with ZyXEL, which got escalated to their engineering managers, and they did confirm my finding that their routers had a bug in sysctl settings that stops them from routing the interfaces (e.g., sysctl net.ipv4.ip_forward not set to 1).
Anyhow, back to T-Mobile US IPv6 on a hotspot — when I originally tried ssh'ing back to my own box via the public IPv6, things didn't work, either; but I then found out that it was some sort of a local policy on the local machine, because another laptop without a firewall was able to receive connections on IPv6 from the internet without any issues.
Mobile carrier NAT, mobile device hotspot NAT, vmware NAT - that's the most I've seen so far.
But IPv6 in home networks replaces the unreachability-because-of-NAT by unreachability-because-of-filtering. The usual home router protects your clients, and if it's not your box, you're out of luck.
To think of it - I might have heard these two pass by. Not on that flight, but I lived with my parents in northern germany, not far from the danish border, and en route from the north to the baltic sea and on to russia. I often heard the badam, accompanied by a creak of the wooden roof.
Kleinwalsertag. Austrian territory, but only reachable (by road) through germany. Was connected to german phone network, which changed once telco stuff got smart enough. Effect: For some time a german and an austrian phone number reached the same phone.
Others, even Congstar (which is a cheap telekom brand), do 24h disconnects with a new v4 address, and no v6 at all.
The DSL I use gives me a fixed v4 and v6 range, but still needs to do the daily disconnects.