%% You should probably cite draft-ietf-pce-interas-pcecp-reqs instead of this I-D.
@techreport{leroux-pce-pcecp-interarea-reqs-00,
    number =    {draft-leroux-pce-pcecp-interarea-reqs-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-leroux-pce-pcecp-interarea-reqs/00/},
    author =    {Jean-Louis Le Roux},
    title =     {{PCE Communication Protocol (PCECP) specific requirements for Inter-Area (G)MPLS Traffic Engineering}},
    pagetotal = 19,
    year =      2005,
    month =     oct,
    day =       17,
    abstract =  {For scalability purposes a network may comprise multiple IGP areas. An inter-area TE-LSP is an LSP that transits through at least two IGP areas. In a multi-area network, topology visibility remains local to a given area, and a head-end LSR cannot compute alone an inter-area shortest constrained path. One key application of the Path Computation Element (PCE) architecture is the computation of inter- area TE-LSP paths. In this context, this document lists a detailed set of PCE Communication Protocol (PCECP) specific requirements for support of inter-area TE-LSP path computation. It complements generic requirements for a PCE Communication Protocol.},
}