An Architecture for Use of PCE and PCEP in a Network with Central Control
draft-ietf-teas-pce-central-control-05

Document Type Active Internet-Draft (teas WG)
Last updated 2017-09-05 (latest revision 2017-09-04)
Replaces draft-zhao-teas-pce-control-function
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Vishnu Beeram
Shepherd write-up Show (last changed 2017-06-27)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to Vishnu Beeram <vbeeram@juniper.net>
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state MISSREF
TEAS Working Group                                        A. Farrel, Ed.
Internet-Draft                                          Juniper Networks
Intended status: Informational                              Q. Zhao, Ed.
Expires: March 8, 2018                                             R. Li
                                                     Huawei Technologies
                                                                 C. Zhou
                                                           Cisco Systems
                                                       September 4, 2017

   An Architecture for Use of PCE and PCEP in a Network with Central
                                Control
                 draft-ietf-teas-pce-central-control-05

Abstract

   The Path Computation Element (PCE) is a core component of Software
   Defined Networking (SDN) systems.  It can compute optimal paths for
   traffic across a network and can also update the paths to reflect
   changes in the network or traffic demands.

   PCE was developed to derive paths for MPLS Label Switched Paths
   (LSPs) supplying them to the head end of the LSP using the Path
   Computation Element Communication Protocol (PCEP).

   SDN has a broader applicability than signaled MPLS traffic engineered
   networks, and the PCE may be used to determine paths in a range of
   use cases including static LSPs, segment routing, service function
   chaining, and most forms of routed or switched network.  It is,
   therefore, reasonable to consider PCEP as a control protocol for use
   in these environments to allow the PCE to be fully enabled as a
   central controller.

   This document briefly introduces the architecture for PCE as a
   central controller, examines the motivations and applicability for
   PCEP as a control protocol in this environment, and introduces the
   implications for the protocol.  A PCE-based central controller can
   simplify the processing of distributed control plane by blending it
   with elements of SDN and without necessarily completely replacing it.

   This document does not describe use cases in detail and does not
   define protocol extensions: that work is left for other documents.

Status of This Memo

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

Farrel, et al.            Expires March 8, 2018                 [Page 1]
Internet-Draft             PCE-CC Architecture            September 2017

   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 March 8, 2018.

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Resilience and Scaling  . . . . . . . . . . . . . . . . .   7
       2.1.1.  Partitioned Network . . . . . . . . . . . . . . . . .   8
       2.1.2.  Multiple Parallel Controllers . . . . . . . . . . . .   9
       2.1.3.  Hierarchical Controllers  . . . . . . . . . . . . . .  12
   3.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.1.  Technology-Oriented Applicability . . . . . . . . . . . .  14
       3.1.1.  Applicability to Control Plane Operated Networks  . .  14
       3.1.2.  Static LSPs in MPLS . . . . . . . . . . . . . . . . .  14
       3.1.3.  MPLS Multicast  . . . . . . . . . . . . . . . . . . .  15
       3.1.4.  Transport SDN . . . . . . . . . . . . . . . . . . . .  15
       3.1.5.  Segment Routing . . . . . . . . . . . . . . . . . . .  15
       3.1.6.  Service Function Chaining . . . . . . . . . . . . . .  16
     3.2.  High-Level Applicability  . . . . . . . . . . . . . . . .  16
Show full document text