%% You should probably cite draft-ietf-bess-bgp-multicast-07 instead of this revision.
@techreport{ietf-bess-bgp-multicast-04,
    number =    {draft-ietf-bess-bgp-multicast-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-multicast/04/},
    author =    {Zhaohui (Jeffrey) Zhang and Lenny Giuliano and Keyur Patel and IJsbrand Wijnands and Mankamana Prasad Mishra and Arkadiy Gulko},
    title =     {{BGP Based Multicast}},
    pagetotal = 28,
    year =      2022,
    month =     jan,
    day =       7,
    abstract =  {This document specifies a BGP address family and related procedures that allow BGP to be used for setting up multicast distribution trees. This document also specifies procedures that enable BGP to be used for multicast source discovery, and for showing interest in receiving particular multicast flows. Taken together, these procedures allow BGP to be used as a replacement for other multicast routing protocols, such as PIM or mLDP. The BGP procedures specified here are based on the BGP multicast procedures that were originally designed for use by providers of Multicast Virtual Private Network service. This document also describes how various signaling mechanisms can be used to set up end-to-end inter-region multiast trees.},
}