Distributed Mobility Anchoring
draft-chan-dmm-distributed-mobility-anchoring-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-04-14
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                                    J. Lee
Expires: October 16, 2015                           Sangmyung University
                                                                 S. Jeon
                                           Instituto de Telecomunicacoes
                                                          April 14, 2015

                     Distributed Mobility Anchoring
            draft-chan-dmm-distributed-mobility-anchoring-02

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 flow.  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 October 16, 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

Chan, et al.            Expires October 16, 2015                [Page 1]
Internet-Draft          mobility anchor switching             April 2015

   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  . . . . . . . . . . . . . . . . .  3
   3.  Anchor Initiation and Switching  . . . . . . . . . . . . . . .  5
     3.1.  Anchoring function in network of attachment  . . . . . . .  5
     3.2.  Anchoring Function not in network of attachment  . . . . .  5
     3.3.  Keeping an IP address  . . . . . . . . . . . . . . . . . .  6
     3.4.  Changing the IP address  . . . . . . . . . . . . . . . . .  7
     3.5.  Moving the IP address  . . . . . . . . . . . . . . . . . .  8
     3.6.  Indirection of a flow  . . . . . . . . . . . . . . . . . .  9
     3.7.  Changing indirection of a flow . . . . . . . . . . . . . . 10
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
   6.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 12
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 12
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14

Chan, et al.            Expires October 16, 2015                [Page 2]
Internet-Draft          mobility anchor switching             April 2015

1.  Introduction

   A key requirement in distributed mobility management [RFC7333] 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
   one relies solely on centralized mobility management.  This may also
   occur when the mobile node has moved such that both the mobile node
Show full document text