RFC 5886: A Set of Monitoring Tools for Path Computation Element (PCE)-Based Architecture
In plain English — editorial summary, not part of the RFC
A Path Computation Element (PCE)-based architecture has been specified for the computation of Traffic Engineering (TE) Label Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks in the context of single or multiple domains (where a domain refers to a collection of network elements within a common sphere of address management or path computational responsibility such as Interior Gateway Protocol (IGP) areas and Autonomous Systems). Path Computation Clients (PCCs) send computation requests to PCEs, and these may forward the requests to and cooperate with other PCEs forming a "path computation chain". In PCE-based environments, it is thus critical to monitor the state of the path computation chain for troubleshooting and performance monitoring purposes: liveness of each element (PCE) involved in the PCE chain and detection of potential resource contention states and statistics in terms of path computation times are examples of such metrics of interest. This document specifies procedures and extensions to the Path Computation Element Protocol (PCEP) in order to gather such information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5886
- Published
- June 2010
- Authors
- JP. Vasseur; JL. Le Roux; Y. Ikejiri
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5885Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)Updated
June 2010
- RFC 5884Bidirectional Forwarding Detection (BFD) for MPLS Label Switched Paths (LSPs)Updated
June 2010
- RFC 5883Bidirectional Forwarding Detection (BFD) for Multihop PathsCurrent
June 2010
- RFC 5882Generic Application of Bidirectional Forwarding Detection (BFD)Current
June 2010
- RFC 5881Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)Current
June 2010
- RFC 5880Bidirectional Forwarding Detection (BFD)Updated
June 2010
- RFC 5867Building Automation Routing Requirements in Low-Power and Lossy NetworksCurrent
June 2010
- 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?