2.5.1 IP Routing for Wireless/Mobile Hosts (mobileip)

NOTE: This charter is a snapshot of the 43rd IETF Meeting in Orlando, Florida. It may now be out-of-date. Last Modified: 25-Nov-98


Erik Nordmark <nordmark@eng.sun.com>
Jim Solomon <solomon@rback.com>

Routing Area Director(s):

Rob Coltun <rcoltun@fore.com>

Routing Area Advisor:

Rob Coltun <rcoltun@fore.com>

Mailing Lists:

General Discussion:mobile-ip@smallworks.com
To Subscribe: majordomo@smallworks.com
In Body: subscribe mobile-ip
Archive: ftp://ftp.smallworks.com/mobile-ip.archive

Description of Working Group:

The Mobile IP Working Group is chartered to develop or adopt architectures and protocols to support mobility within the Internet. In the near-term, protocols for supporting transparent host ``roaming'' among different subnetworks and different media (e.g., LANs, dial-up links, and wireless communication channels) shall be developed and entered into the Internet standards track. The work is expected to consist mainly of new and/or revised protocols at the (inter)network layer, but may also include proposed modifications to higher-layer protocols (e.g., transport or directory). However, it shall be a requirement that the proposed solutions allow mobile hosts to interoperate with existing Internet systems.

In the longer term, the group may address, to the extent not covered by the mobile host solutions, other types of internet mobility, such as mobile subnets (e.g., a local network within a vehicle), or mobile clusters of subnets (e.g., a collection of hosts, routers, and subnets within a large vehicle, like a ship or spacecraft, or a collection of wireless, mobile routers that provide a dynamically changing internet topology).

Goals and Milestones:



Review and approve the charter, making any changes deemed necessary.



Post an Internet-Draft documenting the Mobile Hosts protocol.



Review the charter of the Mobile IP Working Group for additional work required to facilitate non-host mobility.

Jul 96


Submit the IPv4 Mobile Host Protocol to the IESG as a Proposed Standard.

Dec 96


Submit the IPv6 Mobile Host Protocol to the IESG as a Proposed Standard.

Mar 97


Review the WG charter and update as needed.


Request For Comments:







IP in IP Tunneling



Applicability Statement for IP Mobility Support



Minimal Encapsulation within IP



IP Encapsulation within IP



IP Mobility Support



The Definitions of Managed Objects for IP Mobility Support using SMIv2



Reverse Tunneling for Mobile IP



Sun's SKIP Firewall Traversal for Mobile IP

Current Meeting Report

IP Routing for Wireless/Mobile Hosts (mobileip)
Monday, 12/7/98, 1300 - 1500

Co-chairs: Erik Nordmark <nordmark@eng.sun.com>

Minutes by: Jim Solomon

- Mobile IPv6 is in IESG Last Call; several implementations exist and some interest was expressed in having a bakeoff
- There are numerous, disparate, proposals for enhancing Mobile IPv4 to add new AAA functionality, to regionalize registration messages for local handoffs, support private address-spaces, etc. The chairs request that the authors of these disparate groups work together to draft requirements and set out to solve them within the context of the working group.

I. Jim Solomon <solomon@rback.com>, Announcements
- IESG has been asked to advance Mobile IPv6 to PS RFC. Expect Last Call in a week or so.
- A handful of Mobile IPv6 implementations have been written. Some interest in a bakeoff expressed -- to be taken to the mailing list.
- No substantial Mobile IPv4 deployment to discuss.

II. Dave Johnson <dbj@cs.cmu.edu>, Mobility Support in IPv6
Dave described the updates since the last draft:
- clarification of destination options and sub-options
- other clarifications re: prefix options
- Abstract now states that this document confers a requirement on *all* IPv6 nodes
- changes are non-controversial -- no objections from the room
- Erik to coordinate MIPv6 interoperability testing

III. Andras Gergely Valko <andras@comet.columbia.edu>, Cellular IP
- Mobility standards: GPRS, CDPD, UMTS IMT-2000, W-LAN, Mobile IP
- Proposed Network has mobility mgmt, paging, handoff, but no HLR, MSC signalling system, etc ==> Smooth handoffs, simplicity, and scalability are drivers
- Each base station reverse learns MN's location, up to the first-hop router (typically an FA)
- implementations in progress for FreeBSD/WaveLAN
- Security (hijacking, denial-of-service) was mentioned as an issue.
- Routing loops are also possible for arbitrary topologies of Base Stations

IV. Martin Körling <Martin.Korling@era-t.ericsson.se>, IMT-2000 Requirements on Mobile IP
- Requirements, not protocols, for 3G networks
- Problems with 2002 which prevent widescale, commercial, deployment: security model, static public IP address (private address support), handoff performance, scalability
- Issues: authentication, key dist., route optim, hierarchical structure, dynamic host conf, separation of control and traffic
- Martin's main observation: there have been a lot of proposals on these issues but very little discussion on the mailing list on the requirements for these topics.

V. Charlie Perkins <charles.perkins@eng.sun.com>, AAA Extensions for Mobile IP
- AAABOF seems to indicate that a working group will be formed, with DIAMETER-like functionality to be defined
- Idea is to authenticate MN's NAI (username) instead of its IP address, ala most remote access in the internet
- Enhancements since last draft: private address support, regionalized regitration, self-configuring agent hierarchy

VI. Mooi Choo <chuah@hoserve.ho.lucent.com>, Mobile IP Enhancements
- proposes AAA extensions, localized mobility, and other enhancements to Mobile IP
- Two implementations: Bell Labs, Malaysia Multimedia University

VII. Foo Siang Fook <engp7498@leonis.nus.edu.sg>, Regional Aware Foreign Agents (RAFA) Mobile IP extension for Private Internets Support (MPN) Reverse Twice Network Address Translators (RAT)
- more AAA enhancements (key management), fast handoffs for regionalized mobility, notification of old FA after handoff
- implementation underway

X. George Fankhauser <gfa@acm.org>, RSVP and Mobile IPv6
- RSVP_HOP object contains home address
- SESSION object has wrong flow id Solution:
- Change routers on path to match on home address? changing core is not a viable option
- Proposal to change end-systems instead to modify the RSVP messages and extend flows after handoffs


IP Routing for Wireless/Mobile Host
Cellular IP
AAA Extensions for MobileIP
Mobile-IP Enchancements
RAFA: Regional Aware Foreign Agent for Fast Local Handoffs
Mobile IP Extensions for Private Internets Support
Reverse Twice Network Address Translators
Mobile IPv6/RSVP Integration