2.3.17 Network-based Localized Mobility Management (netlmm)

NOTE: This charter is a snapshot of the 72nd IETF Meeting in Dublin, Ireland. It may now be out-of-date.
In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       Additional NETLMM Page

Last Modified: 2007-07-10


Jonne Soininen <jonne.soininen@nsn.com>
Vidya Narayanan <vidyan@qualcomm.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: netlmm@ietf.org
To Subscribe: http://www1.ietf.org/mailman/listinfo/netlmm
In Body: to subscribe
Archive: http://www1.ietf.org/mail-archive/web/netlmm/current/index.html

Description of Working Group:

The IETF has defined both local and global mobility management
protocols that are intended to handle IP mobility for nodes. All IP
mobility management protocols defined thus far require the involvement
of the mobile node in order to accomplish mobility. This working
group is tasked with defining a network-based local mobility
management protocol, where local IP mobility is handled without
involvement from the mobile node. The idea is that the mobile node
may move across multiple access routers without encountering a change
in its IP address, thereby hiding the mobility from the IP layer and

As part of the first phase of efforts in this working group, a
protocol for such network-based local mobility has been developed.
This protocol, Proxy Mobile IPv6 (PMIPv6), has been developed based on
Mobile IPv6, after considering other alternative approaches. With
this protocol, unmodified IP nodes may change access routers without
having to change the IP address on an interface, within a given
administrative domain. This is accomplished by having Mobile Access
Gateways (MAGs), often part of the access routers in a network, send
binding updates on behalf of mobile nodes attached to them, to a Local
Mobility Anchor (LMA). The LMA manages the mobility of the mobile
nodes across the MAGs within a given PMIPv6 domain.

The PMIPv6 protocol is being adopted as part of several wide-area
wireless network (e.g., 3GPP, 3GPP2, WiMAX) and local area network
environments. The current charter of this working group involves
specification of some necessary features that make the deployment of
this protocol feasible in these various environments.

As part of this effort, it is essential to support mobility for IPv4
end nodes. Some means of dealing with overlapping private IPv4
addresses of mobile nodes and supporting separation of flows between
the MAG and LMA is also required. Further, given that local and
global mobility management protocols are likely to be deployed in some
combination in various environments, it is necessary to clearly define
the interactions between PMIPv6 and MIPv6. Interactions with AAA
protocols such as RADIUS and Diameter may be required for
authorization or provisioning purposes. When multiple LMAs are
present, an automated LMA discovery mechanism may be needed to
facilitate deployment. The above items are in scope of the current

The MAG and LMA are considered to be IPv6 capable for all efforts of
this protocol. Also, all features defined must work with unmodified
IP nodes. Specifying any changes to mobile nodes is out of scope of
the current charter. Handoff and route optimizations are also out of
scope. There is, however, considerable interest in optimization work,
for instance, and a future recharter of this working group is likely
to address this in some manner.

NETLMM WG Deliverables

1) Interface between a PMIPv6 MAG and MN: This interface will define
the interaction between a regular IP node and a MAG that will be used
to trigger various mobility management actions on the MAG. This is
necessary for the MAG to properly trigger binding updates to the LMA
and create appropriate mobility management state.

2) IPv4 Support for PMIPv6: This will define the support for IPv4
nodes in PMIPv6. This will also define the protocol operation over an
IPv4 transport between the MAG and LMA, by employing protocol extensions
already developed in the MEXT WG.

3) Interactions between Mobile IPv6 and Proxy Mobile IPv6: This will
highlight the interactions required between these protocols in various
methods of co-existence of these in a system, with a view to
documenting the best practices to be used. The scenarios considered
will include a hierarchical model of local and global mobility
management using PMIPv6 and MIPv6 respectively, a mixed mode of the
two with some nodes supporting MIPv6 and others not, and the use of
MIPv6 upon movement of nodes outside a PMIPv6 domain.

4) GRE Keying option for PMIPv6: This will define a mechanism using
GRE keys to support separation of flows between a MAG and LMA.

5) RADIUS support for PMIPv6: This will define the interactions
between RADIUS and PMIPv6 to support policy provisioning and

6) Automatic LMA discovery: This will define the ability for MAGs to
automatically discover and use an LMA within a PMIPv6 domain. The
scope of this effort may include specifying the use of DNS or DHCP
based LMA discovery or LMA discovery using policy information
retrieved via AAA protocols.

7) MIB for PMIPv6: This will define the MIB for the protocol for
interoperability purposes.

8) PMIPv6 path management and failure detection: This will define
an extension to the PMIPv6 protocol allowing PMIPv6 peers to
verify bidirectional reachability with their peer, detect
failure of their peer, and signal their own failure to their

Goals and Milestones:

Done  Charter Working Group
Done  Working Group Last Call on Problem Statement and Requirements documents
Done  Discuss Last Call comments on Problem Statement and Requirements documents
Done  Submit Problem Statement and Requirements documents to IESG for publication as Informational RFCs
Done  Working Group Last Call on Threat Model documents. Submit Threat Model document to SAAG for review
Done  Working Group Last Call on Threat Model document
Done  IETF 66, Discuss Last Call comments on Threat Model document
Done  Submit Threat Model document to IESG for publication as an Informational RFC
Done  Main protocol decision completed
Done  Initial version of the Protocol draft submitted
Done  Working Group Last Call on Mobile Node to Access Router document
Aug 2007  Working Group Last Call on the Protocol document
Aug 2007  Working Group Last Call on Mobile Node to Access Router document
Aug 2007  Initial version of the PMIP6-MIP6 Interactions document
Sep 2007  Working Group Last Call on the IPv4 support document
Oct 2007  Working Group Last Call on the PMIP6-MIP6 Interactions document
Oct 2007  Submit Protocol, IPv4 support and Mobile Node to Access Router documents for AD review
Nov 2007  Submit PMIP6-MIP6 Interactions document for AD review
Dec 2007  Re-charter


  • draft-ietf-netlmm-mn-ar-if-03.txt
  • draft-ietf-netlmm-proxymip6-11.txt
  • draft-ietf-netlmm-pmip6-ipv4-support-02.txt

    Request For Comments:

    RFC4830 I Problem Statement for Network-based Localized Mobility Management (NETLMM)
    RFC4831 I Goals for Network-based Localized Mobility Management (NETLMM)
    RFC4832 I Security Threats to Network-Based Localized Mobility Management (NETLMM)

    Meeting Minutes


    IETF72 WG Status
    IPv4 Support for Proxy Mobile IPv6
    PMIPv6 – MIPv6 Interactions – Scenario C
    PMIPv6 –MIPv6 interactions To break or not to break multi-homing?
    GRE Key Option for Proxy MIPv6
    RADIUS Proxy Mobile IPv6
    LMA Discovery
    pmipv6 MIB Specification
    Heartbeat Mechanism for Proxy Mobile IPv6