The Internet Protocol Version 4 (IPv4) that supports all communications on the Internet today provides the world with a maximum of about four billion IP addresses, a limitation that is rapidly becoming a barrier to Internet growth. The new version of the protocol, IPv6, is designed to alleviate this IP address shortage and also provide enhancements that boost end-to-end performance and buttress peer-to-peer security, as well as offer stronger support for auto configuration, multicast traffic and advanced collaboration features. One of the most significant drivers for IPv6 implementation is its ability to support converged voice, data and video on a single network, accessible through a single device.

The Office of Management and Budget has ordered agencies to convert their network backbones to IPv6 by June 30, 2008. According to the Federal CIO Council Architecture and Infrastructure Committee’s IPv6 Transition guidelines, IPv6 does not have to be fully operational by that date. Network backbones, however, must be ready to pass IPv6 traffic and support IPv6 addresses, and agencies have to be able to verify the new capability and maintain security during and after adoption of IPv6. That means any new networking purchases should be compatible with the new IP version.

IPv6 Security Concerns
Networking experts cite security as a major concern in transitioning to IPv6. This is primarily because the infrastructure and applications that support the new version may be open to a range of attacks and vulnerabilities that had formerly been addressed in the IPv4 network. In addition, as agencies transition to IPv6 they may very well need to accommodate both the old and new IP versions. Yet dual environments are more vulnerable to attack. For instance, tunneling that involves encapsulating one version’s packets inside the other’s can invite hacker exploits. Dual stacks can also be susceptible to malicious activities.

3Com’s IPv6 Migration Strategy
3Com is well on the way to transitioning to IPv6 as part of a comprehensive three-phase migration strategy.

• Phase 1: This phase provides for mixed IPv6 and IPv4 networks that are capable of identifying, classifying and containing IPv6 traffic. 3Com solutions also provide organizations with the ability to run experimental or trial IPv6 devices.
• Phase 2: This phase enables IPv6 managed networks that provide support for IPv6 application and management control, using either application modules or host CPUs. As IPv6 becomes established in the network core, all the devices—including access layer switches—will be managed using IPv6 protocols.
• Phase 3: This final phase will implement full native IPv6 routing that includes running IPv6 routing and associated protocols in the network’s access layer switches.