IP Routing for Wireless/Mobile Hosts (mobileip)

Last Modified: 2003-02-19


Gabriel Montenegro <gab@sun.com>
Phil Roberts <proberts@megisto.com>
Basavaraj Patil <basavaraj.patil@nokia.com>

Internet Area Director(s):

Thomas Narten <narten@us.ibm.com>
Margaret Wasserman <margaret.wasserman@nokia.com>

Internet Area Advisor:

Thomas Narten <narten@us.ibm.com>

Mailing Lists:

General Discussion: mobile-ip@sunroof.eng.sun.com
To Subscribe: mobile-ip-request@sunroof.eng.sun.com
In Body: (un)subscribe
Archive: http://playground.sun.com/mobile-ip/

Description of Working Group:

The Mobile IP Working Group has developed routing support to permit IP
nodes (hosts and routers) using either IPv4 or IPv6 to seamlessly
"roam" among IP subnetworks and media types.  The Mobile IP method
supports transparency above the IP layer, including the maintenance of
active TCP connections and UDP port bindings. Where this level of
transparency is not required, solutions such as DHCP and dynamic DNS
updates may be adequate and techniques such as Mobile IP not needed.

The WG moving forward will focus on deployment issues in Mobile IP and
provide appropriate protocol solutions to address known deficiencies
and shortcomings. For example, the wireless/cellular industry is
considering using Mobile IP as one technique for IP mobility for
wireless data. The working group will endeavor to gain an
understanding of data service in cellular systems such as
GPRS, UMTS, CDMA2000, and interact with other standards bodies that
are trying to adopt and deploy Mobile IP WG protocols in these
contexts.  In order to provide a complete solution and a set of
protocols that can be used as a roadmap for widespread deployment, the
following work needs to be accomplished by this WG. In the near term,
the WG needs to work on:

- Use of NAIs to identify mobile users/nodes.

- Specifying how Mobile IP should use AAA functionality to support

  inter-domain and intra-domain mobility.

- Develop solutions for IPv4 private address spaces for the scenarios
  needed for deployment.

- Documenting any requirements specific to cellular/wireless networks.

In the longer term, the WG needs to address:

- QoS in the mobile IP environment using diff-serv and/or

- Location Privacy.

The Working Group will ensure that solutions proposed for these problem
domains are suitable for IPv4 and IPv6 respectively.

Goals and Milestones:

Done    Review and approve the charter, making any changes deemed necessary.
Done    Post an Internet-Draft documenting the Mobile Hosts protocol.
Done    Review the charter of the Mobile IP Working Group for additional work required to facilitate non-host mobility.
Done    Submit the IPv4 Mobile Host Protocol to the IESG as a Proposed Standard.
Done    Submit the IPv6 Mobile Host Protocol to the IESG as a Proposed Standard.
Done    Submit Internet-Draft for NAI support in Mobile IP to IESG for consideration as a Proposed Standard.
Done    Review security framework requirements for Mobile IP.
Done    Review solutions and submit drafts for mobility in private address spaces.
Done    Supply AAA requirements for Mobile IP to the AAA Working Group
Sep 00    Submit the IPv4 Mobile IP Protocol to the IESG for consideration as a Draft Standard.
Oct 00    Review the WG charter and update as needed.
Dec 00    Develop an access technology independent method for supporting low latency handover between access points within an administrative domain or across administrative domains.
Jul 01    Review QoS in a Mobile IP enabled network.
Aug 01    Submit Mobile IPv6 MIB to IESG for consideration as a Proposed Standard.


Problem Statement: Mobile IPv4 Traversal of VPN Gateways (43785 bytes)
Mobile IPv4 Traversal Across IPsec-based VPN Gateways (99041 bytes)

Request For Comments:

Applicability Statement for IP Mobility Support (RFC 2005) (10509 bytes)
Minimal Encapsulation within IP (RFC 2004) (12202 bytes)
IP Encapsulation within IP (RFC 2003) (30291 bytes)
IP Mobility Support (RFC 2002) (193246 bytes) obsoleted by RFC 3220
The Definitions of Managed Objects for IP Mobility Support using SMIv2 (RFC 2006) (95030 bytes)
Reverse Tunneling for Mobile IP (RFC 2344) (39469 bytes) obsoleted by RFC 3024
Sun's SKIP Firewall Traversal for Mobile IP (RFC 2356) (53196 bytes)
Mobile IP Network Access Identifier Extension for IPv4 (RFC 2794) (16960 bytes)
Mobile IP Authentication, Authorization, and Accounting Requirements (RFC 2977) (63520 bytes)
Mobile IP Challenge/Response Extensions (RFC 3012) (37005 bytes)
Reverse Tunneling for Mobile IP, revised (RFC 3024) (63929 bytes)
Mobile IP Vendor/Organization-Specific Extensions (RFC 3025) (15611 bytes) obsoleted by RFC 3115
Mobile IP Vendor/Organization-Specific Extensions (RFC 3115) (16363 bytes)
IP Mobility Support for IPv4, revised (RFC 3220) (238343 bytes) obsoleted by RFC 3344
IP Mobility Support for IPv4 (RFC 3344) (241041 bytes)
Mobile IP Traversal of Network Address Translation (NAT) Devices (RFC 3519) (80522 bytes)
Registration Revocation in Mobile IPv4 (RFC 3543) (81805 bytes)
Mobility Support in IPv6 (RFC 3775) (393514 bytes)
Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents (RFC 3776) (87076 bytes)
Low-Latency Handoffs in Mobile IPv4 (RFC 4881) (151124 bytes)