Mobility for IPv6 (mip6)
------------------------
Charter
Last Modified: 2006-05-24
Current Status: Active Working Group
Chair(s):
Basavaraj Patil <basavaraj.patil@nokia.com>
Gopal Dommety <gdommety@cisco.com>
Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>
Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>
Mailing Lists:
General Discussion:mip6@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
Description of Working Group:
Mobile IPv6 (MIPv6) specifies routing support to permit an IPv6 host to
continue using its "permanent" home address as it moves around
the Internet. Mobile IPv6 supports transparency above the IP
layer, including maintenance of active TCP connections and UDP port
bindings. The specifications for these mechanisms consist of:
draft-ietf-mobileip-ipv6-24 (RFC XXX) and
draft-ietf-mobileip-mipv6-ha-ipsec-06 (RFC XXX)
The protocol as specified in the above two documents can be considered
as the baseline or minimum protocol set for implementing IPv6
mobility. During the development phase of the base protocol, a few
additional features were identified as necessary to facilitate
deployment (described below).
The primary goal of the MIP6 working group will be to enhance base
IPv6 mobility by continuing work on developments that are required for
wide-scale deployments. Additionally the working group will ensure
that any issues identified by the interop testing of the MIPv6
specifications are addressed quickly. Specific work items with this
goal in mind are listed below:
1) Create and maintain an issue list that is generated on the basis of
interop testing and address these issues as enhancements to the
base protocol
2) Features such as renumbering of the home link, home agent discovery,
Route Optimization, which are currently a part of the base
specification can be specified more explicitly as separate
specifications. This will also enable modularizing the Mobile
IPv6 specification further into the minimal subset and add-on
features. Some of these specifications will be identified as
base mechanisms of Mobile IPv6.
3) A number of enhancements to basic IPv6 mobility were identified
during the development of the base specification. These
enhancements will be taken up in a phased manner depending on the
priority identified with each. Below are listed the work items to
be taken up by the WG:
- A bootstrap mechanism for setting up security associations
between the Mobile Node (MN) and Home Agent (HA) that would
enable easier deployment of Mobile IPv6. This bootstrap
mechanism is intended to be used when the device is turned on
the very first time and activates MIPv6. The WG should
investigate and define the scope before solving the problem.
- Improving home agent reliability: in the event of a home agent
crashing, this would allow another home agent to continue
providing service to a given mobile node.
- Support for a Mobile Node changing its home address, either
because of renumbering in its home network or because it
periodically changes addresses (perhaps via RFC3041)
- Route optimization will require security mechanisms for
trusting and updating the binding information.Return-routability
is the basic mechanism for route-optimization. Mechanisms using
a shared secret Key/Security Association will be considered.
Methods for establishing a security association between the
mobile node and the correspondent node are out of the scope
of the WG.
- The working group will also document problem statements
associated with deploying Mobile IPv6 in the following areas:
a. Mobile IPv6 issues in the presence of firewalls
b. Mobile IPv6 deployment and transition issues in the
presence of IPv4/IPv6 networks
c. Multicast issues
It should be noted that there are potential optimizations that might
make mobile IP more attractive for use by certain applications (e.g.,
making handovers "faster"). The latter category of optimizations is
explicitly out-of-scope at this time; this WG will focus on issues
for which there is strong consensus that the work is needed to get
basic mobility deployable on a large scale.
Goals and Milestones:
Done Submit I-D 'Issues with firewall Problem statement' to IESG
Done Submit I-D 'MIPv6 MIB' to IESG
Done Submit I-D 'Extensions to Socket Advanced API for MIPv6' to
IESG
Done Submit I-D 'Alternate Route Optimization (Pre-config Key)
scheme' to IESG
Done Submit Bootstrapping problem statement to IESG
Done Submit I-D 'Authentication Option for MIPv6' to IESG
Done Submit I-D 'Identification Option for MIPv6' to IESG
Done Submit I-D 'MIPv6 operation with IKEV2 and the revised IPsec
Architecture to IESG
Done Submit Problem statement and Solution to Mobile IPv6 transition
between v4/v6 networks to IESG
Jul 2006 Submit ID Submit ID 'Motivation for Authentication I-D' to IESG
Aug 2006 Separate specs for Home Agent (HA) Discovery, Route
Optimization, Renumbering to IESG
Aug 2006 Submit Bootstrapping solution for Integrated Scenario to IESG
Aug 2006 Submit Bootstrapping solution for split Scenario to IESG
Sep 2006 Submit I-D 'Goals for AAA HA Interface' to IESG
Dec 2006 Submit Home agent reliability to IESG
Internet-Drafts:
Posted Revised I-D Title <Filename>
------ ------- --------------------------------------------
Jul 2004 May 2006 <draft-ietf-mip6-bootstrap-ps-05.txt>
Problem Statement for bootstrapping Mobile IPv6
Oct 2004 Apr 2006 <draft-ietf-mip6-ikev2-ipsec-06.txt>
Mobile IPv6 Operation with IKEv2 and the revised IPsec
Architecture
Jan 2005 Dec 2005 <draft-ietf-mip6-cn-ipsec-02.txt>
Using IPsec between Mobile and Correspondent IPv6 Nodes
May 2005 Jun 2006 <draft-ietf-mip6-aaa-ha-goals-02.txt>
Goals for AAA-HA interface
Jun 2005 Mar 2006 <draft-ietf-mip6-bootstrapping-split-02.txt>
Mobile IPv6 bootstrapping in split scenario
Jul 2005 Jun 2006 <draft-ietf-mip6-dsmip-problem-02.txt>
Mobility management for Dual stack mobile nodes A Problem
Statement
Sep 2005 Jun 2006 <draft-ietf-mip6-whyauthdataoption-01.txt>
Why Authentication Data suboption is needed for MIP6
Oct 2005 Jun 2006 <draft-ietf-mip6-location-privacy-ps-02.txt>
IP Address Location Privacy and Mobile IPv6: Problem Statement
Oct 2005 Jun 2006 <draft-ietf-mip6-nemo-v4traversal-02.txt>
Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)
Oct 2005 Jun 2006 <draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt>
MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
Jun 2006 Jun 2006 <draft-ietf-mip6-ha-switch-00.txt>
Mobility Header Home Agent Switch Message
Jun 2006 Jun 2006 <draft-ietf-mip6-hareliability-00.txt>
Home Agent Reliability Protocol
Request For Comments:
RFC Stat Published Title
------- -- ----------- ------------------------------------
RFC3776Standard Jun 2004 Using IPsec to Protect Mobile IPv6 Signaling between
Mobile Nodes and Home Agents
RFC3775Standard Jun 2004 Mobility Support in IPv6
RFC4283Standard Dec 2005 Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
RFC4225 I Dec 2005 Mobile IP version 6 Route Optimization Security Design
Background
RFC4285 I Jan 2006 Authentication Protocol for Mobile IPv6
RFC4295 PS Apr 2006 Mobile IPv6 Management Information Base
RFC4487 I May 2006 Mobile IPv6 and Firewalls: Problem Statement
RFC4449 PS Jun 2006 Securing Mobile IPv6 Route Optimization Using a Static
Shared Key
RFC4584 I Jul 2006 Extension to Sockets API for Mobile IPv6