Mobility EXTensions for IPv6 (mext)
-----------------------------------

Charter
Last Modified: 2007-11-26

Current Status: Active Working Group

Chair(s):
    Julien Laganier  <[email protected]>
    Marcelo Bagnulo  <[email protected]>

Internet Area Director(s):
    Jari Arkko  <[email protected]>
    Mark Townsley  <[email protected]>

Internet Area Advisor:
    Jari Arkko  <[email protected]>

Mailing Lists:
    General Discussion:[email protected]
    To Subscribe:      https://www1.ietf.org/mailman/listinfo/mext
    Archive:           http://www1.ietf.org/mail-archive/web/mext/current

Description of Working Group:

Mobile IPv6 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. In addition, network mobility (NEMO) mechanisms built on top
of Mobile IPv6 allow managing the mobility of an entire network, as it
changes its point of attachment to the Internet. The base
specifications consist of:

o RFC 3775 (Mobile IPv6)
o RFC 3963 (NEMO)
o RFC 4877 (Mobile IPv6 Operation with IKEv2)

The MEXT Working Group continues the work of the former MIP6, NEMO,
and MONAMI6 Working Groups.

The primary goal of MEXT will be to (A) enhance base IPv6 mobility by
continuing work on developments that are required for wide-scale
deployments and specific deployment scenarios. Additionally, (B) the
working group will ensure that any issues identified by implementation
and interoperability experience are addressed, and that the base
specifications are maintained. (C) The group will also produce
informational documentation, such as design rationale documents or
description of specific issues within the protocol.

Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) mechanisms to support high-availability
home agents, (A.3) allowing the use of multiple interfaces in mobile
nodes, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
(A.5) address the specific needs of automotive and aviation
communities for route optimisation in network mobility, and (A.6)
support for AAA is needed as a continuation of earlier work on
bootstrapping.

Work items related to large scale deployment include:

(A.1) A Solution for Mobile IPv6 and NEMO 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 Mobile IPv6 or NEMO capable dual-stack hosts.

(A.2) A protocol based solution for enhancing the reliability of home
agents and a method to force a host/router 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 needs to
be taken offline for maintenance.

(A.3) Use of multiple interfaces.

Today, the protocols do not provide suppport for simultaneous
differentiated use of multiple access technologies. Several
proposals exist for such support, and some of them have been
implemented and tested.

When a mobile host/router uses multiple network interfaces
simultaneously, or when multiple prefixes are available on a
single network interface, the mobile host/router would end up
with multiple Care-of Addresses (CoAs). In addition, the Home
Agent might be attached to multiple network interfaces, or to a
single network interface with multiple prefixes, hence resulting
in the option to use multiple IP addresses for the Home
Agent. This could result in the possibility of using a multitude
of bi-directional tunnels between pairs of {Home Agent address,
CoA} and a number of associated issues: establishment, selection
and modification of multiple simultaneous tunnels.

The objective of the WG is to produce a clear problem statement
and to produce standard track specifications to the problems
associated with the simultaneous use of multiple addresses for
either mobile hosts using Mobile IPv6 or mobile routers using
NEMO Basic Support and their variants (FMIPv6, HMIPv6,
etc). Where the effects of having multiple prefixes on a single
interface is identical to the effects of having multiple
interfaces each with a single prefix, the WG will consider a
generalized approach to cater for multiple prefixes available to
a mobile host/router.

The WG uses existing tunneling mechanisms defined for Mobile
IPv6. The involved nodes need to select which tunnel instance
to use when multiple ones are available due to multiple
addresses on either end. But the WG does not plan to define a
new mechanism for this, but rather document how to use existing
mechanisms based upon preferences or policies. In particular,
the WG will consider that a tunnel is alive as long as packets
can be exchanged with the corresponding peer. In addition, local
information, such as interface up/down events, or other failure
detection mechanisms can be used to quickly detect failure of
tunnel(s).

Goals and Milestones:

  Done         Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
               publication as a Proposed Standard

  Dec 2007       Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
               publication as a Proposed Standard.

  Dec 2007       Submit I-D 'Motivation for Authentication I-D' to IESG for
               publication as Informational.

  Dec 2007       Submit Multiple CoA Registration to IESG

  Done         Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
               publication as a Proposed Standard

  Feb 2008       Submit I-D 'Goals for AAA HA Interface' to IESG for publication
               as Informational.

  Feb 2008       Submit -00 draft on Route Optimization needs for Personal
               Mobile Router

  Feb 2008       Submit -00 draft on Route Optimization Needs for Automobile and
               Highway Deployments

  Feb 2008       Submit -00 draft on Route Optimization Needs for Aircraft and
               Spacecraft Deployments

  Mar 2008       Submit the final doc on Prefix Delegation for NEMO to the IESG,
               for Proposed Standard

  Done         Submit I-D 'Mobility Header Home Agent Switch Message' to IESG
               for publication as a Proposed Standard

  May 2008       Submit final doc on Route Optimization needs for Personal
               Mobile Router, for Informational

  May 2008       Submit final doc on Route Optimization Needs for Automobile and
               Highway Deployments, for Informational

  May 2008       Submit final doc on Route Optimization Needs for Aircraft and
               Spacecraft Deployments, for Informational

  May 2008       Submit -00 draft for solution to aircraft/spacecraft problem

  Jun 2008       Determine how to proceed with remaining automotive/Personal
               Mobile Router solutions

  Jun 2008       Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
               publication as a proposed standard.

  Jul 2008       Submit Analysis of the use of Multiple Simultaneous Care-of
               Addresses and Home Agent addresses, for Informational

  Jul 2008       Submit Multiple Interfaces Motivations and Scenario to IESG,
               for Informational

  Aug 2008       Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for
               publication as Informational.

  Aug 2008       Submit the final doc on MIB for NEMO Basic Support to the IESG,
               for Proposed Standard

  Oct 2008       Submit Flow/binding policy transport to IESG, for Proposed
               Standard

  Oct 2008       Submit Flow/binding policy format to IESG, for Proposed
               Standard

  Nov 2008       Submit final doc for solution to aircraft/spacecraft problem to
               the IESG, for Proposed Standard

  Nov 2008       Recharter to work on the remaining automotive/Personal Mobile
               Router solutions

  Dec 2008       Submit I-D(s) related to specific updates and corrections of
               RFC 3775 to IESG for publication as Proposed Standard.

  Dec 2008       Submit I-D 'Home agent reliability' to IESG for publication as
               a Proposed Standard.


Internet-Drafts:

Posted Revised         I-D Title   <Filename>
------ ------- --------------------------------------------
Aug 2005 Aug 2007   <draft-ietf-nemo-prefix-delegation-02.txt>
               Mobile Network Prefix Delegation

Oct 2005 Nov 2007   <draft-ietf-mip6-nemo-v4traversal-06.txt>
               Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)

Feb 2006 Nov 2007   <draft-ietf-monami6-mipv6-analysis-04.txt>
               Analysis of Multihoming in Mobile IPv6

Jun 2006 Feb 2008   <draft-ietf-monami6-multiplecoa-06.txt>
               Multiple Care-of Addresses Registration

Jun 2006 Nov 2007   <draft-ietf-mip6-hareliability-03.txt>
               Home Agent Reliability Protocol

Oct 2006 Nov 2007   <draft-ietf-mip6-radius-03.txt>
               RADIUS Mobile IPv6 Support

Oct 2007 Oct 2007   <draft-ietf-mip6-generic-notification-message-00.txt>
               Generic Notification Message for Mobile IPv6

Dec 2007 Feb 2008   <draft-ietf-mext-aero-reqs-01.txt>
               NEMO Route Optimization Requirements for Operational Use in
               Aeronautics and Space Exploration Mobile Networks

Dec 2007 Dec 2007   <draft-ietf-mext-aaa-ha-goals-00.txt>
               AAA Goals for Mobile IPv6

Jan 2008 Jan 2008   <draft-ietf-mext-nemo-v4traversal-00.txt>
               Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)

Feb 2008 Feb 2008   <draft-ietf-mext-nemo-mib-00.txt>
               NEMO Management Information Base

Feb 2008 Feb 2008   <draft-ietf-mext-nemo-ro-automotive-req-00.txt>
               Automotive Industry Requirements for NEMO Route Optimization

Request For Comments:

 None to date.