IPv6 is the next generation internet protocol, designed at the IETF and defined in RFC 2460 in 1998. The goals of the new protocol were to provide expanded addressing capabilities with simple headers and provide direct support for features like address auto-configuration, prioritization via flow labels, security etc, to make for a better internet layer protocol.
By increasing the address field from 32 to 128 bytes, IPv6 offers the biggest advantage of large address space. As mobile devices and embedded devices proliferate, it is possible to interconnect more devices over the internet than ever before. The address space available with IPv6 seems to be adequate for a significant part of the conceivable future.
The header simplification and improved options processing, makes it easier for intermediate routers to forward IPv6 packets. Traffic flow identification to allow prioritization of different flows and handle them differently has been inbuilt into the protocol as has been the support for security via usage of IPSec.
In order to route IPv6, the routing protocols require upgrade and we have versions of OSPFv3, RIP-NG and enhanced BGP available.
Although the protocol supports auto-configuration via route-advertisements to the nearest router at startup (the address can be divided into a network specific portion that can be provided by the router and a host specific portion that is dependent on the MAC of the datalink interface on the host), support for DHCPv6 is also available to distribute addresses from a preconfigured pool.
Transitioning a network from IPv4 to IPv6 is not a simple job, even with small LANs – the complexity grows for larger network (enterprise-wide or ISP networks). The first issue is to obtain IPv6-ready hardware (ie) deploy hosts, routers and switches that have IPv6 implemented, even if the current network runs on IPv4. This can easily be done as part of the normal upgrade cycle for any organization (hence we find mandates for suppliers of network and host hardware/software to provide support for IPv6 as a criteria for purchase for the last few years). However, since IPv6 is yet to see large scale deployment, the extent of support and interoperability across vendors has to be tested in lab scenarios before live network deployments. For instance, certain network management features that are taken for granted with the current IPv4 systems, are not yet supported by all IPv6 implementations.
As the deployment level of IPv6 on the internet is not yet very significant, the current implementations are yet to undergo the test of time. The CAIDA (Co-operative Association for Internet Data Analysis) charts for the comparison of IPv4 and IPv6 deployment indicate very sparse usage currently for IPv6, although it is expected to pick up with the APAC countries leading the deployment.
At the application level, rewriting the application to use the underlying IPv6 infrastructure is necessary and hence the upgrade is an expensive process. Over time we see many product vendors announcing support for IPv6 and many standard applications today can run over IPv6 with configuration changes.
Transition technologies to ease IPv6 deployment have been in vogue as it is envisaged that IPv6 deployment is likely to grow only in pockets while the main internet backbones continue to run on Ipv4 for a long time. Some of the transition technologies have been controversial and these continue to evolve over time.
The v6ops work group at IETF continues to focus on operational issues with Ipv6 and current items for standardization include Ipv6 CPE routers and issues with router advertisements
As Ipv4 address exhaustion looms before us with a projected date early in the next decade , it is necessary for all technologists involved with IP networks and applications that run over IP to understand IPv6 and prepare for its deployment.
Wikipedia reference: IPv6