%% You should probably cite draft-lzj-mpls-receiver-driven-multicast-rsvp-te-03 instead of this revision.
@techreport{lzj-mpls-receiver-driven-multicast-rsvp-te-02,
    number =    {draft-lzj-mpls-receiver-driven-multicast-rsvp-te-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-lzj-mpls-receiver-driven-multicast-rsvp-te/02/},
    author =    {Richard Li and Quintin Zhao and Christian Jacquenet and Robert Tao and Telus Communications},
    title =     {{Receiver-Driven Multicast Traffic-Engineered Label-Switched Paths}},
    pagetotal = 32,
    year =      2012,
    month =     oct,
    day =       22,
    abstract =  {This document describes the receiver-driven RSVP-TE P2MP LSP signaling protocol (mRSVP-TE) which is an extension to the Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the computation and establishment of Receiver-Driven Traffic-Engineered point-to-multipoint (P2MP) and multipoint-to-multipoint (MP2MP) Label Switched Paths (LSPs) in Multi-Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The document also describes the mRSVP-TE extensions and procedures for the interworking between mRSVP-TE and the Protocol Independent Multicast (PIM) protocol.},
}