Distributed Mobility Anchoring
RFC 8818

Document Type RFC - Informational (October 2020; No errata)
Authors Anthony Chan  , Xinpeng Wei  , Jong-Hyouk Lee  , Seil Jeon  , Carlos Bernardos 
Last updated 2020-10-19
Replaces draft-chan-dmm-distributed-mobility-anchoring
Stream IETF stream
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Dapeng Liu
Shepherd write-up Show (last changed 2020-02-14)
IESG IESG state RFC 8818 (Informational)
Action Holders
Consensus Boilerplate Yes
Telechat date
Responsible AD Suresh Krishnan
Send notices to Dapeng Liu <maxpassion@gmail.com>
IANA IANA review state Version Changed - Review Needed
IANA action state No IANA Actions

Internet Engineering Task Force (IETF)                      H. Chan, Ed.
Request for Comments: 8818                                          CIHE
Category: Informational                                           X. Wei
ISSN: 2070-1721                                      Huawei Technologies
                                                                  J. Lee
                                                       Sejong University
                                                                 S. Jeon
                                                 Sungkyunkwan University
                                                      CJ. Bernardos, Ed.
                                                            October 2020

                     Distributed Mobility Anchoring


   This document defines distributed mobility anchoring in terms of the
   different configurations and functions to provide IP mobility
   support.  A network may be configured with distributed mobility
   anchoring functions for both network-based or host-based mobility
   support, depending on the network's needs.  In a distributed mobility
   anchoring environment, multiple anchors are available for mid-session
   switching of an IP prefix anchor.  To start a new flow or to handle a
   flow not requiring IP session continuity as a mobile node moves to a
   new network, the flow can be started or restarted using an IP address
   configured from the new IP prefix anchored to the new network.  If
   the flow needs to survive the change of network, there are solutions
   that can be used to enable IP address mobility.  This document
   describes different anchoring approaches, depending on the IP
   mobility needs, and how this IP address mobility is handled by the

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Conventions and Terminology
   3.  Distributed Mobility Anchoring
     3.1.  Configurations for Different Networks
       3.1.1.  Network-Based DMM
       3.1.2.  Client-Based DMM
   4.  IP Mobility Handling in Distributed Anchoring Environments:
           Mobility Support Only When Needed
     4.1.  Nomadic Case
     4.2.  Mobility Case with Traffic Redirection
     4.3.  Mobility Case with Anchor Relocation
   5.  Security Considerations
   6.  IANA Considerations
   7.  References
     7.1.  Normative References
     7.2.  Informative References
   Authors' Addresses

1.  Introduction

   A key requirement in distributed mobility management (DMM) [RFC7333]
   is to enable traffic to avoid traversing a single mobility anchor far
   from an optimal route.  This document defines different
   configurations, functional operations, and parameters for distributed
   mobility anchoring and explains how to use them to avoid
   unnecessarily long routes when a mobile node moves.

   Other distributed mobility management documents already address
   source address selection [RFC8653] and control-plane and data-plane
   signaling [FPC-DMM-PROTOCOL].  A number of distributed mobility
   solutions have also been proposed, for example, in [DMM-DMA],

   Distributed mobility anchoring employs multiple anchors in the data
   plane.  In general, control-plane functions may be separated from
   data-plane functions and be centralized but may also be co-located
   with the data-plane functions at the distributed anchors.  Different
   configurations of distributed mobility anchoring are described in
Show full document text