Distributed Mobility Anchoring
draft-ietf-dmm-distributed-mobility-anchoring-13

Document Type Active Internet-Draft (dmm WG)
Last updated 2019-06-12 (latest revision 2019-03-26)
Replaces draft-chan-dmm-distributed-mobility-anchoring
Stream IETF
Intended RFC status Informational
Formats plain text pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Other - see Comment Log
Document shepherd Dapeng Liu
Shepherd write-up Show (last changed 2019-04-19)
IESG IESG state AD Evaluation
Consensus Boilerplate Unknown
Telechat date
Responsible AD Suresh Krishnan
Send notices to Dapeng Liu <maxpassion@gmail.com>
DMM                                                         H. Chan, Ed.
Internet-Draft                                                    X. Wei
Intended status: Informational                       Huawei Technologies
Expires: September 27, 2019                                       J. Lee
                                                    Sangmyung University
                                                                 S. Jeon
                                                 Sungkyunkwan University
                                                      CJ. Bernardos, Ed.
                                                                    UC3M
                                                          March 26, 2019

                     Distributed Mobility Anchoring
            draft-ietf-dmm-distributed-mobility-anchoring-13

Abstract

   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 according to the needs of mobility support.  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 re-started 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
   network.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Chan, et al.           Expires September 27, 2019               [Page 1]
Internet-Draft       distributed mobility anchoring           March 2019

   This Internet-Draft will expire on September 27, 2019.

Copyright Notice

   Copyright (c) 2019 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
   2.  Conventions and Terminology . . . . . . . . . . . . . . . . .   4
   3.  Distributed Mobility Anchoring  . . . . . . . . . . . . . . .   5
     3.1.  Configurations for Different Networks . . . . . . . . . .   5
       3.1.1.  Network-based DMM . . . . . . . . . . . . . . . . . .   5
       3.1.2.  Client-based DMM  . . . . . . . . . . . . . . . . . .   6
   4.  IP Mobility Handling in Distributed Anchoring Environments -
       Mobility Support Only When Needed . . . . . . . . . . . . . .   7
     4.1.  Nomadic case (no need of IP mobility): Changing to new IP
           prefix/address  . . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Mobility case, traffic redirection  . . . . . . . . . . .  10
     4.3.  Mobility case, anchor relocation  . . . . . . . . . . . .  12
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   7.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  14
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   A key requirement in distributed mobility management [RFC7333] is to
   enable traffic to avoid traversing a single mobility anchor far from
   an optimal route.  This document defines different configurations,
Show full document text