Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

JL. Le Roux
JP. Vasseur
Y. Lee

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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 5541

Abstract

The computation of one or a set of Traffic Engineering Label SwitchedPaths (TE LSPs) in MultiProtocol Label Switching (MPLS) andGeneralized MPLS (GMPLS) networks is subject to a set of one or morespecific optimization criteria, referred to as objective functions(e.g., minimum cost path, widest path, etc.).

In the Path Computation Element (PCE) architecture, a PathComputation Client (PCC) may want a path to be computed for one ormore TE LSPs according to a specific objective function. Thus, thePCC needs to instruct the PCE to use the correct objective function.Furthermore, it is possible that not all PCEs support the same set ofobjective functions; therefore, it is useful for the PCC to be able toautomatically discover the set of objective functions supported byeach PCE.

This document defines extensions to the PCE communication Protocol(PCEP) to allow a PCE to indicate the set of objective functions itsupports. Extensions are also defined so that a PCC can indicate ina path computation request the required objective function, anda PCE can report in a path computation reply the objectivefunction that was used for path computation.

This document defines objective function code types for sixobjective functions previously listed in the PCE requirements work,and provides the definition of four new metric types that apply to aset of synchronized requests. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.