%% You should probably cite draft-ietf-pce-monitoring instead of this I-D.
@techreport{vasseur-pce-monitoring-03,
    number =    {draft-vasseur-pce-monitoring-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-vasseur-pce-monitoring/03/},
    author =    {JP Vasseur},
    title =     {{A set of monitoring tools for Path Computation Element based Architecture}},
    pagetotal = 20,
    year =      2007,
    month =     may,
    day =       11,
    abstract =  {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 is referred to as a collection of network elements within a common sphere of address management or path computational responsibility such as IGP areas and Autonomous Systems). 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, detection of potential resource contention states, statistics in term 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.},
}