This Working Group did not meet
NOTE: This charter is a snapshot of the 58th IETF Meeting in Minneapolis, Minnesota USA. It may now be out-of-date.
Last Modified: 2003-02-19
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 int-serv/RSVP.
- Location Privacy.
The Working Group will ensure that solutions proposed for these problem domains are suitable for IPv4 and IPv6 respectively.
| 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. |
| RFC | Status | Title |
|---|---|---|
| RFC2005 | PS | Applicability Statement for IP Mobility Support |
| RFC2004 | PS | Minimal Encapsulation within IP |
| RFC2003 | PS | IP Encapsulation within IP |
| RFC2002 | PS | IP Mobility Support |
| RFC2006 | PS | The Definitions of Managed Objects for IP Mobility Support using SMIv2 |
| RFC2344 | PS | Reverse Tunneling for Mobile IP |
| RFC2356 | I | Sun's SKIP Firewall Traversal for Mobile IP |
| RFC2794 | PS | Mobile IP Network Access Identifier Extension for IPv4 |
| RFC2977 | I | Mobile IP Authentication, Authorization, and Accounting Requirements |
| RFC3012 | PS | Mobile IP Challenge/Response Extensions |
| RFC3024 | PS | Reverse Tunneling for Mobile IP, revised |
| RFC3025 | PS | Mobile IP Vendor/Organization-Specific Extensions |
| RFC3115 | PS | Mobile IP Vendor/Organization-Specific Extensions |
| RFC3220 | PS | IP Mobility Support for IPv4, revised |
| RFC3344 | PS | IP Mobility Support for IPv4 |
| RFC3519 | PS | Mobile IP Traversal of Network Address Translation (NAT) Devices |
| RFC3543 | PS | Registration Revocation in Mobile IPv4 |