Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

A. Farrel, Ed.
Q. Zhao, Ed.
Z. Li
C. Zhou

Stream:

IETF

Source:

teas (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 8283

Abstract

The Path Computation Element (PCE) is a core component of Software-Defined Networking (SDN) systems. It can compute optimal paths fortraffic across a network and can also update the paths to reflectchanges 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 PathComputation 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 rangeof use cases including static LSPs, segment routing, Service FunctionChaining (SFC), and most forms of a routed or switched network. Itis, therefore, reasonable to consider PCEP as a control protocol foruse in these environments to allow the PCE to be fully enabled as acentral controller.

This document briefly introduces the architecture for PCE as acentral controller, examines the motivations and applicability forPCEP as a control protocol in this environment, and introduces theimplications for the protocol. A PCE-based central controller cansimplify the processing of a distributed control plane by blending itwith elements of SDN and without necessarily completely replacing it.

This document does not describe use cases in detail and does notdefine protocol extensions: that work is left for other documents.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.