%% You should probably cite draft-ietf-mpls-rsvp-te-hsmp-lsp instead of this I-D.
@techreport{jjb-mpls-rsvp-te-hsmp-lsp-03,
    number =    {draft-jjb-mpls-rsvp-te-hsmp-lsp-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-jjb-mpls-rsvp-te-hsmp-lsp/03/},
    author =    {Lizhong Jin and Frederic JOUNAY and Manav Bhatia},
    title =     {{Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Hub and Spoke Multipoint Label Switched Paths (LSPs)}},
    pagetotal = 15,
    year =      2013,
    month =     feb,
    day =       24,
    abstract =  {In Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) environment, the RSVP-TE based Point-to-Multipoint (P2MP) LSP allows traffic to transmit from root to leaf node, but there is no co-routed reverse path for traffic from leaf to root node. There are applications that require bi-directional, co-routed and guaranteed communication from a root node to several leaf nodes in a hub-and- spoke fashion. This draft defines such a Hub and Spoke Multipoint LSP (HSMP LSP) and defines protocol extensions to P2MP RSVP-TE to setup such LSPs.},
}