Enhanced Mobility Anchoring
draft-chan-dmm-distributed-mobility-anchoring-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-03-09
Replaced by draft-ietf-dmm-distributed-mobility-anchoring
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                                                              H. Chan
Internet-Draft                                       Huawei Technologies
Intended status: Informational                             March 9, 2015
Expires: September 10, 2015

                      Enhanced Mobility Anchoring
            draft-chan-dmm-distributed-mobility-anchoring-00

Abstract

   This document defines the mobility management protocol solutions in
   the context of a distributed mobility management deployment.  Such
   solutions consider the problem of assigning a mobility anchor and a
   gateway at the initiation of a session.  In addition, the mid-session
   switching of the mobility anchor in a distributed mobility management
   environment is considered.

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 September 10, 2015.

Copyright Notice

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

Chan                   Expires September 10, 2015               [Page 1]
Internet-Draft          mobility anchor switching             March 2015

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  3
   3.  Anchor Selection and Switching . . . . . . . . . . . . . . . .  5
     3.1.  IP anchoring in network of attachment  . . . . . . . . . .  5
     3.2.  IP anchoring not in network of attachment  . . . . . . . .  6
     3.3.  Changing IP anchoring in mid-session . . . . . . . . . . .  7
     3.4.  Moving IP anchoring in mid-session . . . . . . . . . . . .  7
     3.5.  Anchoring a session  . . . . . . . . . . . . . . . . . . .  8
     3.6.  Changing session anchoring in mid-session  . . . . . . . .  9
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     6.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     6.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chan                   Expires September 10, 2015               [Page 2]
Internet-Draft          mobility anchor switching             March 2015

1.  Introduction

   A key requirement in distributed mobility management
   [I-D.ietf-dmm-requirements] is to enable traffic to avoid traversing
   single mobility anchor far from the optimal route.  Recent
   developments in research and standardization with respect to future
   deployment models call for far more flexibility in network function
   operation and management.  For example, the work on service function
   chaining at the IETF (SFC WG) has already identified a number of use
   cases for data centers.  Although the work in SFC is not primarily
   concerned with mobile networks, the impact on IP-based mobile
   networks is not hard to see as by now most hosts connected to the
   Internet do so over a wireless medium.  For instance, as a result of
   a dynamic re-organization of service chain a non-optimal route
   between mobile nodes may arise if pme relies solely on centralized
   mobility management.  As discussed earlier in the distributed
   mobility management working group (DMM WG) this may also occur when
   the mobile node has moved such that both the mobile node and the
   correspondent node are far from the mobility anchor via which the
   traffic is routed.

   Recall that distributed mobility management solutions do not make use
   of centrally deployed mobility anchor.  As such, an application
   session SHOULD be able to have its traffic passing from one mobility
Show full document text