The mobility agent software incorporates home agent and foreign agent functionality. The Solaris Mobile IP software does not provide a client mobile node. Only the agent functionality is provided. Each network with mobility support should have at least one static (non-mobile) host running this software. The following RFC functions are supported in the Solaris implementation of Mobile IP:
Address Allocation for Private Internets
(Agent only) IP Mobility Support
IP Encapsulation within IP
Mobile IP Network Access Identifier Extension for IPv4
The base Mobile IP protocol (RFC 2002) does not address the problem of scalable key distribution and treats key distribution as an orthogonal issue. The Solaris Mobile IP software utilizes only manually configured keys, specified in a configuration file.
The functionality in the following IETF drafts are also supported in the Solaris implementation of Mobile IP:
draft-ietf-mobileip-rfc2002–bis-03.txt – IP Mobility Support for IPv4, revised
draft-ietf-mobileip-challenge-13.txt – Mobile IP Challenge/Response Extensions
draft-ietf-mobileip-vendor-ext-09.txt – Mobile IP Vendor/Organization-Specific Extensions
draft-ietf-mobileip-rfc2344-bis-03.txt – Reverse Tunneling for Mobile IP
The following RFC functions are not supported in the Solaris implementation of Mobile IP:
General Routing Encapsulation
General Routing Encapsulation
Minimal Encapsulation Within IP
The following functions are not supported in the Solaris implementation of Mobile IP:
The forwarding of multicast or broadcast traffic to a mobile node visiting a foreign network
The routing of broadcast datagrams through reverse tunnels
Private care-of addresses or private home agent addresses
See mipagent(1M) man page for additional information.