%% You should probably cite draft-dhody-pce-pcep-p2mp-per-destination-12 instead of this revision.
@techreport{dhody-pce-pcep-p2mp-per-destination-02,
    number =    {draft-dhody-pce-pcep-p2mp-per-destination-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-p2mp-per-destination/02/},
    author =    {Dhruv Dhody and Udayasree Palle},
    title =     {{Supporting explicit-path per destination in Path Computation Element Communication Protocol (PCEP) P2MP Path Request Message.}},
    pagetotal = 15,
    year =      2012,
    month =     aug,
    day =       17,
    abstract =  {The ability to determine paths of point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) is one the key requirements for Path Computation Element (PCE). {[}RFC6006{]} and {[}PCE-P2MP-PROCEDURES{]} describes these mechanisms for intra and inter domain environment. Explicit Path in this document refers to the configured list of network elements that MUST be traversed or MUST be excluded in the final path computation. This should not be confused with the RSVP terminology. Network elements can further be strict or loose hop. This document describes extensions to the PCE communication Protocol (PCEP) to define explicit-path per destination in P2MP context.},
}