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

internet-drafts@ietf.org Mon, 22 February 2021 02:04 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: <161395949429.10704.280733302878136463@ietfa.amsl.com>
Date: Sun, 21 Feb 2021 18:04:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/WkrrFpGY1SFBg5gMM7mI81ImGgs>
Subject: [Pce] I-D Action: draft-ietf-pce-pcep-extension-pce-controller-sr-01.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) for Segment Routing (SR) MPLS Segment Identifier (SID) Allocation and Distribution.
        Authors         : Zhenbin Li
                          Shuping Peng
                          Mahendra Singh Negi
                          Quintin Zhao
                          Chao Zhou
	Filename        : draft-ietf-pce-pcep-extension-pce-controller-sr-01.txt
	Pages           : 34
	Date            : 2021-02-21

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/set up/initiated and the label forwarding entries can also
   be downloaded through a centralized PCE server to each network device
   along the path while leveraging the existing PCE technologies as much
   as possible.

   This document specifies the procedures and PCEP extensions when a
   PCE-based controller is also responsible for configuring the
   forwarding actions on the routers, in addition to computing the paths
   for packet flows in a segment routing (SR) network and telling the
   edge routers what instructions to attach to packets as they enter the
   network.  PCECC is further enhanced for SR-MPLS SID (Segment
   Identifier) allocation and distribution.


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

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

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


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-p… internet-drafts