%% You should probably cite draft-ietf-pals-vpls-pim-snooping instead of this I-D.
@techreport{ietf-l2vpn-vpls-pim-snooping-04,
    number =    {draft-ietf-l2vpn-vpls-pim-snooping-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-l2vpn-vpls-pim-snooping/04/},
    author =    {Olivier Dornon and Jayant Kotalwar and Venu Hemige and Ray (Lei) Qiu and Zhaohui (Jeffrey) Zhang},
    title =     {{PIM Snooping over VPLS}},
    pagetotal = 39,
    year =      2013,
    month =     jul,
    day =       12,
    abstract =  {This document describes the procedures and recommendations for VPLS PEs to facilitate replication of multicast traffic to only certain ports (behind which there are interested PIM routers and/or IGMP hosts) via PIM Snooping and PIM Proxy. With PIM Snooping, PEs passively listen to certain PIM control messages to build control and forwarding states while transparently flooding those messages. With PIM Proxy, PEs do not flood PIM Join/ Prune messages but only generate their own and send out of certain ports, based on the control states built from downstream Join/Prune messages. PIM Proxy is required when PIM Join suppression is enabled on the CE devices and useful to reduce PIM control traffic in a VPLS domain. The document also describes PIM Relay, which can be viewed as light- weight proxy, where all downstream Join/Prune messages are simply forwarded out of certain ports but not flooded to avoid triggering PIM Join suppression on CE devices.},
}