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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-10-15
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                                                    X. Wei
Intended status: Informational                       Huawei Technologies
Expires: April 17, 2016                                           J. Lee
                                                    Sangmyung University
                                                                 S. Jeon
                                           Instituto de Telecomunicacoes
                                                              F. Templin
                                          Boeing Research and Technology
                                                        October 15, 2015

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

Abstract

   This document defines the mobility management solutions in the
   context of a distributed mobility management deployment.  It consider
   the problem of assigning a mobility anchor 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 April 17, 2016.

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

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

   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 . . . . . . . . . . . . . . . . .   3
   3.  IP prefix/address anchored in current network of attachment .   4
     3.1.  Changing to the new IP prefix/address . . . . . . . . . .   5
     3.2.  Moving the IP prefix/address anchor to the new network  .   8
       3.2.1.  Centralized control plane . . . . . . . . . . . . . .   9
       3.2.2.  Hierarchical network  . . . . . . . . . . . . . . . .  12
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  14
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  15
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

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.  Recall that distributed mobility management
   solutions do not make use of centrally deployed mobility anchor
   [Paper-Distributed.Mobility].  As such, a flow SHOULD be able to have
   its traffic changing from traversing one mobility anchor to
   traversing another mobility anchor as the mobile node moves, or when
   changing operation and management (OAM) requirements call for
   mobility anchor switching, thus avoiding non-optimal routes.  This
   draft proposes distributed mobility anchoring solutions.

   The needs of IP-layer mobility support are diverse so that the use of
   distributed anchoring may differ according to the needs.

   A mobile node (MN) may be running a flow with its correspondent node
   (CN) for which the source IP address of this flow belongs to MN's
   network.  That is, it is anchored to an access router (anchor)
   belonging to MN's network.  When there are multiple anchors, the flow
   may need to select the anchor when it is initiated (Section 3).
   Using an anchor in MN's network has the advantage that the packets
Show full document text