%% You should probably cite draft-ietf-mpls-mldp-in-band-wildcard-encoding instead of this I-D.
@techreport{wijnands-mpls-mldp-in-band-wildcard-encoding-00,
    number =    {draft-wijnands-mpls-mldp-in-band-wildcard-encoding-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-wijnands-mpls-mldp-in-band-wildcard-encoding/00/},
    author =    {IJsbrand Wijnands and Arkadiy Gulko and Uwe Joorde and Jeff Tantsura},
    title =     {{mLDP in-band signalling Wildcard encoding}},
    pagetotal = 11,
    year =      2013,
    month =     jul,
    day =       8,
    abstract =  {Documents {[}RFC6826{]} and {[}I-D.ietf-l3vpn-mldp-vrf-in-band-signaling{]} define a solution to splice an IP multicast tree together with a multipoint LSP in the global or VRF context. In these drafts the Multipoint Label Distribution Protocol (mLDP) Opaque TLV encodings have been documented for Source specific and Bidir IP multicast trees. For each IP multicast tree a multipoint LSP is created. There are scenarios where it is beneficial to support shared trees and allow aggregation such that fewer multipoint LSPs are created in the network. This document defines wildcard encodings to be used for the Source or Group fields of the existing opaque encodings. With the wildcard encoding it is possible to create a single multipoint LSP that is used to represent *all* sources for a given multicast group or *all* groups for a given source.},
}