Search

In the Identifier Locator Network Protocol (ILNP) networks, the existing mobility control schemes based on the centralized entity, called the Dynamic Domain Name Service (DDNS) server, such that all the control traffic is processed at the DDNS server. However, the centralized mobility schemes have significant limitations, such as control traffic overhead at the server and large handover delay. In order to resolve these issues, we propose a new mobility control scheme for ILNP networks, which manages the identifier-locators (ID-LOCs) in the fully distributed manner. In our scheme, each domain has a dedicated mobile DDNS (m-DDNS) server at the site border router (SBR). The m-DDNS server maintains two databases, i.e., home host register (HHR) and visiting host register (VHR), to support the roaming of mobile hosts. When a mobile host roams into a domain, the m-DDNS server in the visiting domain registers the host&rsquo, s ID-LOC in the VHR and requests the update of HHR to the m-DDNS server in the home domain. Since the m-DDNS servers communicate each other directly, the ID-LOC mappings are managed without involvement of any central entities. We analyzed our proposed mobility scheme via numerical analysis and compared its performance with those of existing schemes. Numerical results showed that our scheme outperforms the existing mobility control schemes substantially in terms of control traffic overhead at the servers, total transmission delay and handover delay.

Date of Acceptance: 14/07/2014 We present the first results of an implementation of IP-layer soft handoff, based on the Identifier Locator Network Protocol (ILNP). In our testbed experiments, we show minimal gratuitous packet loss in vertical handoff scenarios (WiFi-3G). Unlike the IETF Mobile IP proposals, the ILNP uses a purely end-to-end architecture, and does not require proxies, middleboxes or tunnelling to support mobility. Our testbed is based on an in-kernel implementation using a modified Linux IP stack. Postprint

We present an empirical evaluation of network-layer soft handoff for IP mobility. Such functionality is not currently available for Mobile IP. Our new approach, based on the Identifier Locator Network Protocol (ILNP), requires no additional network entities, such as proxies, and it does not require modification of any routing protocols. Only the communicating hosts need to have their end-system protocol stacks updated so it is incrementally deployable. In our performance evaluation, we find that soft handoff minimises packet loss, with the observed packet loss during handoff being no worse than the natural loss of the end-to-end path.

Wireless mobile devices are becoming increasingly prevalent in society. As a result, aggregation of network connectivity through the use of mobile networks is becoming increasingly relevant to service providers as well as for mobile users. The current approach being pursued within the IETF Mobile Extensions for IPv6 (MEXT) WG, is based on the Network Mobility (NEMO) architecture. NEMO uses IP-in-IP tunnelling for providing mobile network capability on an existing IPv6 network. This approach can result in non-optimal routing between source and destination nodes. Other proposals such as OptiNets extend NEMO and try to address issues such as sub-optimal routing. There are alternative approaches also being proposed, such as the Identifier Locator Network Protocol (ILNPv6), which is based on the use of naming, to enable a flexible and integrated mobile network capability based on IPv6.We have conducted a comparative analysis of the cost of providing optimal routing, in terms of packet and bandwidth overhead, based on an emulation, using data from the London Circle Line metropolitan railway as a scenario. Our analysis shows that these different approaches to mobility offer significantly different performance trade-offs in routing for mobile networks, depending on the constraints of the network scenario.

Site multi-homing is an important capability in modern military networks. Resilience of a site is greatly enhanced when it has multiple upstream connections to the Global Information Grid, including the global Internet. Similarly, the ability to provide traffic engineering for a site can be important in reducing delays and packet loss over low-bandwidth and/or high-delay uplinks. Current approaches to site multi-homing and site traffic engineering (a) require assistance from a trusted network service provider; (b) inject significant additional routing information into the global Internet routing system. This approach reduces flexibility, does not scale and is a widespread concern today. The proposed Identifier-Locator Network Protocol (ILNP) offers backward compatible extensions for IPv6 to enable a site to (a) use multiple routing prefixes concurrently, without needing to advertise these more-specific site prefixes upstream to the site's service providers; (b) enables edge-site controlled traffic engineering and localised addressing, without breaking end-to-end connectivity. This feature combination provides both multi-homing and traffic engineering capabilities without any adverse impact on the routing system and does not require anything more than unicast routing capability in the provider network. ILNP enables concurrent multi-path transmission for a flow, without requiring multicast routing, to increase flow resilience to path interruptions. This technique has a secondary security benefit of reducing the risk of an adversary successfully blocking an ILNP flow via a Denial-of-Service attack on any single path or single link.

At present, military communications within battlefields are very restricted, both by policy and due to technology limitations. In Southwest Asia today, there are needlessly long and complex communications paths, often involving multiple relays and use of constrained-bandwidth MILSATCOM back-haul outside the theatre, when nearby forces could communicate directly via existing interoperable radios. This is a current problem for NATO and Coalition forces. The current Internet Protocol suite lacks core support for mobility, scalable support for multi-homed nodes, and does not provide the capabilities needed for optimal communications in forward operating areas. We propose a coalition-based, multi-homed approach lever-aging both local-area and wide-area connectivity, improving both the flexibility and robustness of communication, without conflicting with the security policy of sensitive communication. The Coalition Peering Domain (CPD), is a distributed, self-configuring architecture that supports the secure, collaborative networking relationships needed to provide this flexibility and robustness. The CPD facilitates the inter-connection of cooperating, but administratively separate, network segments. The CPD exploits multi-homed and multi-path communication to better-utilise all available connectivity. The Identifier-Locator Network Protocol (ILNP) provides native support for improved scalability in multi-homing and mobility, while easing use of network layer security and allowing inter-operation across different administrative domains. Our approach is compatible with current work in Mobile Ad-Hoc Networking (MANET). ILNP has excellent compatibility with IPv6: existing IPv6 backbone networks do not require any modification to carry ILNP traffic natively. There are practical, realistic and deployable engineering solutions to realise the CPD and ILNP within the framework of IPv6.