DMM Deployment Models and Architectural Considerations
draft-ietf-dmm-deployment-models-01

Document Type Active Internet-Draft (dmm WG)
Last updated 2017-02-21
Replaces draft-wt-dmm-deployment-models
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DMM WG                                                     S. Gundavelli
Internet-Draft                                                     Cisco
Intended status: Informational                                   S. Jeon
Expires: August 25, 2017                         Sungkyunkwan University
                                                       February 21, 2017

         DMM Deployment Models and Architectural Considerations
                draft-ietf-dmm-deployment-models-01.txt

Abstract

   This document identifies the deployment models for Distributed
   Mobility Management architecture.

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 August 25, 2017.

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

Gundavelli & Jeon        Expires August 25, 2017                [Page 1]
Internet-Draft            DMM Deployment Models            February 2017

Table of Contents

   1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions and Terminology  . . . . . . . . . . . . . . . . .  3
     2.1.  Conventions  . . . . . . . . . . . . . . . . . . . . . . .  3
     2.2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  DMM Architectural Overview . . . . . . . . . . . . . . . . . .  4
     3.1.  DMM Service Primitives . . . . . . . . . . . . . . . . . .  4
     3.2.  DMM Functions and Interfaces . . . . . . . . . . . . . . .  5
       3.2.1.  Home Control-Plane Anchor (H-CPA): . . . . . . . . . .  5
       3.2.2.  Home Data-Plane Anchor (H-DPA):  . . . . . . . . . . .  6
       3.2.3.  Access Control Plane Node (Access-CPN) . . . . . . . .  6
       3.2.4.  Access Data Plane Node (Access-DPN)  . . . . . . . . .  6
       3.2.5.  DMM Function Mapping to other Architectures  . . . . .  6
   4.  Deployment Models  . . . . . . . . . . . . . . . . . . . . . .  7
     4.1.  Model-1: Split Home Anchor Mode  . . . . . . . . . . . . .  7
     4.2.  Model-2: Seperated Control and User Plane Mode . . . . . .  8
     4.3.  Model-3: Centralized Control Plane Mode  . . . . . . . . .  9
     4.4.  Model-4: Data Plane Abstraction Mode . . . . . . . . . . . 10
     4.5.  On-Demand Control Plane Orchestration Mode . . . . . . . . 11
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  Work Team  . . . . . . . . . . . . . . . . . . . . . . . . . . 13
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 14
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

Gundavelli & Jeon        Expires August 25, 2017                [Page 2]
Internet-Draft            DMM Deployment Models            February 2017

1.  Overview

   One of the key aspects of the Distributed Mobility Management (DMM)
   architecture is the separation of control plane (CP) and data plane
   (DP) functions of a network element.  While data plane elements
   continue to reside on customized networking hardware, the control
   plane resides as a software element in the cloud.  This is usually
   referred to as CP-DP separation and is the basis for the IETF's DMM
   Architecture.  This approach of centralized control plane and
   distributed data plane allows elastic scaling of control plane and
Show full document text