[Abstract] Introduction
Internet Protocol version 6 (IPv6) is the next-generation Internet Protocol designated to be the successor to IPv4.
Though IPv4 has proven to be robust, easily implemented, interoperable, and has stood the test of scaling an internetwork to a global utility the size of today’s Internet, it has its own limitations.
This current version of the Internet Protocol, IPv4, has been in use for almost 30 years (started from 1981 with RFC 791) and exhibits significant challenges in supporting emerging demands for address space cardinality, high-density mobility, multimedia, and stronger security.
IPv6 – Why do we need it?
This section describes the impact of the imminent IPv4 address exhaustion on enterprises, why they should be concerned, and how they need to tackle it, using measures such as deploying IPv6.
The need for IPv6 has been building for a while now and basically arises due to the inherent limitations of IPv4. It is only due to the evolution of new technologies such as NATing and subnetting that has prolonged the inevitable. We assume that IPv6 will be deployed together with current IPv4 networks, so that the network engineering team will have to consider both the protocols.
Though IPv4 has proven to be robust, easily implemented and interoperable, the following are some of the limitations:
• IPv4 Addresses Exhaustion - IPv4 addresses have become relatively scarce due to ever increasing numbers of Internet-connected devices and appliances. The public IPv4 address space will eventually be depleted and new addresses will be available only when they have been recovered from previous use. While Network Address Translation (NAT) promotes the reuse of the private address space, they do not support standards-based network layer security or undertake mapping of all higher layer protocols. Thus creating problems when connecting two organizations, which use the private address space.
• Routing Scalability – There are routinely over 200,000 routes in the routing tables of Internet backbone routers, which are growing at alarming rates. The backbone routers’ routing tables must reflect information for every connected network in the world, and some experts have suggested that more than the issue of address shortage, the size of the non default routing tables will ultimately drive the acceptance of IPv6.
• IP Address translation – The nature of IPv4 raises challenges as the end-to-end nature of IP computing is broken when a system starts changing material as it passes between the nodes. There are reasonable workarounds for most applications, but security poses a problem because the Internet Security Protocol (IPSec) relies on the global uniqueness of the nodes’ IP addresses to ensure that packets are not spoofed. Additionally, not all applications can work around NATs.
• Simpler Configuration - Most current IPv4 implementations must be either manually configured or use an address configuration protocol such as Dynamic Host Configuration Protocol (DHCP). With more computers and devices using IP, there is a need for an easier and automatic configuration of addresses and other settings that do not rely on the administration of a DHCP infrastructure.
• Support for real-time delivery of data (QoS) - While standards for QoS exist for IPv4, real-time traffic support relies on the IPv4 Type of Service (TOS) field and the identification of the payload, typically using a UDP or TCP port. Unfortunately, the IPv4 TOS field has limited functionality. In addition, payload identification using a TCP and UDP port is not possible when the IPv4 packet payload is encrypted.
Other than these design issues there are following technical limitations in IPv4 as well,
• Operates on a best effort delivery model
• Does not guarantee delivery
• Does not assure proper sequencing
• Does not validate data integrity
These limitations have stimulated the development of IPv6, which is currently in the early stages of deployment, and is the only long-term solution.IPv6 is a solution for IP addressing space issue as it has 128-bit (16-byte) source and destination IP addresses.
IPv6 is getting more attention within the networking industry. Where only a few years ago there was widespread doubt as to whether IPv6 would ever be adopted, the meetings of network operators forums such as the North American Network Operators’ Group (NANOG), the Asia Pacific Regional Internet Conference on Operational Technologies (APRICOT) and Réseaux IP Européens (RIPE) now devote substantial portions of their agendas to discussions of how to best implement the new protocol.
Where a few years ago resistance to IPv6 centered on the lack of a business case, organizations worldwide are now devoting significant financial and engineering resources to IPv6 planning.
✥ 2725 The session begins by examining the current key drivers for IPv6, which includes
1. An explosion of Internet Applications, Games, Information Sources and Business transaction
2. Movement of traditional services such as voice and video from legacy circuit-based infrastructures to IP networks
3. Expanding economies in populous countries
✥ 2725 An overview of IPv6 deployment status around the world
✥ 2725 How to create a successful IPv6 Implementation Plan and Design
✥ 2725 Understanding the Inventory details of the Enterprise network
✥ 2725 The three different approaches to IPv6 Implementation
1. Core to Edge
2. Edge to Core
3. IPv6 Islands
✥ 2725 Design and Interoperability testing
✥ 2725 Different type of Implementation Mechanisms which includes
1. Dual Stack
2. Manually Configured Tunnels
3. Automatic Tunnels
4. Translators
✥ 2725 Cost and Risk Analysis
|
[Biography] Siva Sen (Sivaramakrishnan Senthatty) Graduate Engineer specialized in Electronics & communication with MS in Quality Management. He has over 20+ years of experience in IT Infrastructure specializing in Project Management, transformation & technical support of complex heterogeneous environments.
Current Role in TCS is Global Practice Director – IT IS Converged Network Practice Managing all Cisco – CoE, ALE- CoE, Avaya – CoE, Juniper CoE, in addition to the Practice role managing the Strategic outsourcing solution for Japan Market. Responsible for Go to Market strategy with all OEM’s.
Prior to TCS worked with Banking Captives and leading Outsourcing companies managed multiple service delivery centers.
|