Seamless Infrastructure independent Multi Homed NEMO Handoff Using Effective and Timely IEEE 802.21 MIH triggers

Handoff performance of NEMO BS protocol with existent improvement proposals is still not sufficient for real time and QoS-sensitive applications and further optimizations are needed. When dealing with single homed NEMO, handoff latency and packet loss become irreducible all optimizations included, so that it is impossible to meet requirements of the above applications. Then, How to combine the different Fast handoff approaches remains an open research issue and needs more investigation. In this paper, we propose a new Infrastructure independent handoff approach combining multihoming and intelligent Make-Before-Break Handoff. Based on required Handoff time estimation, L2 and L3 handoffs are initiated using effective and timely MIH triggers, reducing so the anticipation time and increasing the probability of prediction. We extend MIH services to provide tunnel establishment and switching before link break. Thus, the handoff is performed in background with no latency and no packet loss while pingpong scenario is almost avoided. In addition, our proposal saves cost and power consumption by optimizing the time of simultaneous use of multiple interfaces. We provide also NS2 simulation experiments identifying suitable parameter values used for estimation and validating the proposed mode

Analyzing challenging aspects of IPv6 over IPv4

The exponential expansion of the Internet has exhausted the IPv4 addresses provided by IANA. The new IP edition, i.e. IPv6 introduced by IETF with new features such as a simplified packet header, a greater address space, a different address sort, improved encryption, powerful section routing, and stronger QoS. ISPs are slowly seeking to migrate from current IPv4 physical networks to new generation IPv6 networks. ‎The move from actual IPv4 to software-based IPv6 is very sluggish, since billions of computers across the globe use IPv4 addresses. The configuration and actions of IP4 and IPv6 protocols are distinct. Direct correspondence between IPv4 and IPv6 is also not feasible. In terms of the incompatibility problems, all protocols can co-exist throughout the transformation for a few years. Compatibility, interoperability, and stability are key concerns between IP4 and IPv6 protocols. After the conversion of the network through an IPv6, the move causes several issues for ISPs. The key challenges faced by ISPs are packet traversing, routing scalability, performance reliability, and protection. Within this study, we meticulously analyzed a detailed overview of all aforementioned issues during switching into ipv6 network

A Survey on Handover Management in Mobility Architectures

This work presents a comprehensive and structured taxonomy of available techniques for managing the handover process in mobility architectures. Representative works from the existing literature have been divided into appropriate categories, based on their ability to support horizontal handovers, vertical handovers and multihoming. We describe approaches designed to work on the current Internet (i.e. IPv4-based networks), as well as those that have been devised for the "future" Internet (e.g. IPv6-based networks and extensions). Quantitative measures and qualitative indicators are also presented and used to evaluate and compare the examined approaches. This critical review provides some valuable guidelines and suggestions for designing and developing mobility architectures, including some practical expedients (e.g. those required in the current Internet environment), aimed to cope with the presence of NAT/firewalls and to provide support to legacy systems and several communication protocols working at the application layer

Analysis of BGP4 Peering Establishment Time on IPv6 Connection over 6PE and 6VPE

Nowadays, because of the exhaustion of IPv4 address space, IPv6 is increasingly being used on enterprise networks. Usually, an enterprise uses an MPLS network from a Service Provider to interconnect their IPv4 network sites. Although MPLS Service Providers mostly built their MPLS backbone based on IPv4, their MPLS backbone have the capability to transport IPv6 traffic of their customers. Two methods can be used by the MPLS Service Provider to connect its customer IPv6 network, which is 6PE (IPv6 Provider Edge Routers) and 6VPE (IPv6 VPN Provider Edge Router). Enterprises generally use a BGP routing protocol to interconnect their networks, and they need to use the best method that suits their requirement from their MPLS Service Provider to transport their IPv6 traffic (including the BGP protocol). The MPLS Service Providers need to consider the advantages and disadvantages of both methods. This paper illustrates the analysis of BGP4 (current BGP version) IPv6 peering establishment time over 6PE and 6VPE methods. The MPLS Service Providers can use the analysis results of this study to determine the suited method to interconnect its customers' IPv6 networks

Enhancing Capacity and Network Performance of Client-Server Architectures Using Mobile IPv6 Host-Based Network Protocol

A huge number of studies have been done supporting seamless mobility networks and mobile technologies over the years. The recent innovations in technology have unveiled another revolution from the static architectural approach to more dynamic and even mobile approaches for client-server networks. Due to the special equipments and infrastructure needed to support network mobility management, it is difficult to deploy such networks beyond the local network coverage without interruption of communications. Therefore, MIPv6 as developed by the Internet Engineering Task Force (IETF) and ancillary technologies were reviewed to provide clear insights on implementing MIPv6 in Client-Server architectures. However, MIPv6 technology presents weaknesses related to its critical handover latency which appears long for real-time applications such as Video Stream with potential loss of data packets during transmission

Enhancing Capacity and Network Performance of Client-Server Architectures Using Mobile IPv6 Host-Based Network Protocol

A huge number of studies have been done supporting seamless mobility networks and mobile technologies over the years The recent innovations in technology have unveiled another revolution from the static architectural approach to more dynamic and even mobile approaches for client-server networks Due to the special equipments and infrastructure needed to support network mobility management it is difficult to deploy such networks beyond the local network coverage without interruption of communications Therefore MIPv6 as developed by the Internet Engineering Task Force IETF and ancillary technologies were reviewed to provide clear insights on implementing MIPv6 in Client-Server architectures However MIPv6 technology presents weaknesses related to its critical handover latency which appears long for real-time applications such as Video Stream with potential loss of data packets during transmissio

An Empirical Study of the I2P Anonymity Network and its Censorship Resistance

Tor and I2P are well-known anonymity networks used by many individuals to protect their online privacy and anonymity. Tor's centralized directory services facilitate the understanding of the Tor network, as well as the measurement and visualization of its structure through the Tor Metrics project. In contrast, I2P does not rely on centralized directory servers, and thus obtaining a complete view of the network is challenging. In this work, we conduct an empirical study of the I2P network, in which we measure properties including population, churn rate, router type, and the geographic distribution of I2P peers. We find that there are currently around 32K active I2P peers in the network on a daily basis. Of these peers, 14K are located behind NAT or firewalls. Using the collected network data, we examine the blocking resistance of I2P against a censor that wants to prevent access to I2P using address-based blocking techniques. Despite the decentralized characteristics of I2P, we discover that a censor can block more than 95% of peer IP addresses known by a stable I2P client by operating only 10 routers in the network. This amounts to severe network impairment: a blocking rate of more than 70% is enough to cause significant latency in web browsing activities, while blocking more than 90% of peer IP addresses can make the network unusable. Finally, we discuss the security consequences of the network being blocked, and directions for potential approaches to make I2P more resistant to blocking.Comment: 14 pages, To appear in the 2018 Internet Measurement Conference (IMC'18