%% You should probably cite draft-ietf-pce-stateful-pce-p2mp or draft-palle-pce-stateful-pce-p2mp instead of this I-D.
@techreport{palle-pce-stateful-pce-initiated-p2mp-lsp-01,
    number =    {draft-palle-pce-stateful-pce-initiated-p2mp-lsp-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-palle-pce-stateful-pce-initiated-p2mp-lsp/01/},
    author =    {Udayasree Palle and Dhruv Dhody and Yosuke Tanaka and Yuji Kamite},
    title =     {{PCEP Extensions for PCE-initiated Point-to-Multipoint LSP Setup in a Stateful PCE Model}},
    pagetotal = 11,
    year =      2014,
    month =     feb,
    day =       14,
    abstract =  {The Path Computation Element (PCE) has been identified as an appropriate technology for the determination of the paths of point- to-multipoint (P2MP) TE LSPs. The extensions described in {[}I-D.ietf-pce-stateful-pce{]} provide stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSP) via PCE communication Protocol (PCEP), for a model where the Path Computation Client (PCC) delegates control over one or more locally configured LSPs to the PCE. Further {[}I-D.ietf-pce-pce-initiated-lsp{]} describes the creation and deletion of PCE-initiated LSPs under the stateful PCE model. This document provides extensions required for PCEP so as to enable the usage of a stateful PCE initiation capability in supporting point-to-multipoint (P2MP) TE LSP instantiation.},
}