%% You should probably cite draft-wang-bess-mvpn-upstream-df-selection-10 instead of this revision.
@techreport{wang-bess-mvpn-upstream-df-selection-09,
    number =    {draft-wang-bess-mvpn-upstream-df-selection-09},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-wang-bess-mvpn-upstream-df-selection/09/},
    author =    {Fanghong Duan and Siyu Chen and Yisong Liu and Heng Wang},
    title =     {{Multicast VPN Upstream Designated Forwarder Selection}},
    pagetotal = 18,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {This document defines Multicast Virtual Private Network (VPN) extensions and procedures of designated forwarder election performed between ingress PEs, which is different from the one described in {[}RFC9026{]} in which the upstream designated forwarder determined by using the "Standby PE Community" carried in the C-Multicast routes. Based on the DF election, the failure detection point discovery mechanism between DF and standby DF is extended in MVPN procedures to achieve fast failover by using BFD session to track the status of detection point. To realize a stable "warm root standby", this document obsolete the P-Tunnel status determining procedure for downstream PEs in regular MVPN by introducing a RPF Set Checking mechanism as an instead.},
}