In some Mobile IPv6 deployments, identifying the mobile node or the mobility service subscriber is not enough to distinguish between multiple services possibly provisioned to the said mobile node and its mobility service subscription. A capability to specify different services in addition to the mobile node identity can be leveraged to provide flexibility for mobility service providers on provi...

We present a framework for IPv6 mobility support in Cluster Based Heterogeneous Wireless Mesh Networks. The framework inherits the design and the features from the trendy Proxy Mobile IPv6 (PMIPv6) which can provide network-based mobility to Mobile Nodes having standard IPv6 stack. Design and implementation details are described. We also present a virtualization method using User-mode Linux and...

A Mobile IPv6 node requires a Home Agent address, a home address, and IPsec security associations with its Home Agent before it can start utilizing Mobile IPv6 service. RFC 3775 requires that some or all of these are statically configured. This document defines how a Mobile IPv6 node can bootstrap this information from non-topological information and security credentials pre-configured on the M...

Large Proxy Mobile IPv6 deployments would benefit from a functionality where a Mobile Access Gateway could dynamically discover a Local Mobility Anchor for a Mobile Node attaching to a Proxy Mobile IPv6 domain. The purpose of the dynamic discovery functionality is to reduce the amount of static configuration in the Mobile Access Gateway. This document describes several possible dynamic Local Mo...

The process that mobile node still maintains its connectivity when moved from one access router (AR) to another access router is called handover. The handover technology is one of the most important technologies for the quality of real-time operation. In order to reduce the handover delay. Fast Mobile IPv6 (FMIPv6), Hierarchical Mobile IPv6 (HMIPv6) and Fast Hierarchical Mobile IPv6 are studied...

Mobile IPv6 (MIPv6) defines a new Mobility header that is used by mobile nodes, correspondent nodes, and home agents in all messaging related to the creation and management of bindings. Mobile IPv6 nodes need the capability to identify themselves using an identity other than the default home IP address. Some examples of identifiers include Network Access Identifier (NAI), Fully Qualified Domain...

This letter proposes a new mechanism for network configuration on a mobile device that provides Point of Attachment (PoA) specific information using IEEE 802.21 and DHCP before moving to a new PoA. This allows the mobile device to prepare for intelligent handover decision either stateless address configuration or stateful address configuration when entering an IPv6 network. It allows the mobile...

The current design of Mobile IPv4 and Mobile IPv6 protocols doesn’t provide the compatibility between networks of different versions. A Network Mobility(NEMO) protocol also provides the limited mobility in IPv6 networks. However, we can easily expect that the current IPv4 network will coexist with IPv6 network in the near future internet environment. So, in this paper, we propose the architectu...

This document specifies the operation of the IPv6 Internet with mobile computers. Each mobile node is always identified by its home address, regardless of its current point of attachment to the Internet. While situated away from its home, a mobile node is also associated with a care-of address, which provides information about the mobile node’s current location. IPv6 packets addressed to a mobi...

Although Mobile IPv6 allows maintaining transport layer connections alive when an IPv6 node roams to different access networks, certain enabling mechanisms are needed for it to work in large scale network scenarios, including, most notably, issues with Mobile IPv6 bootstrapping and firewall traversal. This paper tries to address these problems by extending the IETF PANA and NSIS protocols to fo...