Extensions to the Path Computation Element Communication Protocol (PCEP) for Route Exclusions
RFC 5521
Revision differences
Document history
Date | By | Action |
---|---|---|
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The Path Computation Element (PCE) provides functions of path computation in support of traffic engineering (TE) … Received changes through RFC Editor sync (changed abstract to '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]') |
2015-10-14
|
(System) | Notify list changed from pce-chairs@ietf.org, draft-ietf-pce-pcep-xro@ietf.org to (None) |
2009-05-05
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2009-05-05
|
Amy Vezza | [Note]: 'RFC 5521' added by Amy Vezza |
2009-04-28
|
(System) | RFC published |