Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

S. Yasukawa
A. Farrel

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

The Path Computation Element (PCE) provides path computationfunctions in support of traffic engineering in Multiprotocol LabelSwitching (MPLS) and Generalized MPLS (GMPLS) networks.

Extensions to the MPLS and GMPLS signaling and routing protocols havebeen made in support of point-to-multipoint (P2MP) Traffic Engineered(TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks isalready established, and since P2MP TE LSP routes are sometimescomplex to compute, it is likely that PCE will be used for P2MP LSPs.

Generic requirements for a communication protocol between PathComputation Clients (PCCs) and PCEs are presented in RFC 4657, "PathComputation Element (PCE) Communication Protocol GenericRequirements". This document complements the generic requirements andpresents a detailed set of PCC-PCE communication protocolrequirements for point-to-multipoint MPLS/GMPLS traffic engineering.This document is not an Internet Standards Track specification; it ispublished for informational purposes.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.