%% You should probably cite rfc5376 instead of this I-D.
@techreport{ietf-pce-interas-pcecp-reqs-06,
    number =    {draft-ietf-pce-interas-pcecp-reqs-06},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-pce-interas-pcecp-reqs/06/},
    author =    {Kenji Kumaki and Raymond Zhang and Dr. Nabil N. Bitar},
    title =     {{Inter-AS Requirements for the Path Computation Element Communication Protocol (PCECP)}},
    pagetotal = 14,
    year =      2008,
    month =     may,
    day =       7,
    abstract =  {Multiprotocol Label Switching Traffic Engineered (MPLS TE) Label Switched Paths (LSPs) may be established wholly within an Autonomous System (AS) or may cross AS boundaries. The Path Computation Element (PCE) is a component that is capable of computing constrained paths for (G)MPLS TE LSPs. The PCE Communication Protocol (PCECP) is defined to allow communication between Path Computation Clients (PCCs) and PCEs, as well as between PCEs. The PCECP is used to request constrained paths and to supply computed paths in response. Generic requirements for the PCECP are set out in "Path Computation Element (PCE) Communication Protocol Generic Requirements", RFC 4657. This document extends those requirements to cover the use of PCECP in support of inter-AS MPLS TE. This memo provides information for the Internet community.},
}