RFC 5521: Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
In plain English — editorial summary, not part of the RFC
The Path Computation Element (PCE) provides functions of path computation in support of traffic engineering (TE) in Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. When a Path Computation Client (PCC) requests a PCE for a route, it may be useful for the PCC to specify, as constraints to the path computation, abstract nodes, resources, and Shared Risk Link Groups (SRLGs) that are to be explicitly excluded from the computed route. Such constraints are termed "route exclusions". The PCE Communication Protocol (PCEP) is designed as a communication protocol between PCCs and PCEs. This document presents PCEP extensions for route exclusions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5521
- Published
- April 2009
- Authors
- E. Oki; T. Takeda; A. Farrel
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 5623Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic EngineeringCurrent
September 2009
- RFC 6457PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic EngineeringCurrent
December 2011
- RFC 4558Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification StatementCurrent
June 2006
- RFC 3480Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)Current
February 2003
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 5298Analysis of Inter-Domain Label Switched Path (LSP) RecoveryCurrent
August 2008
- RFC 5862Path Computation Clients (PCC) - Path Computation Element (PCE) Requirements for Point-to-Multipoint MPLS-TECurrent
June 2010
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?