Mobility-aware Floating Anchor (MFA)
draft-gundavelli-dmm-mfa-01

Document Type Active Internet-Draft (individual)
Last updated 2018-09-19
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DMM WG                                                     S. Gundavelli
Internet-Draft                                                     Cisco
Intended status: Standards Track                              M. Liebsch
Expires: March 23, 2019                                              NEC
                                                           S. Matsushima
                                                                SoftBank
                                                      September 19, 2018

                  Mobility-aware Floating Anchor (MFA)
                    draft-gundavelli-dmm-mfa-01.txt

Abstract

   IP mobility protocols are designed to allow a mobile node to remain
   reachable while moving around in the network.  The currently deployed
   mobility management protocols are anchor-based approaches, where a
   mobile node's IP sessions are anchored on a central node.  The mobile
   node's IP traffic enters and exits from this anchor node and it
   remains as the control point for all subscriber services.  This
   architecture based on fixed IP anchors comes with some complexity and
   there is some interest from the mobile operators to eliminate the use
   of fixed anchors, and other residual elements such as the overlay
   tunneling that come with it.

   This document describes a new approach for realizing a mobile user-
   plane that does not require fixed IP anchors.  The architectural-
   basis for this approach is the separation of control and user plane,
   and the use of programmability constructs of the user-plane for
   traffic steering.  This approach is referred to as, Mobility-aware
   Floating Anchor (MFA).

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 http://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."

   This Internet-Draft will expire on March 23, 2019.

Gundavelli, et al.       Expires March 23, 2019                 [Page 1]
Internet-Draft                     MFA                    September 2018

Copyright Notice

   Copyright (c) 2018 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
   (http://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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  4
     2.1.  Conventions  . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1.  The Network Topology Database  . . . . . . . . . . . . . .  9
     3.2.  The Node Location Database . . . . . . . . . . . . . . . .  9
     3.3.  Determination of the Correspondent Node Anchor . . . . . . 10
     3.4.  Traffic Steering Approaches  . . . . . . . . . . . . . . . 10
     3.5.  Mobile Node Attachment Triggers  . . . . . . . . . . . . . 12
     3.6.  Programming the User-plane . . . . . . . . . . . . . . . . 12
   4.  Life of a Mobile Node in a MFA Domain  . . . . . . . . . . . . 14
     4.1.  MN's Initial Attachment to a MFA Domain  . . . . . . . . . 15
     4.2.  MN's Roaming within the MFA Domain . . . . . . . . . . . . 17
     4.3.  Traffic Steering State Removal . . . . . . . . . . . . . . 20
     4.4.  Mobile Node's new IP flows . . . . . . . . . . . . . . . . 21
   5.  MFA in 5G System Architecture  . . . . . . . . . . . . . . . . 21
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 23
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 23
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 23
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 23
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 23
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
Show full document text