Skip to main content

Mobility for IPv6

Document Charter Mobility for IPv6 WG (mip6)
Title Mobility for IPv6
Last updated 2007-11-20
State Approved
WG State Concluded
IESG Responsible AD Jari Arkko
Charter edit AD (None)
Send notices to (None)

Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
host to continue using its home address as it moves around the
Internet, enabling continuity of sessions. Mobile IPv6 supports
transparency above the IP layer, including maintenance of active
transport level sessions. The base specifications for Mobile IPv6
consist of:

o RFC 3775
o RFC 3776

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 implementation and interoperability
experience are addressed, and that the base specifications are
maintained. The group will also produce informational documentation,
such as design rationale documents or description of specific issues
within the protocol.

Deployment considerations call for work to reduce per-mobile node
configuration and enrollment effort, solutions to enable dual-stack
operation, mechanisms to support high-availabity home agents, and ways
to employ Mobile IPv6 in the presence of firewalls.

Work items related to base specification maintenance include:

- Create and maintain an issue list that is generated on the basis of
implementation and interoperability experience. Address specific
issues with specific updates or revisions of the base
specification. One specific area of concern that should
be analyzed and addressed relates to multilink subnets.

This work item relates only to corrections and
clarifications. The working group shall not revisit design
decisions or change the protocol.

- Update RFC 3776 to specify the usage of IKEv2 for the establishment
of the IPsec SA between the MN and HA. This work also provides a
way for a mobile node to change its home address or employ multiple
home addresses as needed.

- Update the IANA considerations of RFC 3775 to allow extensions for
experimental purposes as well passing of optional vendor-specific

Work items related to large scale deployment include:

- Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
be used when the device is turned on the very first time and
activates Mobile IPv6, or periodically such as when powering
on. The WG should investigate and define the scope before solving
the problem.

Work on the problem statement and the solutions needed for various
deployment scenarios. Work with other WGs such as DHC for defining
the options needed for bootstrapping.

- Capture the AAA requirements needed for bootstrapping and
deployment, and work with the Radext and DiME WGs on the solutions.

- A Solution for MIP6 session continuity for dual stack hosts which
attach to IPv4 access networks. Additionally provide a mechanism
for carrying IPv4 packets via the Home agent for MIP6 capable
dual-stack hosts. This work will be done in collaboration with the

- A protocol based solution for enhancing the reliability of home
agents and a method to force a host to switch home agents.

- A mechanism to force an MN to switch the HA that is currently
serving it. This is required in deployments where the HA may need
to be taken offline for maintenance.

- Work on solutions to deal with firewalls and the problems that
firewalls cause as identified in RFC 4487.

Work items related to informational documentation include:

- Produce a problem statement relating to location privacy and the
use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the

- Produce a design rationale that documents the historical
thinking behind the introduction of an alternative security
mechanism, the Authentication Protocol (RFC 4285).

It should be noted that some of the features that are directly related
to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
working groups. The specific extensions from these groups are out of
scope for the MIP6 working group. In particular, all optimizations are
out of scope. However, MIP6 may assist these groups when they use
features listed above and have requirements on them.