Mobile IPv6 Frequently Asked Questions

1. What customers' problem does this product solve?

HP-UX Mobile IPv6 allows Mobile Nodes to change network attachment points—

always remaining reachable and with no disruption in network connectivity—using a

single, fixed IPv6 address for extended periods of time. By handling mobility at the IP

layer, the only common layer for applications in IP networks, mobility is transparent

to the layers above the IP layer.

2. How does this product fit within customers' overall solution and topology?

This product actually consists of two Mobile IPv6 functions:

 Home Agent

 Correspondent Node

The Home Agent is for those customers who need to provide mobility service to

some Mobile Nodes that administratively belong to them (e.g. ISP mobility service

providers).

The Correspondent Node is for any IPv6 box owner who wants to provide

MIPv6’s route optimization support to Mobile Nodes that will communicate to the

IPv6 box. For example, a web server that provides location-sensitive contents to the

Mobile Nodes.

3. What is the product relationship between IPv6 and MobileIPv6?

The HP-UX Mobile IPv6 design and implementation took advantage of the IPv6

framework in the following manner:

IPv6 items leveraged by Mobile IPv6:

 Large address space to eliminate the need for private addresses and NATing.

 Leverages the AH and ESP IPv6 extension headers for security.

IPv6 items expanded for Mobile IPv6:

 Added a new IPv6 extension header (Mobility Header) for MIPv6 signaling

messages such as BU, BA, HoT, HoTi, CoT, CoTi, BRR, and BE.

 Expanded the IPv6 Destination Option to include a Home Address Option.

 Added a new Type 2 IPv6 Routing header for Route Optimization.

 Added additional ICMPv6 messages for Home Agent discovery request and

reply, and Prefix solictation and advertisement.

 Modified router advertisment messages to include Mobile IPv6 attributes.