[secdir] [new-work] WG Review: Distributed Mobility Management (dmm)

IESG Secretary <iesg-secretary@ietf.org> Fri, 03 October 2014 19:39 UTC

Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7491A1A73; Fri, 3 Oct 2014 12:39:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1412365198; bh=z1BksY726fW1tDgLfWVbJanDtCSXfCe+lSd7z6cKRbQ=; h=MIME-Version:From:To:Message-ID:Date:Subject:Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=K7YRVse7O16r3O5IokhP5HIYZTI3usg9jsfxdp2Y0SBPb4atD6yUPAJjHkTWyWTm5 TO2Jsn6ojClS41bGi21D16eRf4M0CSIhhMoBvgEh2AZCQTlDJQwWirM0oR7vFhB/Mt 1MB6UTnVKRlENpvcABhXzWiU6fOP6zerzcBGzQDg=
X-Original-To: new-work@ietfa.amsl.com
Delivered-To: new-work@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 23D7F1A1AE7; Fri, 3 Oct 2014 12:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1OGAiHRrym5L; Fri, 3 Oct 2014 12:39:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C47C1A19EC; Fri, 3 Oct 2014 12:39:55 -0700 (PDT)
MIME-Version: 1.0
From: IESG Secretary <iesg-secretary@ietf.org>
To: new-work@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141003193955.16996.85009.idtracker@ietfa.amsl.com>
Date: Fri, 03 Oct 2014 12:39:55 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/new-work/YalNOhoIPwGYo2-KFkV_4e1HQXw
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.15
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: new-work <new-work-bounces@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/secdir/cwaP1IrohHWmyMFhhpG4FUU8TkA
X-Mailman-Approved-At: Fri, 03 Oct 2014 13:46:45 -0700
Subject: [secdir] [new-work] WG Review: Distributed Mobility Management (dmm)
X-BeenThere: secdir@ietf.org
Reply-To: iesg@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Oct 2014 19:39:58 -0000

The Distributed Mobility Management (dmm) working group in the Internet
Area of the IETF is undergoing rechartering. The IESG has not made any
determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to
the IESG mailing list (iesg at ietf.org) by 2014-10-13.

Distributed Mobility Management (dmm)
Current Status: Active WG

  Dapeng Liu <liudapeng@chinamobile.com>
  Jouni Korhonen <jouni.nospam@gmail.com>

Assigned Area Director:
  Brian Haberman <brian@innovationslab.net>

Mailing list
  Address: dmm@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/dmm
  Archive: http://www.ietf.org/mail-archive/web/dmm


Mobility management solutions lie at the center of the wireless Internet
and enable mobile devices to partake in IP networks anytime and
anywhere. The IETF Distributed Mobility Management (DMM) working group
(WG) specifies solutions for IP networks so that traffic between mobile
and correspondent nodes can take an optimal route. DMM solutions aim for
transparency above the IP layer, including maintenance of active
transport level sessions when mobile hosts or mobile networks change
their point of attachment to the Internet.

Wireless network deployments have traditionally relied on hierarchical
schemes that often lead to centralized deployment models, where a small
number of mobility anchors manage both mobility and reachability for a
mobile node. The DMM WG will consider the latest developments in mobile
networking research and operational practice (i.e. flattening network
architectures, the impact of virtualization, new deployment needs as
wireless access technologies evolve in the coming years) and will
describe how distributed mobility management addresses the new needs in
this area better than previously standardized solutions.

A topic of particular focus will be mobility anchoring in this new
context, and the DMM working group is chartered to work on
maintenance-oriented extensions of the Mobile IPv6 protocol family (RFC
5213, RFC 5844, RFC 5555, RFC 5568, and RFC 6275) as well as new
approaches which capitalize on other protocols specified by the IETF.
For example, mobility management in a limited area, such as within an
autonomous system, is not strictly limited to mentioned IP mobility
protocols but can be any existing or a new protocol solution enabling
the movement of a mobile node such as routing protocols. When extending
protocols that are not based on Mobile IP, DMM solutions will have to be
reviewed by the corresponding WGs.

IPv6 is assumed to be present in both the mobile host/router and the
access networks. DMM solutions are primarily targeted at IPv6
deployments and are not required to support IPv4, in particular for the
case where private IPv4 addresses and/or NATs are used. DMM solutions
must maintain backward compatibility:  If the network or the mobile
host/router does not support the distributed mobility management
protocol that should not prevent the mobile host/router gaining basic
access (i.e., nomadic) to the network.

Contrary to earlier IP mobility protocols, mobility management signaling
paths and end-user traffic forwarding paths may differ. Further,
mobility-related functions may be located in separate network nodes. DMM
solutions should not distinguish between physical or virtualized
networking functions. Whenever applicable, clarifications and additional
features/capabilities for specific networking function deployment
models, e.g. in virtualized environments, are in-scope and encouraged.
Solutions may also specify the selection between the care-of addresses
and home address(es)/prefix(es) for different application use cases.

The working group will produce both informational architectural and
standards track protocol solutions on the following work item topics.

      o Distributed mobility management deployment models and scenarios:
        describe the target high-level network architectures and
        deployment models where distributed mobility management
        protocol solutions would apply.

      o Enhanced mobility anchoring: define protocol solutions for a
        gateway and mobility anchor assignment and mid-session mobility
        anchor switching that go beyond what has been specified, for
        example, in RFC 6097, 6463, and 5142. Traffic steering
        associated with the anchor switch is also in-scope if deemed

      o Forwarding path and signaling management: the function
        that handles mobility management signaling interacts with the
        DMM network elements for managing the forwarding state
        associated with a mobile node's IP traffic.  These two functions
        may or may not be collocated. Furthermore, the forwarding state
        may also be distributed into multiple network elements instead
        of a single network element (e.g., anchor).  Protocol extensions
        or new protocols will be specified to allow the above mentioned
        forwarding path and signalling management.

      o Exposing mobility state to mobile nodes and network nodes:
        define solutions that allow, for example, mobile nodes to select
        either a care-of address or a home address depending on an
        application' mobility needs. In order to enable this
        functionality, the network-side control functions and other
        networking nodes must also be able to exchange appropriate
        control information, as well as to the mobile nodes and their

The working group may decide to extend the current milestones based on
the new information and knowledge gained during working on other
documents listed in the initial milestones. Possible new documents and
milestones must still fit into the overall DMM charter scope as outlined


new-work mailing list