Distributed Identifier-Locator Mapping Management in Mobile ILNP Networks

Abstract

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’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.

Mobile Oriented Future Internet (MOFI): Architectural Designs and Experimentations

“…In this work, the validity of the MOFI architecture is evaluated through the experimentations over the European Union (EU)-Korea testbed network. Reference [9] proposes an enhanced mobility management scheme in the ILNP-based mobile networks, in which the identifier-locators (ID-LOCs) mappings are managed in the fully distributed manner by using a mobile dynamic domain name system (m-DDNS) server located in each domain.…”