RFC 5089: IS-IS Protocol Extensions for Path Computation Element (PCE) Discovery
In plain English — editorial summary, not part of the RFC
There are various circumstances where it is highly desirable for a Path Computation Client (PCC) to be able to dynamically and automatically 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 the Interior Gateway Protocol (IGP), or even a server participating passively in the IGP, a simple and efficient way to announce PCEs consists of using IGP flooding. For that purpose, this document defines extensions to the Intermediate System to Intermediate System (IS-IS) routing protocol for the advertisement of PCE Discovery information within an IS-IS area or within the entire IS-IS routing domain. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5089
- Published
- January 2008
- Authors
- JL. Le Roux; JP. Vasseur; Y. Ikejiri; R. Zhang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
- Updated by:
- RFC 9353
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5088OSPF Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 4674Requirements for Path Computation Element (PCE) DiscoveryCurrent
October 2006
- RFC 4657Path Computation Element (PCE) Communication Protocol Generic RequirementsCurrent
September 2006
- RFC 5541Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)Current
June 2009
- RFC 5301Dynamic Hostname Exchange Mechanism for IS-ISUpdated
October 2008
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 5303Three-Way Handshake for IS-IS Point-to-Point AdjacenciesCurrent
October 2008
- RFC 5304IS-IS Cryptographic AuthenticationUpdated
October 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?