Comparative Evaluation of Host-Based Translator Mechanisms for IPv4-IPv6 Communication Performance Analysis With Different Routing Protocols

Comparative Evaluation of Host-Based Translator Mechanisms for IPv4-IPv6 Communication Performance Analysis With Different Routing Protocols

Ala Hamarsheh, Ahmad Alqeerm, Iman Akour, Mohammad Alauthman, Amjad Aldweesh, Ali Mohd Ali, Ammar Almomani, Someah Alangari
Copyright: © 2023 |Pages: 26
DOI: 10.4018/IJCAC.332765
Article PDF Download
Open access articles are freely available for download

Abstract

The impending exhaustion of internet protocol (IP) version four (IPv4) addresses necessitates a transition to the more expansive IP version six (IPv6) protocol. However, this shift faces challenges due to the widespread legacy of IPv4 infrastructure and resistance among organizations to overhaul networks. Host-based translators offer a critical bridging solution by enabling IPv6-only devices to communicate with IPv4-only devices through software-level protocol translation. This paper comprehensively evaluates four pivotal host-based translator mechanisms—bump-in-the-stack (BIS), bump-in-the-application programming interface (API) (BIA), BIA version 2 (BIAv2), and bump-in-the-host (BIH). Using simulated networks with diverse configurations of IPv4/IPv6 applications, hosts, and routing protocols, the authors assessed performance through metrics including packet loss, convergence time, traffic throughput, and overhead. The results reveal variability in effectiveness across both translators and scenarios. BIAv2 demonstrated advantages in throughput and overhead due to stateless mapping. The research underscores the importance of selecting the optimal translation approach for specific network environments and goals. It guides smoother IPv6 adoption by demonstrating how host-based translators can facilitate coexistence during transition. Further exploration of performance tradeoffs can continue guiding effective deployment strategies.
Article Preview
Top

Introduction

For more than 30 years, the internet protocol (IP) version four (IPv4) has been the cornerstone of the internet. However, the limited number of accessible IPv4 addresses has become a serious concern as more devices connect to the internet. This issue created the IP version six (IPv6) protocol, which provides a significantly bigger address space. Despite its benefits, IPv6 adoption has been delayed due to several problems. These include the need for IPv4 compatibility, the high expense of updating existing infrastructure, and the lack of IPv6 functionality in specific network devices. The internet's fast expansion and the rising number of connected devices have depleted IPv4 addresses. Each device needs a unique IP address to interact with other devices, but the present IPv4 address space can only allow around 4.3 billion distinct addresses, which is inadequate to meet the increasing demand. Furthermore, some corporations have been collecting IPv4 addresses, exacerbating the scarcity. Figure 1 shows the current status of available IPv4 addresses (Hamarsheh & Eleyat, 2018; Hamarsheh & Goossens, 2014; Hamarsheh et al., 2012).

It was first expected that everyone participating in the internet would happily shift to IPv6. However, this assumption proved fairly foolish. It is now commonly acknowledged that human and business considerations were undervalued, hindering a spontaneous move to IPv6. Two key stakeholders are involved in the transition: network providers and end customers. IPv6 primarily helps network providers, whereas end users may gain only indirectly from enhanced network functioning. As a result, it is doubtful that most end users will be strongly motivated to migrate to IPv6. While network providers may profit, their desire to move still depends on their end users. This results in a deadlock: commercial network providers are unlikely to compel users to move against their will. As a result, the key to a successful IPv6 transition is to make it smooth and invisible to end users. Most end users are unconcerned with the network layer and do not care if their programs utilize IPv4 or IPv6. Although end users may be unmotivated to transfer, most would not object to the shift as long as they could continue utilizing their existing apps (Hamarsheh, 2019; Hamarsheh et al., 2011a).

Figure 1.

The current state of available IPv4 addresses

IJCAC.332765.f01

Changing from IPv4 to IPv6 on the IP layer may first appear to not affect programs. However, this is not the case. Applications need IP addresses to communicate; therefore, when using IPv6, they must be able to handle longer IPv6 addresses. It is unrealistic to anticipate that all apps will be upgraded to be IPv6 compliant. While many common internet apps, such as web browsers and email clients, now support IPv6, hundreds of others may not be ready for the switch. Since many of these programs are created by tiny businesses or even one person, IPv6 compatibility upgrades may not always be a top concern, particularly for programs that solely utilize the internet to perform operations like registering or checking for updates. For this reason, it is likely that many apps will not be changed to be IPv6 compatible until IPv6 use is more commonplace. However, it cannot be expected that all end users would upgrade their software following new versions of these apps with IPv6 functionality. Not all users may be able or willing to update software since it might be difficult and time-consuming. To lessen the effect on end users' experiences and promote a more seamless adoption of the new protocol, it is crucial to make the switch to IPv6 as transparent as possible (Hamarsheh & AbdAlaziz, 2019).

Complete Article List

Search this Journal:
Reset
Volume 14: 1 Issue (2024)
Volume 13: 1 Issue (2023)
Volume 12: 4 Issues (2022): 2 Released, 2 Forthcoming
Volume 11: 4 Issues (2021)
Volume 10: 4 Issues (2020)
Volume 9: 4 Issues (2019)
Volume 8: 4 Issues (2018)
Volume 7: 4 Issues (2017)
Volume 6: 4 Issues (2016)
Volume 5: 4 Issues (2015)
Volume 4: 4 Issues (2014)
Volume 3: 4 Issues (2013)
Volume 2: 4 Issues (2012)
Volume 1: 4 Issues (2011)
View Complete Journal Contents Listing