June 2004. He has been an eminent teacher and researcher in Computer Science and Engineering having made an excellent contribution towards Teaching and Research for nearly 11 years in so many engineering colleges in Davanagere, Bangalore and DoS in CS at Mysore. Currently he is Teacher Fellow at the Dept of P. G Studies and Research in Computer Science, from Mangalore University for his Ph. D in Computer Science under the supervision of Dr. Manjaiah. D. H on an area of Wired Networks and on the topic entitled “Investigations into the Design, Performance and Evaluation of a Novel IPv4/IPv6Transition Scenarios and also presently he is working as an Asst. Professor at DoS in Computer Science, Manasagangotri, Mysore. He has also co-authored more than 45 innovative technical papers out of which 32 in International Conferences, 9 in National Conferences and 4 papers in refereed International Journals. His prime area of research has been Computer networking, Protocol design, Network Protocols and Algorithms, Protocol performance issues, etc.
IPv6 has yet to become more than a worthy successor of IPv4, which remains, for now, the dominant Internet Protocol. This is due to the complicated transition period through which the Internet will have to go, until IPv6 will completely replace IPv4. One of the challenges introduced by this transition is to decide which technology is more feasible for a particular network scenario. To that end, this article proposes the IPv6 Network Evaluation Testbed (IPv6NET), a research project whose ultimate goal is to obtain feasibility data in order to formulate a coherent, scenario-based IPv6transition strategy. The paper presents the overview of IPv6NET, the testing methodology and empirical results for a specific network scenario. The presented empirical feasibility data includes network performance data such as latency, throughput, packet loss, and operational capability data, such as configuration, troubleshooting and applications capability.
The new Internet Protocol (IPv6) has been developed to replace the current Internet Protocol (IPv4) and the transition from IPv4 to IPv6 is a necessary process in the realization of global Internet. The development of IPv6 technology and continuous increases in application, but this process will take long time so a transition methods will be needed. There are many IPv4/IPv6transition methods already exist today, some of them applied in practice, the others still as proposed solutions. Tunneling and encapsulation methods are the most techniques that used until now, but all encapsulation mechanisms suffer from the increasing of the overhead traffic network as a result for either encapsulating IPv4 packet in the IPv6 packet or encapsulating IPv6 packet in the IPv4 packet. In this paper we proposed a system that make incompatible nodes; the first based IP4 the other based IPv6, communicate together without increasing packets size, this system is called Bi-Directional Transition System (BDTS). This system depends on understanding of the two environment of transmission , that is , received the source packet then converting the information header to be adaptable to the destination end. Our system has been implemented then we made a test by simulation tool called VMware ,during this simulation our system was studied in one scenario and the results shown that BDTS make two incomputable protocol hosts communicate together.
Tunneling: It enables IPv6 connectivity across an IPv4 network and vice versa. Tunneling operations include encapsulation, decapsulation, and tunnel endpoint signaling, with no upper layer operation required. Hardware can implement data forwarding at the network layer with line speed capacity. Although tunneling can’t achieve direct interworking between IPv4 and IPv6, we believe that broadly adopting it as the foundation for IPv6transition will accelerate IPv6 adoption, retain 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. Here, the project deals with a tunnel-based IPv6transition framework. Considering the diversity in network structure and functionality, the framework applies different tunneling mechanisms to backbone and access networks. Backbone networks must support both IPv4 and IPv6 connectivity for client networks even when the backbone is homogenous IPv4 or IPv6 .
This paper has proposed a 6in4 tunnel based IPv6transition solution for IPv4 mobile terminals, so that they can easily get access to IPv6. The solution proposed could also provide possible solution for telecom carriers who are eager to offer IPv6 services without much improvements or replacements done on their current system. It is unique for the fact that it aims at providing a suitable way for existing mobile terminals to migrate from IPv4 to IPv6. With the application software designed and implemented, IPv4 mobile terminals are able to reach IPv6 resources in the experimental environment. Moreover, host mobility has been taken into account, and mobile terminals can “stay on IPv6” when they move from one network to another, as long as the new IPv4 address assigned to them allows a new tunnel to be established. Qualitative and quantitative tests have proved the practical significance and effectiveness of the solution.
Abstract—IPv6 networks are rarely fully IPv6 from end to end particularly when interconnected over other providers core data networks, hence the need for IPv6transition methods or mechanisms. Previous studies have identified some potential impact on performance where transitions occur. This study considered implementations where Quality of Service (QoS) service policies have been applied in the IPv6 network to determine if the transition mechanisms were able to guarantee the same performance and level of service when the IPv6 traffic transitions over a core IPv4 network. Using a test lab, traffic generators and data capture tools the study was able to fully test the transition mechanisms using data rates and link speeds that replicated equipment and traffic levels used in real world implementations. The study showed that the Quality of Service classes applied were maintained across the transition network providing the service guarantees required for a range of traffic classes. Results indicated that the transition implementations on the devices used (Cisco ISR 4351) translate the QoS settings from IPv6 to IPV4 and vice versa were highly effective and with negligible additional impact on performance occurring due to the additional processing required.
The suite is designed to support several deployment models although we expect two of them to be preeminent: The first one is to allow the internal nodes of an IPv6-only stub network to reach the public IPv4 Internet. In this case the NAT64/DNS64 functions can be provided either by the IPv6 stub network itself or by its direct provider i.e. in a Carrier Grade NAT. In the second scenario, an IPv4-only stub site decides to give access to its IPv4-only servers to clients in the IPv6 Internet. For this, NAT64 can be provisioned by the IPv4 stub network. Because the DNS server of the IPv4 site is authoritative for the local data, the DNS64 function is replaced by a DNS server with AAAA RRs that contain the IPv6 representation of the IP addresses assigned to the IPv4- only servers.
The ISATAP address is made up of 24-bit EEE UI (00- 00-5E at a specific IPv4 address and 02-00-5E on IPv4 public address), and 8-bit hex value 0xFE made by EUI-64 format, and node IP-4 IP address can be found. In this way, the node creates an internal address of the city center, allowing it to reach other ISATAP isodas in that inner area. The ISATAP engine specifies that the multicast is not available on the IPv4 network, so it can identify possible routers. ISATAP hosted the navigation key, manually configured or using the DNS query, oratap.company.com (domain domain company.com). Computers for a router IPv4 address can handle a router application to obtain a global IPv6 address with the same 64-modified format of EU 64 described above. This allows the ISATAP processor to communicate with the IPv6 Internet.
In most cases, sites will start by making small portions of their internal networks IPv6-capable, so they can test various tools and configurations. Depending on a site’s performance and scalabil- ity requirements, providers can then extend the use of the technologies as they prove stable. ISA- TAP supports such an approach to introduction, letting developers overlay the IPv6 network on the existing IPv4 infrastructure. A site might also deploy an internal tunnel broker service for iso- lated (or remote) hosts wishing to use IPv6. A site can expect to receive a /48 prefix IPv6 address space from their ISP, and site developers can divide the space among various departments (perhaps with a /56 prefix), according to alloca- tion policies.
Numerous studies on the evaluation of IPv6transition mechanisms have been reported in the current literature. Shin et al.  showed the impact of IPv6transition mechanisms on user applications. Law et al. in  focused on the performance of dual-stack technologies in terms of various network metrics including network connec- tivity, hop-count, RTT, throughput, operating systems dependencies and the address configuration latency. The authors in   provided the evaluation of tunnel mechanisms with the key performance-related metrics in- cluding throughput, delay, jitter, and the CPU usage of transition nodes. AlJa’afreh et al.  gave the compa- rison between the tunneling process and mapping schemes for IPv4/IPv6transition using end-to-end delay and throughput as the key performance metrics. Guerin and Hosanagar  adopted a simple model to illustrate how the connectivity quality affects both IPv6 adoption and the volume of translation traffic, and summarize their implications for IPv6 adoption. The authors in  evaluated the dual-stack protocol and tunneling transition based on the metrics of throughput and round-trip delay. Several studies - presented the comparisons of translation mechanisms with the aspects of operation complexity and scalability, real-time communications, field device, multicast address, and application-layer protocol. The authors in  proposed the evaluation of the transition mechanisms including the estimation on the scalability, heterogeneous addressing and application- layer translation, hardware cost, performance and capacity of the equipment, security, end-to-end property, and the influence for developing applications.
ISATAP, refers to Intra-Site Automatic Tunnel Addressing Protocol; another IPv6transition mechanism for transmitting IPv6 packets over IPv4 network. The word "automatic" signifies that once an ISATAP server/router has been set up only the clients must be configured to connect to it. This solution enables enterprises to deploy a simple and manageable IPv6 within their infrastructure with little time and effort.Another advantage is that, within a site, usually only one ISATAP router is needed. The host/router functioning as an ISATAP server should be dualstack and have a connection to the IPv6 internet in order for it to become a gateway for all clients in the ISATAP subnet it serves.
In this era of Internet evolution, the transition from IPv4 to IPv6 has become inevitable and fairly urgent. Internet Assigned Numbers Authority (IANA) has finally exhausted the IPv4 global address space, which leaves the community no choice but to push forward the IPv6transition process. IPv4 and IPv6 networks both will exist during the transition period, while they were not compatible in nature with each other. Therefore it became necessary to maintain the availability, as well as to provide the inter-communication ability of IPv4 and IPv6. Years ago, a series of transition techniques were actually proposed. However because of some technical issues they failed to cover the solution space well. IPv6 mobility provides a mechanism for the host to roam around
It will be returned the right results as the two sides of NAT-PT gateway: the pure IPv4 network and pure IPv6 network. If one of the sides is double stack protocol or the two sides are double stack protocols, it will have to directly communicate through the NAT-PT gateway when the nodes are in the same protocol. Through the process of NAT – PT, it will have two times’ translation on the condition of non-need translation, then come back to the former translation. This kind of result not only decreases the communication efficiency but also wastes the relevant limited NAT-PT gateway resource. Therefore, when we use NAT-PT gateway under the complicated net circumstances, in some cases it will not only affect the gateway efficiency but also the realization of gateway function. In the view of the above problems, this paper modifies the treatment process of NAT-PT gateway communication, and puts forward the corresponding improvement plans.
337 593 543 950 336) times larger than the number of IPv4 addresses. The text form of the IPv6 address is xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx, where each x is a hexadecimal digit, representing 4 bits. Leading zeros can be omitted.
Some of the cloud-based solutions and applications for healthcare organizations are abstracted in this paper. Both large hospitals and small clinics can benefit from these solu- tions, not to mention all the other players in the healthcare industry. IPv6 is the critical backbone for the next generation technology. It holds tremendous promise; however, enterpris- es and businesses need to have a carefully planned evalua- tion and transition strategy for IPv6. Quick glances on necessi- ty, benefits of IPv6 over IPv4 and little compatibility mentioned in this paper. In future as per further development in IPv6 pro- tocol will take place and prove, this whole system can shifted on IPv6 network by step wise improvements.
scheme in IPv6 enables to allocate devices with globally unique IP addresses. This assures that mechanism to save IP addresses such as NAT is not required. So devices can send/receive data between each other, for example VoIP and/or any streaming media can be used much efficiently. Other fact is, the header is less loaded so routers can make forwarding decision and forward them as quickly as they arrive.
In ICMPv6 flooding attacks detection, behavioural-based approaches, particularly suffer from the unavailability of the benchmark datasets. This can lead to the lack of precise results evaluation of ICMPv6flooding attack detection systems, comparison, and deployment, which originates from the deficiency of adequate datasets. Most of the datasets in the IPv6 field are from local environment and cannot be used on a large scale due to privacy problems and do not reflect common trends. They also lack some statistical features. Therefore, there is not any available benchmark dataset infected by ICMPv6-based foods for performing a Denial of Service (DoS) attacks against Web servers by using ICMPv6 flooding method. In addition, there is no Web access log infected by ICMPv6-based flood available for researchers. This paper presents the ICMPv6-based flooding attacks testbed to study the behaviour of ICMPv6 flooding attack as well as evaluating different solutions proposed for detecting ICMPv6-based flood of DoS attacks by various researchers.
To make the deployment of IPv6 and DNSSEC easier, we designed a web-based system which named Auxiliary Deployment System for IPv6 and DNSSEC for pro- moters and any person who want to use these. This sys- tem is divided into a front-end and a back-end. At the front-end, users can see some information about IPv6 and DNSSEC including news, reports, and various statis- tics. In addition, users can also detect any domain name to determine whether it supports IPv6 or DNSSEC via complete detection or general detection that the users choose. At the back-end, an admin can manage any ser- vices of each organization and carry out some investiga- tion to improve system integrity and understand the needs of users. In addition to interaction with the users, the system also detects a task for service list every hour that is established by our crawler module.