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

internet-drafts@ietf.org Mon, 27 May 2024 17:49 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
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171683218239.55989.5277780973414165494@ietfa.amsl.com>
Date: Mon, 27 May 2024 10:49:42 -0700
Message-ID-Hash: Y6LVAQ3QVQJJQGEAINQCQRBACMD7IWQG
CC: teas@ietf.org
Reply-To: teas@ietf.org
Subject: [Teas] I-D Action: draft-ietf-teas-pcecc-use-cases-16.txt
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/T-zFaVv8KeA2i78edCQ66wTIG6o>

Internet-Draft draft-ietf-teas-pcecc-use-cases-16.txt is now available. It is
a work item of the Traffic Engineering Architecture and Signaling (TEAS) WG of
the IETF.

   Title:   Use Cases for a PCE as a Central Controller (PCECC)
   Authors: Zhenbin (Robin) Li
            Dhruv Dhody
            Quintin Zhao
            King He
            Boris Khasanov
   Name:    draft-ietf-teas-pcecc-use-cases-16.txt
   Pages:   45
   Dates:   2024-05-27

Abstract:

   The PCE is a core component of a Software-Defined Networking (SDN)
   system.  It can be used to compute optimal paths for network traffic
   and update existing paths to reflect changes in the network or
   traffic demands.  PCE was developed to derive traffic-engineered
   paths in MPLS networks, which are supplied to the head end of the
   paths using the Path Computation Element Communication Protocol
   (PCEP).

   SDN has much 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.

   A PCE as a Central Controller (PCECC) can simplify the processing of
   a distributed control plane by blending it with elements of SDN
   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
   are required for the PCECC use cases are covered in separate
   documents.

The IETF datatracker status page for this Internet-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-16

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

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

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