Anchorless Mobility Management
draft-wei-dmm-anchorless-mm-01

Document Type Active Internet-Draft (individual)
Last updated 2017-05-31
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)
INTERNET-DRAFT                                                 X.Wei Ed.
Intended Status: Proposed Standard                                F.Yang
Expires: December 3, 2017                            Huawei Technologies
                                                            June 1, 2017

                    Anchorless Mobility Management 
                     draft-wei-dmm-anchorless-mm-01

Abstract

   This memo discusses anchor-less mobility management based on
   ID/Locator split scheme, especially for VM handoff scenario in MEC
   network.

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 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
 

J.Wei                   Expires December 3, 2017                [Page 1]
INTERNET DRAFT              <Document Title>                June 1, 2017

   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
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2  Mobility Management Gap Analysis  . . . . . . . . . . . . . . .  4
   3  Mobility Solution Based on ID/Locater Split . . . . . . . . . .  5
   4  Relations with Existing DMM Solutions . . . . . . . . . . . . .  9
   5  Security Considerations . . . . . . . . . . . . . . . . . . . .  9
   6  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  9
   7  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1  Normative References  . . . . . . . . . . . . . . . . . . . 10
     7.2  Informative References  . . . . . . . . . . . . . . . . . . 10
   Contributors:  . . . . . . . . . . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10

 

J.Wei                   Expires December 3, 2017                [Page 2]
INTERNET DRAFT              <Document Title>                June 1, 2017

1  Introduction

   With the development of network technology, there are more and more
   services sensitive to network latency, for example, interactive VR,
   tactile Internet, remote control, automatic drive etc. Also low
   latency has become an important requirement in 5G network design. For
   service with low latency requirements, the network needs to meet its
   end-to-end latency requirements.

   The MEC (Multi-access Edge Computing) sinks computing and storage
   capacity to the edge of the network. The MEC server is deployed at
   the edge of the network and applications could be deployed in the MEC
   server. This allows the MN to access the required services in close
   proximity without having to traverse through the core network,
   thereby reducing the end-to-end RTT, and satisfying latency
   requirements. Usually, MN and MEC server are under the same operator
   network. One of the basic MEC deployment scenarios is shown in Figure
   1:

   +--+           +---+       +---+     +----------+
   |MN|-----------|UP1|       |UP3|-----|MEC Server|
   +--+           +---+       +---+     +----------+

                  +---+       +---+     +----------+
                  |UP2|       |UP4|-----|MEC Server|
                  +---+       +---+     +----------+

   UP: User Plane function

                 Figure 1: MEC Deployment Architecture

   In order to meet the low latency requirements of network services, an
   alternative approach is to deploy services with low latency
Show full document text