"Mobility Support in IPv6", Dave Johnson, Charles Perkins, Jari Arkko, 05-Jul-02. ( bytes)

This document specifies how the IPv6 Internet operates with mobile computers. Without specific support for mobility in IPv6 [11], packets destined to a mobile node would not be able to reach it while the mobile node is away from its home link. In order to continue communication in spite of its movement, a mobile node could change its IP address each time it moves to a new link, but the mobile node would then not be able to maintain transport and higher-layer connections when it changes location. Mobility support in IPv6 is particularly important, as mobile computers are likely to account for a majority or at least a substantial fraction of the population of the Internet during the lifetime of IPv6. The protocol defined in this document, known as Mobile IPv6, allows a mobile node to move from one link to another without changing the mobile node's IP address. A mobile node is always addressable by its 'home address', an IP address assigned to the mobile node within its home subnet prefix on its home link. Packets may be routed to the mobile node using this address regardless of the mobile node's current point of attachment to the Internet. The mobile node may also continue to communicate with other nodes (stationary or mobile) after moving to a new link. The movement of a mobile node away from its home link is thus transparent to transport and higher-layer protocols and applications.

"Mobile IPv4 Regional Registration", Pat Calhoun, Gabriel Montenegro, Charles Perkins, 07-Mar-02. ( bytes)

Using Mobile IP, a mobile node registers with its home agent each time it changes care-of address. If the distance between the visited network and the home network of the mobile node is large, the signaling delay for these registrations may be long. We propose a new kind of 'regional' registration, i.e., registration local to the visited domain. Regional registrations reduce the number of signaling messages to the home network, and reduce the signaling delay when a mobile node moves from one foreign agent to another, within the same visited domain.

"AAA Registration Keys for Mobile IP", Charles Perkins, Pat Calhoun, 07-Mar-02. ( bytes)

AAA servers, such as RADIUS and DIAMETER, are in use within the Internet today to provide authentication and authorization services for dial-up computers. Mobile IP requires strong authentication between the mobile node and its home agent. When the mobile node shares a security association with its home AAA server, however, it is possible to use that security association to create derivative security associations between the mobile node and its home agent, and again between the mobile node and the foreign agent currently offering connectivity to the mobile node. This document specifies extensions to the Mobile IP Registration Reply packet that can be used to create such security information at the mobile node.

"Hierarchical MIPv6 mobility management (HMIPv6)", Hesham Soliman, Claude Castelluccia, Karim Malki, Ludovic Bellier, 05-Jul-02. ( bytes)

This draft introduces some extensions for MIPv6 and neighbour discovery to allow for the introduction of a hierarchical MIPv6 mobility management model. The proposed hierarchical mobility management for MIPv6 will reduce the amount of signalling to CNs and the HA and may also improve the performance of MIPv6 in terms of handoff speed. Moreover, HMIPv6 is well-suited to implement access control and handoffs between different access technologies.

"Fast Handovers for Mobile IPv6", Goral Dommety, 01-Oct-02. ( bytes)

Mobile IPv6 describes how a Mobile Node can maintain connectivity to the Internet when it changes its Access Router for another, a process referred to as handover. During this process, there is a time period when the Mobile Node is unable to send or receive IPv6 packets both due to link switching delay and IP protocol operations. This time period is referred to as handover latency. In many instances, the handover latency resulting from standard Mobile IPv6 handover procedures could be greater than what is acceptable to support real-time or delay sensitive traffic. Furthermore, reducing the handover latency could be beneficial to non real-time, throughput-sensitive applications as well. The intent of this document is to describe protocol enhancements to reduce handover latency due to IP protocol operations as small as possible in comparison to the inevitable link switching latency.

"Low latency Handoffs in Mobile IPv4", Karim Malki, 01-Jul-02. ( bytes)

Mobile IPv4 describes how a Mobile Node can perform IP-layer handoffs between subnets served by different Foreign Agents. In certain cases, the latency involved in these handoffs can be above the threshold required for the support of delay-sensitive or real-time services. The aim of this document is to present two methods to achieve low- latency Mobile IP handoffs. In addition, a combination of these two methods is described. The described techniques allow greater support for real-time services on a Mobile IPv4 network by minimising the period of time when a Mobile Node is unable to send or receive IP packets due to the delay in the Mobile IP Registration process.

"Registration Revocation in Mobile IPv4", Steven Glass, M Chandra, 12-Sep-02. ( bytes)

This document defines a Mobile IPv4 Registration Revocation mechanism whereby either mobility agent participating in providing Mobile IP services to the same mobile node can notify the other mobility agent (or co-located mobile node) of the termination of either a single, or multiple mobility bindings, and for this notification to be acknowledged. Furthermore, if desired, a signaling mechanism already defined by the base Mobile IP protocol [1] is leveraged as a way to inform the mobile node of the revocation of this binding.

"Requirements of a QoS Solution for Mobile IP", Hemant Chaskar, 30-Jul-02. ( bytes)

Mobile IP ensures correct routing of packets to mobile node as the mobile node changes its point of attachment to the Internet. However, it is also required to provide proper QoS forwarding treatment to mobile node's packet stream at the intermediate nodes in the network, so that QoS-sensitive IP services can be supported over Mobile IP. This document describes requirements for an IP QoS mechanism for its satisfactory operation with Mobile IP.

"The Definitions of Managed Objects for IP Mobility Support using SMIv2, revised", Ravindra Rathi, 04-Sep-02. ( bytes)

This memo defines the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it describes managed objects used for managing the Mobile Node, Foreign Agent and Home Agent of the Mobile IP Protocol. This memo is intended to update and possibly obsolete RFC 2006, however, it is designed to be backward compatible.

"Localized Mobility Management Requirements", Carl Williams, 03-Jul-02. ( bytes)

This document describes requirements for Localized Mobility Management (LMM) for Mobile IP and Mobile Ipv6 protocols. These requirements are intended to guide the design of a protocol specification for LMM. Localized Mobility Management, in general, introduces enhancements to Mobile IPv4 and Mobile IPv6 to reduce the amount of latency in binding updates sent to the Home Agent and, for route-optimization, Correspondent Nodes, upon Care of Address change. In addition, LMM seeks to reduce the amount of signaling over the global Internet when a mobile node traverses within a defined local domain. The identified requirements are essential for localized mobility management functionality. They are intended to be used as a guide for analysis on the observed benefits over the identified requirements for architecting and deploying LMM schemes.

"Mobile IPv4 Challenge/Response Extensions", Charles Perkins, Pat Calhoun, 22-May-02. ( bytes)

Mobile IP, as originally specified, defines an authentication extension (the Mobile-Foreign Authentication extension) by which a mobile node can authenticate itself to a foreign agent. Unfortunately, this extension does not provide ironclad replay protection for the foreign agent, and does not allow for the use of existing techniques (such as CHAP) for authenticating portable computer devices. In this specification, we define extensions for the Mobile IP Agent Advertisements and the Registration Request that allow a foreign agent to use a challenge/response mechanism to authenticate the mobile node.

"Mobile IP NAT/NAPT Traversal using UDP Tunnelling", O Levkowetz, Sami Vaarala, 27-Sep-02. ( bytes)

Mobile IP's datagram tunnelling is incompatible with Network Address Translation (NAT). This document presents extensions to the Mobile IP protocol and a tunnelling method which permits mobile nodes using Mobile IP to operate in private address networks which are separated from the public internet by NAT devices. The NAT traversal is based on using the Mobile IP Home Agent UDP port for encapsulated data traffic.

"Nonfinal Mobility Header for Mobile IPv6", Charles Perkins, Francis Dupont, 15-Apr-02. ( bytes)

This document specifies operations to allow inclusion of data along with a mobility header (from Mobile IPv6) containing a Binding Update or Binding Acknowledgement message. In this way, smoother handovers and reduced jitter and bandwidth utilization can be achieved. Interactions with IPsec-based verification of mobility messages are described; basically, establishment of such IPsec-based methods preclude the use of the mobility header specified in this document, unless simple modifications to IPsec (outside the scope of this document) can be utilized.

"AAA NAI for Mobile IPv4 Extension", Fredrik Johansson, Tony Johansson, 30-May-02. ( bytes)

When a mobile node moves between two foreign networks it has to be reauthenticated. If the home network has multiple AAA servers the reauthentication request may not be received by the same AAAH as previous authentication requests. In order for the new AAAH to be able to forward the request to the correct HA it has to know the identity of the HA. This document defines an extension that enables the HA to pass its identity to the mobile node which can in turn pass it to the AAA server when changing point of attachment. This document specifies a NAI extension that can carry these NAIs.

"Problem Statement and Requirements for Mobile IPv4 Traversal Across IPsec-based VPN Gateways", Alpesh Patel, 27-Aug-02. ( bytes)

Mobile IP [1] agents are being deployed in enterprise networks, to enable mobile users with network mobility across wired and wireless LANs while roaming inside the enterprise firewall. With the growing deployment of multi-subnetted IEEE 802.11 networks (referred as hot spots) in public places such as hotels, airports, and convention centers, and wireless WAN data networks such as GPRS, the need for enabling mobile users to maintain their transport connections and constant reachability while connecting back to their target 'home' networks protected by Virtual Private Network (VPN) technology is increasing. This implies that Mobile IP and VPN technologies have to coexist and co-function in order to provide mobility and security to the enterprise mobile users. The goal of this draft is threefold. The first is to describe possible deployment scenarios for Mobile IP and VPN in enterprise and operator environments. The second is to identify example usage scenarios for enterprise users roaming outside the 'home' network (e.g., corporate Intranet), and articulate the problems resulting from Mobile IP and VPN coexistence. The third is to specify a set of framework requirements to evaluate proposed solutions, supporting multi- vendor seamless IPv4 mobility across IPsec-based VPN Gateways. Hereafter, a 'VPN' term in this draft refers to an IPsec-based VPN Gateway.

"Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents", Jari Arkko, Vijay Devarapalli, Francis Dupont, 20-Sep-02. ( bytes)

Mobile IPv6 uses IPsec to protect signaling between the home agent and the mobile node. Mobile IPv6 base document defines the main requirements these nodes must follow. This draft discusses these requirements in more depth, illustrates the used packet formats, describes suitable configuration procedures, and shows how implementations can process the packets in the right order.

Return to Internet-Draft directory.

Return to IETF home page.