TUNNEL-BASED IPV6 TRANSITION WITH AUTOMATIC BANDWIDTH MANAGEMENT

The Internet will soon be sailing in very rough as it is about to run out of the current Internet Protocol Version four (IPV4). Moving from Internet Protocol version Four (IPv4) to Internet Protocol version six (IPv6) is not straightforward because IPv4 and IPv6 are incompatible protocols. To enable the smooth transition between IPv4 and IPv6, several transition mechanisms have been proposed by IETF IPng Transition Working Group (NGTrans) such as Tunneling, dual stack, Translation. Tunneling supports ―like-to-like‖ IP connectivity across an ―unlike‖ network, whereas translation supports ―like-to-unlike‖ IP interconnectivity. No comprehensive strategy exists to address all possible scenarios. Because tunneling can keep the end-to-end model that the Internet is built on. Tunneling enables IPv6 connectivity across an IPv4 network and vice versa. Although tunneling can’t achieve direct interworking between IPv4 and IPv6, but broadly adopting it as the foundation for IPv6 transition will accelerate IPv6 adoption, and retain the legacy IPv4 connectivity, and let operators leverage their existing IPv4 assets during the transition period. The key concern is that tunneling retains the end-to-end notion and IP like-to-like affinity on which the Internet is built. Bandwidth allocation is an important factor to be considered in networking. Efficient bandwidth management technique is important in satisfying the requested services. In this project, the emphasis is laid on developing a tunnel-based framework that solves the transition problems in backbone and allocation of bandwidth efficiently by allocating the requested bandwidth as per the demand.