I-D Action: draft-ietf-teas-pcecc-use-cases-13.txt

internet-drafts@ietf.org Mon, 09 January 2023 04:12 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
Subject: I-D Action: draft-ietf-teas-pcecc-use-cases-13.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: teas@ietf.org
Message-ID: <167323755891.4182.554744996681522955@ietfa.amsl.com>
Date: Sun, 08 Jan 2023 20:12:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/ocT7sZEJ_iFHF4cxYIWjs1a837Y>

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 He
                          Boris Khasanov
  Filename        : draft-ietf-teas-pcecc-use-cases-13.txt
  Pages           : 44
  Date            : 2023-01-08

Abstract:
   The Path Computation Element (PCE) is a core component of a Software-
   Defined Networking (SDN) systems.  It can compute optimal paths for
   traffic across a network and update 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 much broader applicability than signal MPLS traffic-
   engineered (TE) paths, 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.

   A PCE as a 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.  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 which
   required for the PCECC use cases are covered in separate documents.


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

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-teas-pcecc-use-cases-13

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-teas-pcecc-use-cases-13


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts

I-D Action: draft-ietf-teas-pcecc-use-cases-13.txt internet-drafts