4 ms·

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.

jandrese 9y ago
Shoving IPv6 into the DOCSIS3 spec was really forward looking for the industry. 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.
- takeda 9y ago
  Kind of reminds me of Python 3 migration, no one was willing to do it until running 2.7 became bigger and bigger hassle. And even then people rarely looked ahead and try to make their code forward compatible. At least it looks like Py3 was finally accepted.
- javajosh 9y ago
  I believe that IPv6 is a threat to Verizon's business model. Without net neutrality, V can be a paid gatekeeper to centralized services; IPv6 is a tool useful for connecting decentralized resources, and so erode's one of V's revenue sources.
lwhalen 9y ago
I beg to differ. I've got Comcast in the PNW, and their IPv6 stack on Business class is atrocious. A short list of the issues I've had/am currently experiencing: - 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"
- sliken 9y ago
  Comcast consumer lines work great. You get a /60, it works, end of story.
  - apple4ever 9y ago
    Disagree. Unlike their IPv4 setup, where the IP rarely changes, the IPv6 address constantly changes for no apparently reason. This makes it hard to whitelist IPs or to set up an internal IPv6 network. 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.

jandrese 9y ago

Shoving IPv6 into the DOCSIS3 spec was really forward looking for the industry. 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.

takeda 9y ago
Kind of reminds me of Python 3 migration, no one was willing to do it until running 2.7 became bigger and bigger hassle. And even then people rarely looked ahead and try to make their code forward compatible. At least it looks like Py3 was finally accepted.
javajosh 9y ago
I believe that IPv6 is a threat to Verizon's business model. Without net neutrality, V can be a paid gatekeeper to centralized services; IPv6 is a tool useful for connecting decentralized resources, and so erode's one of V's revenue sources.

lwhalen 9y ago

I beg to differ. I've got Comcast in the PNW, and their IPv6 stack on Business class is atrocious. A short list of the issues I've had/am currently experiencing: - 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"

sliken 9y ago
Comcast consumer lines work great. You get a /60, it works, end of story.
- apple4ever 9y ago
  Disagree. Unlike their IPv4 setup, where the IP rarely changes, the IPv6 address constantly changes for no apparently reason. This makes it hard to whitelist IPs or to set up an internal IPv6 network. 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.