IPv6 is one of the things that Comcast actually does right. I can't believe how slow some of the other ISPs are at adopting it.
Meanwhile Verizon's only visible contribution to getting IPv6 on FiOS has been to delete their IPv6 on FiOS FAQ.
It's a crying shame that a service born in 2005 (10 years after RFC 1883 was finalized!) apparently has no transition plan for IPv6. Even if it wasn't enabled at launch, the network should have been designed for v6 support from the start.
And even then people rarely looked ahead and try to make their code forward compatible.
At least it looks like Py3 was finally accepted.
- Account is registered for a /56, their router only responds to requests for a /59
- Once my CPE is configured for that /59, routing from anything smaller than that /59 is just dropped on the ground (no delegation to/from /64s, etc, is allowed)
- significant investigation later, the root cause is because I also have a /29 static v4 block on my router. Removing the v4 block from the Comcast end, everything works great (as a /59). As soon as the Comcast equipment receives the static v4 config, v6 delegation grinds to a halt
- Comcast Business Support is WOEFULLY under-trained on v6. Talking about v6 netblocks gets me strange stares and "But I see your /29 on the account, is that what you're talking about?"
- Comcast line-managers have told me on multiple occasions, "Oh, if static-v4/v6 doesn't work, then it's just not supported. Sorry, just take your business elsewhere if static is important to you"
I ended up getting an IPv6 /48 from Hurricane because of the hassles. That works great (other than having to force Netflix to IPv4 because of their dumb IP block).
If Comcast offered static IPv6 (NOT via business class), and more than a /60 (/58 at least), that would make it "work great".
For now, it doesn't.