{'fraction_non_alphanumeric': 0.015182186234817813, 'fraction_numerical': 0.0, 'mean_word_length': 5.067484662576687, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Mobility Management in HIMALIS Architecture

Mobility is not natively supported in the current Internet because it uses IP addresses as host or session identifiers in the transport and application layers and as locators in the network layer. In the mobile networking environment, a host should be able to change its locator when it moves from one network to another, while keeping the host or session ID fixed. Thus, to provide inherent mobility support in the future Internet, which we call the New Generation Network, we propose HIMALIS (Heterogeneity Inclusion and Mobility Adaptation through Locator ID Separation) architecture. HIMALIS uses separate namespaces for host IDs and locators. It includes a new naming scheme for generating host names and IDs. It uses a logical control network to store and distribute bindings among host names, IDs and locators for supporting mobility. We verify the basic functions of the architecture by implementing and testing it in a testbed system.