Merit Logo Merit IconSet
Skip to content

Start Your IPv6 Journey

About IPv6

IPv6, or Internet Protocol version 6, is designed to replace the aging IPv4 protocol—and the urgency to do so is no longer theoretical. The global pool of IPv4 addresses has been effectively exhausted, forcing organizations to rely on stopgap measures like Network Address Translation (NAT). While NAT extends IPv4 usability, it introduces significant complexity, reduces end-to-end visibility, and can weaken security posture by obscuring device identity and complicating threat detection.

IPv6 solves the address exhaustion problem outright with an almost inexhaustible address space (2¹²⁸ addresses), enabling true end-to-end connectivity again. This eliminates the need for NAT, simplifying network architecture and improving performance and traceability. Additionally, IPv6 was built with modern security in mind: support for IPsec is standardized, address scanning is vastly more difficult due to the sheer size of the address space, and features like Secure Neighbor Discovery (SEND) enhance protection at the network layer.

Organizations that delay IPv6 adoption are not just postponing an upgrade—they are increasing operational risk. Continuing to depend solely on IPv4 means relying on increasingly fragile workarounds, shrinking address availability, and reduced compatibility with modern services. The most effective path forward is dual-stack deployment (IPv4 + IPv6) with a clear roadmap toward full IPv6 adoption.

This page provides IPv6 resources and information for Michigan communities.

Merit and the University of California, through the NSF CC* (Campus Cyberinfrastructure) grant, are working to advance a more resilient IPv6 internet through both research and practical implementation.

A woman works on a laptop at a desk

Why IPv6

IPv6 has moved well beyond early adoption and is now a critical component of the modern internet. Over the past decade—especially in the last five years—global IPv6 traffic has grown substantially, with major platforms like Google and Meta Platforms delivering services over IPv6 at scale and increasingly prioritizing it within their infrastructure. Many mobile networks already operate predominantly on IPv6, using IPv4 only as a compatibility layer.

At the same time, IPv4 is becoming more costly and less viable. The secondary market for IPv4 addresses continues to drive prices upward, and reliance on NAT-heavy environments creates bottlenecks, degrades application performance, and limits innovation—particularly for emerging technologies like IoT, edge computing, and large-scale sensor deployments. From a security standpoint, IPv6 enables more direct device-to-device communication with clearer attribution, while modern network designs can implement more consistent and scalable security policies without NAT interference.

The transition is no longer optional—it is inevitable. As more content, services, and networks optimize for IPv6, organizations that remain IPv4-dependent will face degraded performance, increased costs, and growing security blind spots. Deploying IPv6 now ensures compatibility, improves resilience, and positions organizations to fully participate in the future internet rather than struggle to catch up to it.


IPv6 Myths vs Reality

We can always go get more IPv4 addresses if we need to.
Some organizations may think that they don’t need to buy any more IPv4 addresses, so they believe that they are unaffected by market forces. ARIN doesn’t have any additional IPv4 address space to assign. Prices of IPv4 address space will continue to rise over time. Planning to purchase additional IPv4 address space to avoid IPv4 address depletion creates an unnecessary capital expenditure, subject to unknown market pricing.

We can sell our IPv4 address space and make money.
IPv4 address prices will likely drop before an organization gets enough IPv6 addresses to convert. The only way this strategy makes sense is if an organization aggressively deploys IPv6 in the next year or two to be able to sell its IPv4 assets at the peak price before the price deadline.

We can’t establish multi-homing to multiple ISPs with IPv6.
The core of the internet runs IPv4 and IPv6 on the same layer-2 and physical connections at the same time, so this cannot be true. Routes between and among ISPs and end-user organizations use the Multi-Protocol Border Gateway Protocol (MP-BGP) the same way for IPv4 and IPv6. The same methods of peering networks for IPv4 exist for IPv6. Enterprises can be EBGP peered with many organizations using IPv6, just as is done with IPv4.

We have no interest in being on the “bleeding edge” with something like IPv6.
IPv6 is no longer a “bleeding edge” technology. It has existed for over 20 years. IPv6 is implemented in the software running all routers, switches, firewalls, host operating systems, mobile devices, and the cloud infrastructure. IPv6 is considered mainstream – nearly half of the internet traffic is IPv6. Organizations that have IPv6 deployed today are in the early majority. If an organization doesn’t deploy IPv6 within the next two years, it will be in the late majority phase.

We don’t want to switch from IPv4 to IPv6. We still have IPv4 systems that need to function
Some people still hold on to the misconception that they need to migrate completely from IPv4 to IPv6 all at once. This is not the case. Most organizations will move through the dual-protocol phase (running both protocols simultaneously) on their way to an IPv6-only network.

IPv4 and NAT help protect our end-users from the internet.
It is a common security misconception that the absence of NAT in IPv6 makes it less secure and allows remote organizations to “map” your internal IP address network topology. The truth is that NAT is not a security measure. Stateful packet filtering will help keep your “internal” nodes safe and prevent unsolicited inbound connections. Relying solely on a perimeter defense such as NAT is a flawed security approach anyway because erosion of the security perimeter can still occur. NAT complicates configurations and troubleshooting. Why would you want to use NAT if you could avoid having to deal with it?

We are not running IPv6. We have disabled IPv6 on our hosts (via a Microsoft GPO), so we are not at risk.
All the host operating systems in your environment and mobile devices today already use IPv6. You have IPv6 packets on your access and data center LANs. End-users at their homes likely already have IPv6. When users move to remote locations, they likely have IPv6 internet connectivity. Even if you have turned off the IPv6 protocol on the interfaces, IPv6 is still running in the kernel (you can always ping::1). Microsoft recommends keeping IPv6 enabled and will deny you support if you disable it. You have not disabled IPv6 on all your Linux, BYOD/mobile devices, printers, IP cameras, guest operating systems, and remote workers’ computers. Disabling IPv6 gives one additional step for deploying IPv6. You must re-enable IPv6.

IPv6 provides greater security than IPv4. IPv6 has weaker security than IPv4.
IPv6 is not secure by default. Just like IPv4, there is no inherent security built into IPv6. IPsec is not mandated for all IPv6 communications. IPsec is optionally implemented with IPv6- the same situation as IPv4. The same vulnerabilities that exist in IPv6’s Neighbor Discovery Protocol (NDP) exist in the Address Resolution Protocol (ARP) for IPv4. Both IPv4 and IPv6 packets can be spoofed and are susceptible to interception and eavesdropping. IPv6 traffic is no less likely to be sniffed than IPv4. Attacks at the application layer are unaffected by IPv6. IPv6 is neither more nor less secure than IPv4. Similarly, IPv6 is not any weaker than IPv4.

Adding IPv6 can cause network instability.
Adding IPv6 to a network already running IPv4 will not affect the existing IPv4 traffic in any way. The packets will pass by each other like “ships in the night.” The IPv6 and IPv4 protocols are incompatible and not backward or forward compatible. An IPv6-only host cannot communicate with an IPv4-only host, and are therefore mutually exclusive to one another. However, if there is instability in the underlying physical layer infrastructure, it will affect both IPv4 and IPv6.


IPv6 Benefits

IPv6 can be faster than IPv4
In many real-world scenarios, IPv6 is now as fast as—or faster than—IPv4. This is largely due to the widespread use of Carrier-Grade NAT (CGN/LSN) in IPv4 networks. IPv4 traffic is often forced through multiple layers of NAT, backhauled through centralized infrastructure, and constrained by limited TCP/UDP port availability. These factors introduce latency, reduce reliability, and create congestion points.

By contrast, IPv6 restores true end-to-end connectivity, eliminating the need for NAT in most deployments. Major providers like Google and Meta Platforms have reported measurable performance improvements for users connecting over IPv6. Data from APNIC also shows that IPv6 often outperforms IPv4 globally.

This performance gain benefits both service providers and end users: IPv6-enabled applications are faster to reach, and users on IPv6 networks experience more direct, efficient connectivity. While IPv6 headers are larger, modern hardware acceleration and protocol efficiencies (such as the removal of header checksums at each hop) offset this overhead.

IPv6 provides plentiful addresses
IPv6 uses 128-bit addresses, compared to IPv4’s 32-bit scheme. While IPv4 supports roughly 4.3 billion addresses, IPv6 supports an effectively limitless pool (2¹²⁸ addresses), ensuring scalability for decades to come.

With billions of people and tens of billions of devices already connected—and continued growth in IoT, mobile, and edge computing—IPv6 is the only protocol capable of sustainably addressing global demand. Unlike IPv4, it eliminates the need for address conservation techniques that complicate network design and limit growth.

IPv6 has a simpler addressing model
IPv6 introduces a more structured and hierarchical addressing approach, typically using prefix-based (“slash”) notation aligned on nibble boundaries. This makes address planning, allocation, and aggregation significantly more straightforward than IPv4 subnetting, which often requires complex workarounds due to limited address space.

Because IPv6 removes the dependency on NAT and provides abundant address space, networks can be designed more logically, reducing administrative overhead and improving long-term scalability Dual-stack provides access to the “whole internet.”

Operating in a dual-stack environment (supporting both IPv4 and IPv6) ensures maximum compatibility and reachability. IPv4-only environments—especially those behind CGN/LSN—can experience connectivity limitations due to port exhaustion and shared public IP constraints.

IPv6 enables direct access to IPv6-enabled services without NAT, improving reliability and simplifying communication paths. Dual-stack deployments allow systems to dynamically choose the best available protocol using mechanisms like Happy Eyeballs (RFC 6555), ensuring optimal performance and user experience.

IPv6 helps avoid technological obsolescence
IPv4 is increasingly strained, costly, and dependent on temporary solutions. As more networks, services, and content providers prioritize IPv6, organizations that remain IPv4-only risk degraded performance, limited interoperability, and rising operational costs (including the growing expense of acquiring IPv4 address space).

Adopting IPv6 is not just modernization—it is necessary to maintain full participation in the evolving internet. Early adoption reduces long-term risk and ensures smoother transitions as IPv4 continues to decline.

Enhanced Network Security and Visibility
IPv6 enables stronger, more consistent security architectures by eliminating many of the complications introduced by NAT. With globally unique addressing, organizations gain improved visibility into individual devices and traffic flows, making monitoring, logging, and threat attribution more accurate.

Additionally, IPv6 was designed with native support for IPsec, allowing for standardized encryption and authentication at the network layer. While not always enabled by default, this built-in capability simplifies secure communication compared to IPv4 environments, where security is often layered on top in less uniform ways. Combined with features like Secure Neighbor Discovery (SEND) and reduced reliance on address-sharing, IPv6 allows for more scalable and transparent security policy enforcement.

Improved End-to-End Connectivity
IPv6 restores true end-to-end communication between devices, which was largely lost with widespread NAT in IPv4. This enables more efficient peer-to-peer applications, simplifies real-time communications (like VoIP and video), and reduces the need for complex traversal techniques.

Better Support for Modern Applications and IoT
IPv6 is better suited for large-scale deployments such as IoT, smart infrastructure, and edge computing. Its vast address space and simplified network design allow each device to have a unique, routable address, improving manageability and enabling more advanced automation and orchestration.

More Efficient Routing and Network Design
IPv6’s hierarchical addressing and route aggregation reduce the size of global routing tables and improve routing efficiency. This leads to more scalable internet infrastructure and can contribute to improved network stability and performance over time.


Developing Your Program

IPv6 deployment requires an institution-wide program with a committed interdisciplinary and interdepartmental team whose purpose and goals are supported by the IT leadership. Every institution should create an IPv6 deployment program to successfully achieve its deployment goals. Merit recommends following these steps to prepare for a successful deployment:

Know Your Institution’s IT vision and mission
Knowing your institution’s IT vision and mission will help you decide where, when, and how to phase in IPv6 deployment so that it will support your institution’s IT vision and mission. This helps its integration into the ongoing IT advancement efforts.

Understand Why IPv6 Deployment Has Taken So Long but is Now Increasing
Understanding the commonly known benefits, barriers, excuses, myths, and misconceptions to IPv6 deployment will help you develop a business case for your institution’s IPv6 deployment initiative. (See HexaBuild’s “IPv6 Deployment: Benefits, Barriers, Excuses, Myths, and Misconceptions.”)

Develop Your IPv6 Deployment Business Case
Identify the IPv6 deployment benefits, barriers, excuses, myths, and misconceptions that pertain to your institution. Write a business case to justify IPv6 deployment using what you have identified. State how IPv6 deployment supports the institution’s IT vision and mission.

Identify Your IPv6 Deployment Goals
Review a range of possible deployment goals that support the IT vision and mission. Decide which ones are achievable for increasing IPv6 adoption within your institution’s time frames.

Assess Portions of the IT Infrastructure
Assess only those portions of the network that are included in your deployment goals, not your whole IT infrastructure. This will give you enough accurate information to create your IPv6 deployment roadmap.

Determine Your IPv6 Deployment Roadmap
Each IPv6 deployment goal will include a set of detailed tasks and activities that need to be performed to achieve the goal. This set of tasks and activities defines your IPv6 deployment roadmap.

Create Your IPv6 Deployment Proposal
Combine your IPv6 deployment business case, goals, roadmap, and team definition into an IPv6 deployment proposal to present to the IT leadership for approval.

Obtain IT Leadership Approval
Present your IPv6 deployment report to your IT leadership for approval. Modify the proposal as necessary until approval is achieved. You won’t be able to proceed with deployment until your IT leadership supports you.


Increase Your Knowledge

Learning IPv6 technology can seem daunting, given the myths and misconceptions that have grown around it over the years. Looking at an IPv6 address can turn people off, too, because it requires a new way of understanding, saying, and memorizing network addresses. IPv4 addresses are easy to say and memorize because they use four decimal numbers separated by a “.”. Therefore, they can be said out loud using plain English, such as “one ninety eight dot one oh eight dot sixty dot one sixty eight” when referring to 198.108.60.168

In contrast, IPv6 uses hexadecimal notation, with four hexadecimal numbers conjoined in a group, with eight groups separated by a “:”, e.g., 2001:48a8:6880:60:889a:a6ff:2208:4165. No one would want to say this address out loud: it would take too long, and no one would be able to remember it. However, when someone is trained on IPv6, that person learns that the four groups to the left in yellow can be ignored for the most part because it represents the internet outside of the enterprise’s network. Furthermore, there are procedures for using the four rightmost groups in green that reduce the need to refer to all four groups, making referencing a particular address easier still. Just knowing these few facts can reduce people’s fear of using IPv6.


Partner With Us

Contact Merit Research

It appears your browser is blocking access to our web forms.
Please see this support article for more information.