Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

INFORMATIONAL

Authors:

Z. Li
D. Dhody
Q. Zhao
Z. Ke
B. Khasanov

Stream:

IETF

Source:

teas (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9689

Discuss this RFC: Send questions or comments to the mailing listteas@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9689

Abstract

The PCE is a core component of a Software-Defined Networking (SDN)system. It can be used to compute optimal paths for network trafficand update existing paths to reflect changes in the network ortraffic demands. The PCE was developed to derive Traffic Engineering(TE) paths in MPLS networks, which are supplied to the headend of thepaths using the Path Computation Element Communication Protocol(PCEP).

SDN has much broader applicability than signalled MPLS TE networks,and the PCE may be used to determine paths in a range of use casesincluding static Label-Switched Paths (LSPs), Segment Routing (SR),Service Function Chaining (SFC), and most forms of a routed orswitched network. Therefore, it is reasonable to consider PCEP as acontrol protocol for use in these environments to allow the PCE to befully enabled as a central controller.

A PCE as a Central Controller (PCECC) can simplify the processing ofa distributed control plane by blending it with elements of SDNwithout necessarily completely replacing it. This document describesgeneral considerations for PCECC deployment and examines itsapplicability and benefits, as well as its challenges andlimitations, through a number of use cases. PCEP extensions, whichare required for the PCECC use cases, are covered in separatedocuments.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.