[Teas] I-D Action: draft-ietf-teas-pcecc-use-cases-07.txt

internet-drafts@ietf.org Tue, 09 March 2021 07:42 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: teas@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: teas@ietf.org
Message-ID: <161527572068.3018.268579031512863162@ietfa.amsl.com>
Date: Mon, 08 Mar 2021 23:42:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/fVMgMfColkG8vGy3E97MACVk-sc>
Subject: [Teas] I-D Action: draft-ietf-teas-pcecc-use-cases-07.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Traffic Engineering Architecture and Signaling WG of the IETF.

        Title           : The Use Cases for Path Computation Element (PCE) as a Central Controller (PCECC).
        Authors         : Zhenbin (Robin) Li
                          Dhruv Dhody
                          Quintin Zhao
                          King Ke
                          Boris Khasanov
                          Luyuan Fang
                          Chao Zhou
                          Boris Zhang
                          Artem Rachitskiy
                          Anton Gulida
	Filename        : draft-ietf-teas-pcecc-use-cases-07.txt
	Pages           : 35
	Date            : 2021-03-08

Abstract:
   The Path Computation Element (PCE) is a core component of a Software-
   Defined Networking (SDN) system.  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).

   SDN has a broader applicability than signaled MPLS traffic-engineered
   (TE) networks, and the PCE may be used to determine paths in a range
   of use cases including static LSPs, segment routing (SR), Service
   Function Chaining (SFC), and most forms of a 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 describes general considerations for PCECC deployment
   and examines its applicability and benefits, as well as its
   challenges and limitations, through a number of use cases.  PCEP
   extensions required for stateful PCE usage are covered in separate
   documents.

   This is a living document to catalog the use cases for PCECC.  There
   is currently no intention to publish this work as an RFC.  [Update:
   Chairs are evaluating if the document should be published instead.]



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-pcecc-use-cases/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-teas-pcecc-use-cases-07
https://datatracker.ietf.org/doc/html/draft-ietf-teas-pcecc-use-cases-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-teas-pcecc-use-cases-07


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/

[Teas] I-D Action: draft-ietf-teas-pcecc-use-case… internet-drafts