Empirical Measuring IPv4/IPv6 Network Performance on Microsoft Windows Operating Systems

Author(s):  
Shibendu Debbarma ◽  
Abhijit Das
2019 ◽  
Vol 3 (1) ◽  
pp. 4 ◽  
Author(s):  
Babu R. Dawadi ◽  
Danda B. Rawat ◽  
Shashidhar R. Joshi ◽  
Daya S. Baral

The software defined networking (SDN) paradigm with enhanced features of IPv6 offers flexible network management and better network visibility for enhancing overall network performance, network manageability, and security. Thus, along with the IPv6 network deployment worldwide, SDN migration has emerged worldwide, but network service providers suffer from different issues when migrating their existing legacy network into operable SDN and IPv6 enabled networks. In this paper, we investigate the affordability of broadband network services for the rural communities in the context of information and communication technology (ICT) infrastructure deployment throughout Nepal. During the phase of network transformation, it will be more challenging for the service providers of Nepal to have a proper choice of technologies to expand the network while considering the proper policy formulation, affordability, need of skilled human resources, deployment cost, and many other aspects. We also present the service provider affordability via energy optimization in software defined IPv6 network (SoDIP6) implementation that contributes to a reduction in organizational operational expenditure (OpEX). We perform an experimental analysis over an SoDIP6 network testbed and present a comparison of the annual energy and OpEX savings for network service providers. Our empirical analysis shows that an energy saving of 31.50% on switches and 55.44% on links can be achieved with an SoDIP6 network compared to a network with legacy devices and network management. Optimization on service provider network operational cost leads to sustainability and affordable services to both customers and service providers


Author(s):  
Neha Jain ◽  
Ashish Payal ◽  
Aarti Jain

With IPv4 addresses being exhausted, network engineers and researchers are encouraged to adopt IPv6. But before using the IPv6 network directly, engineers need to test their hardware and network performance under new conditions of IPv6 as it has an extended address, high complexity, overhead performance, and IPsec complications. As routing protocols play a crucial role in network performance, it leads to a network’s extended performance by finding the shortest path, good throughput, and lowest delay. As the specifications, viz. frame structure for IPv4 and IPv6 are entirely different, there are modified routing protocols specified for IPv6. Routing Information Protocol (RIP) and Routing Information Protocol Next Generation (RIPng) are distance vector routing protocols and use hop count as a cost. In this paper, we have used RIPng on the IPv6 addressing network and RIP on the IPv4 addressing network and then analyze and compare them on the basis of different performance parameters. For this comparison, three different applications – File Transfer Protocol (FTP), DB Query (DataBase), and electronic mail (e-mail) – are set on a network consisting of three different subnets, each having a diverse network topology. The performance parameters analyzed are global and object statistics, viz. ethernet delay, number of hops, applications response time, background traffic delay, traffic dropped, point-to-point links throughput, links utilization, and links queuing delay. The experimental results determine the strength of the routing protocols. Thus, the quantitative results give the option to choose the routing protocol according to the network scenarios. In terms of ethernet delay, traffic dropped, network convergence, and security, it is found that the RIPng_IPv6 network performs better than RIP_IPv4. RIPng_IPv6 has an ethernet delay of 2.9 milliseconds, traffic dropped of 0.29 packets/second, and network convergence of 17 seconds less than RIP_IPv4 values. However, the RIP_IPv4 network is scalable, uses less hop, and has 40 milliseconds of traffic delay, while RIPng_IPv6 has 0.40 seconds of traffic delay. RIP_IPv4 also has a better response time for all three applications, FTP as 100 milliseconds, DB as 40 milliseconds, and e-mail as 20 milliseconds which is much less than the values obtained for RIPng_IPv6 network. Therefore, according to the performance requirements, the network engineers/operators or researchers can use either the existing IPv4 network or a new IPv6 network to achieve the Quality of Service (QoS) target level.


Sign in / Sign up

Export Citation Format

Share Document