Overview of the Solaris Mobile IP Implementation

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:

RFC 1918

Address Allocation for Private Internets

RFC 2002

(Agent only) IP Mobility Support

RFC 2003

IP Encapsulation Within IP

RFC 2794

Mobile IP Network Access Identifier Extension for IPv4

RFC 3012

Mobile IP Challenge/Response Extensions

RFC 3024

Reverse Tunneling for Mobile IP

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 is 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-vendor-ext-09.txt – Mobile IP Vendor/Organization-Specific Extensions

The following RFC functions are not supported in the Solaris implementation of Mobile IP:

RFC 1700

General Routing Encapsulation

RFC 1701

General Routing Encapsulation

RFC 2004

Minimal Encapsulation Within IP

The following functions are not supported in the Solaris implementation of Mobile IP:

• The forwarding of multicast or broadcast traffic by the home agent to the foreign agent for a mobile node that is visiting a foreign network

• The routing of broadcast and multicast datagrams through reverse tunnels

• Private care-of addresses or private home agent addresses

See mipagent(1M) man page for additional information.