2.3.13 Mobility for IPv6 (mip6)

NOTE: This charter is a snapshot of the 67th IETF Meeting in San Diego, California USA. It may now be out-of-date.

Last Modified: 2006-10-05


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
Oct 2006  Submit I-D 'Mobility management for Dual stack mobile nodes: A Problem Statement' to IESG for publication as Informational.
Oct 2006  Submit I-D 'Motivation for Authentication I-D' to IESG for publication as Informational.
Oct 2006  Submit I-D 'Bootstrapping solution for Integrated Scenario' to IESG for publication as a Proposed Standard.
Oct 2006  Submit I-D 'Goals for AAA HA Interface' to IESG for publication as Informational.
Oct 2006  Submit I-D 'Address Location Privacy and Mobile IPv6 Problem Statement' to IESG for publication as Informational.
Nov 2006  Submit I-D 'Bootstrapping solution for split Scenario' to IESG for publication as a Proposed Standard.
Nov 2006  Submit I-D 'DHCP Options for Home Information Discovery in MIPv6' for publication as a proposed standard.
Dec 2006  Submit I-D 'Home agent reliability' to IESG for publication as a Proposed Standard.
Dec 2006  Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for publication as a Proposed Standard.
Dec 2006  Submit I-D 'Mobility Header Home Agent Switch Message' to IESG for publication as a Proposed Standard.
Jan 2007  Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for publication as a Proposed Standard.
Apr 2007  Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for publication as a proposed standard.
Apr 2007  Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for publication as Informational.
May 2007  Submit I-D(s) related to specific updates and corrections of RFC 3775 to IESG for publication as Proposed Standard.


  • draft-ietf-mip6-ikev2-ipsec-07.txt
  • draft-ietf-mip6-cn-ipsec-03.txt
  • draft-ietf-mip6-aaa-ha-goals-03.txt
  • draft-ietf-mip6-bootstrapping-split-03.txt
  • draft-ietf-mip6-dsmip-problem-02.txt
  • draft-ietf-mip6-whyauthdataoption-01.txt
  • draft-ietf-mip6-location-privacy-ps-04.txt
  • draft-ietf-mip6-nemo-v4traversal-03.txt
  • draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
  • draft-ietf-mip6-ha-switch-01.txt
  • draft-ietf-mip6-hareliability-00.txt
  • draft-ietf-mip6-hiopt-00.txt
  • draft-ietf-mip6-radius-01.txt

    Request For Comments:

    RFC3775 Standard Mobility Support in IPv6
    RFC3776 Standard Using IPsec to Protect Mobile IPv6 Signaling between Mobile Nodes and Home Agents
    RFC4225 I Mobile IP version 6 Route Optimization Security Design Background
    RFC4283 Standard Mobile Node Identifier Option for Mobile IPv6 (MIPv6)
    RFC4285 I Authentication Protocol for Mobile IPv6
    RFC4295 PS Mobile IPv6 Management Information Base
    RFC4449 PS Securing Mobile IPv6 Route Optimization Using a Static Shared Key
    RFC4487 I Mobile IPv6 and Firewalls: Problem Statement
    RFC4584 I Extension to Sockets API for Mobile IPv6
    RFC4640 I Problem Statement for bootstrapping Mobile IPv6

    Meeting Minutes


    Agenda, Status and Next steps
    AAA Goals for Mobile IPv6
    MIP6 Operation with IKEv2 and the revised IPsec Architecture
    HA reliability protocol
    PMIP6 Discussion
    Firewall traversal discussion
    Experimental and vendor specific messages