Why IPv6 is so complicated

· devtools · Source ↗

TLDR

  • Chapter from the collaborative book6 project argues IPv6’s complexity stems from coexistence math, not design overreach.

Key Takeaways

  • Expanding beyond 32-bit addresses forces a version change, dual-stack or translation, and coexistence overhead – unavoidable regardless of address length chosen.
  • The dual-stack vs. translation matrix (OLD/DUAL/NEW) is a mathematical fact; no “IPv8” proposal escapes it.
  • IPv6 added SLAAC, extension headers, and flow labels – modest additions inspired by DECnet, Netware, AppleTalk – not Second System Syndrome bloat.
  • The mandatory IPsec requirement was a political mistake that slowed deployment until it was dropped.
  • Any replacement protocol would still take 25+ years to deploy, as with DNSSEC, RPKI, and frame relay retirement.

Hacker News Comment Review

  • Thin discussion; commenters push back on the framing: the headline claims IPv6 is complicated but the text concedes it is actually a conservative design, creating a contradiction the author does not fully resolve.
  • One commenter flatly disputes the premise with “It’s not,” suggesting the complexity narrative is overstated or misattributed.

Notable Comments

  • @vaylian: flags internal contradiction – article admits IPv6 is conservative yet headline implies bloat.
  • @api: “It’s not” – direct rebuttal to the core premise.

Original | Discuss on HN