Introduction to IPv6: The Future of Internet Addressing
What does IPv6 solve, and what work remains? Understand address space, coexistence costs and Lu Heng’s case for letting operators decide.
A new online shop wants every customer to reach its website. Someone recommends IPv6: more addresses, newer technology, the future of the internet. But the shop still has customers using IPv4. Adding IPv6 does not make that part of the job disappear.
That is the useful starting point for understanding IPv6. It offers a much larger address space. Whether adopting it improves a particular network depends on the customers it must reach, the work it removes and the work it adds.
What IPv6 changes
An IP address helps networks deliver data to the right destination. IPv4 uses 32-bit addresses; IPv6 uses 128 bits. The difference is enormous: IPv4 has roughly 4.3 billion possible addresses, while IPv6 provides vastly more room for assigning addresses and organizing networks. The IPv6 specification also describes changes to packet handling and support for automatic address configuration.
For a network that needs many addresses, that extra room can be useful. It does not, by itself, make a website faster or encrypt its traffic. Security still requires deliberate configuration. The IETF’s IPv6 security guidance makes clear that supporting IPsec, a set of security protocols, does not mean it is automatically deployed.
Why “more addresses” does not mean “migration finished”
IPv4 and IPv6 use different packet formats. A service using only one cannot simply assume it can communicate directly with a customer using only the other. A network can support both, or use a suitable translation arrangement.
Supporting both is called dual stack. As the IETF’s transition specification explains, it means implementing both IPv4 and IPv6. For our shop, enabling IPv6 may add a way for customers to connect while leaving a continuing need for IPv4.
The practical cost is ongoing work: testing both paths, applying security policy to both and investigating failures that affect only one. Shared tools can help, but the responsibility remains. A successful IPv6 launch and a successful IPv4 retirement are different milestones.
Who decides whether that cost is worth paying?
Lu Heng challenges the claim that every operator should accept this arrangement as an inevitable stage of progress. In Note 40, on who IPv6 promotion serves, he asks readers to examine the incentives of registries and equipment vendors alongside the interests of the operators paying for deployment.
His argument is about power as well as engineering. More available numbers do not, on their own, make the institutions administering those numbers accountable. Nor does a protocol upgrade settle who should control an operator’s investment decisions. Note 40 explicitly rejects banning or suppressing IPv6; it calls for judging the technology from the operator’s position.
A business decision needs a business case
Before committing, ask three questions: Which customer or operational problem will IPv6 solve? What will it cost to run the resulting network, including coexistence? What would allow the old work to stop, and is that condition actually within reach?
If there is a concrete benefit, evaluate it. If the case rests only on being told that migration is inevitable, ask who bears the cost if coexistence continues. Lu Heng’s alternative is operator choice: the people responsible for building and sustaining a network should decide its direction, rather than treating an institution’s preferred roadmap as an obligation.
This matters when budgets and equipment purchases are agreed, before a temporary transition becomes a standing expense. To follow the argument further, read Note 33: why Lu Heng calls prolonged coexistence a “dual-stack tax”.