[Pce] I-D Action: draft-ietf-pce-pcep-extension-for-pce-controller-04.txt

internet-drafts@ietf.org Mon, 09 March 2020 06:41 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: pce@ietf.org
Message-ID: <158373608934.6850.2434255939024978505@ietfa.amsl.com>
Date: Sun, 08 Mar 2020 23:41:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/CL6xxFNuRoIip3fHEuXTOZQSLX0>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-extension-for-pce-controller-04.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Path Computation Element WG of the IETF.

        Title           : PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs
        Authors         : Quintin Zhao
                          Zhenbin Li
                          Mahendra Singh Negi
                          Shuping Peng
                          Chao Zhou
	Filename        : draft-ietf-pce-pcep-extension-for-pce-controller-04.txt
	Pages           : 34
	Date            : 2020-03-08

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), which are supplied to the head end of the LSP using the Path
   Computation Element Communication Protocol (PCEP).  But SDN has a
   broader applicability than signaled (G)MPLS traffic-engineered (TE)
   networks, and the PCE may be used to determine paths in a range of
   use cases.  PCEP has been proposed as a control protocol for use in
   these environments to allow the PCE to be fully enabled as a central
   controller.

   A PCE-based central controller (PCECC) can simplify the processing of
   a distributed control plane by blending it with elements of SDN and
   without necessarily completely replacing it.  Thus, the LSP can be
   calculated/setup/initiated and the label forwarding entries can also
   be downloaded through a centralized PCE server to each network
   devices along the path while leveraging the existing PCE technologies
   as much as possible.

   This document specifies the procedures and PCEP protocol extensions
   for using the PCE as the central controller.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-pce-pcep-extension-for-pce-controller-04
https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-extension-for-pce-controller-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-pce-pcep-extension-for-pce-controller-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Pce] I-D Action: draft-ietf-pce-pcep-extension-f… internet-drafts