Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Updated by:

RFC 9353

Authors:

JL. Le Roux, Ed.
JP. Vasseur, Ed.
Y. Ikejiri
R. Zhang

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

There are various circumstances where it is highly desirable for aPath Computation Client (PCC) to be able to dynamically andautomatically discover a set of Path Computation Elements (PCEs),along with information that can be used by the PCC for PCE selection.When the PCE is a Label Switching Router (LSR) participating in theInterior Gateway Protocol (IGP), or even a server participatingpassively in the IGP, a simple and efficient way to announce PCEsconsists of using IGP flooding. For that purpose, this documentdefines extensions to the Intermediate System to Intermediate System(IS-IS) routing protocol for the advertisement of PCE Discoveryinformation within an IS-IS area or within the entire IS-IS routingdomain. [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.