Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 23
- Abstract
- The computation of one or a set of Traffic Engineering Label Switched Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks is subject to a set of one or more specific optimization criteria, referred to as objective functions (e.g., minimum cost path, widest path, etc.). In the Path Computation Element (PCE) architecture, a Path Computation Client (PCC) may want a path to be computed for one or more TE LSPs according to a specific objective function. Thus, the PCC needs to instruct the PCE to use the correct objective function. Furthermore, it is possible that not all PCEs support the same set of objective functions; therefore, it is useful for the PCC to be able to automatically discover the set of objective functions supported by each PCE. This document defines extensions to the PCE communication Protocol (PCEP) to allow a PCE to indicate the set of objective functions it supports. Extensions are also defined so that a PCC can indicate in a path computation request the required objective function, and a PCE can report in a path computation reply the objective function that was used for path computation. This document defines objective function code types for six objective functions previously listed in the PCE requirements work, and provides the definition of four new metric types that apply to a set of synchronized requests. [STANDARDS-TRACK]
- Publication Date
- 2009-06-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5541- Link
- https://doi.org/10.17487/RFC5541
- Author(s)
- Jean-Louis Le RouxJP VasseurYoung Lee
- Keyword(s)
- PCE
Latest version of IETF RFC 5541
Document Versions — IETF RFC 5541
-
▶ IETF RFC 5541 (2009-06-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 4655 [Active*]
- IETF RFC 5440 [Active*]
Bibliographic Reference(s)
- Lee, Y., Le Roux, JL., King, D., and E. Oki, "Path Computation Element Communication Protocol (PCEP) Requirements and Protocol Extensions in Support of Global Concurrent Optimization", Work in Progress, March 2009. EXTERNAL
- Koushik, K., and E. Stephan, "PCE Communication Protocol (PCEP) Management Information Base", Work in Progress, January 2009. EXTERNAL
- IETF RFC 4657 [Active*]
- IETF RFC 4674 [Active*]
- IETF RFC 5088 [Active*]
- IETF RFC 5089 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5511 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5541.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5541, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC5541
Snippet:
IETF RFC 5541, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC5541
HTML (ISO 690 compliant)
Preview:
IETF RFC 5541, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP). Available at https://doi.org/10.17487/RFC5541
Snippet:
<span class="citation"><cite>IETF RFC 5541</cite>, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP). Available at <a href="https://doi.org/10.17487/RFC5541" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5541</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5541, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
doi: 10.17487/RFC5541
url: https://doi.org/10.17487/RFC5541
doi: 10.17487/RFC5541
url: https://doi.org/10.17487/RFC5541
Snippet:
<li> <cite id="bib-rfc5541">IETF RFC 5541</cite>, Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP) <span class="doi">10.17487/RFC5541</span> </li>
Referenced By
- IETF RFC 5557 [Active*]
- IETF RFC 6805 [Active*]
- IETF RFC 9522 [Active*]