%% You should probably cite rfc9541 instead of this I-D.
@techreport{ietf-bess-pbb-evpn-isid-cmacflush-01,
    number =    {draft-ietf-bess-pbb-evpn-isid-cmacflush-01},
    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-pbb-evpn-isid-cmacflush/01/},
    author =    {Jorge Rabadan and Senthil Sathappan and Kiran Nagaraj and Masahiro Miyake and Taku Matsuda},
    title =     {{PBB-EVPN ISID-based CMAC-Flush}},
    pagetotal = 12,
    year =      2020,
    month =     oct,
    day =       30,
    abstract =  {Provider Backbone Bridging (PBB) can be combined with Ethernet VPN (EVPN) to deploy Ethernet Local Area Network (ELAN) services in large Multi-Protocol Label Switching (MPLS) networks (PBB-EVPN). Single- Active Multi-homing and per-ISID Load-Balancing can be provided to access devices and aggregation networks. In order to speed up the network convergence in case of failures on Single-Active Multi-Homed Ethernet Segments, PBB-EVPN defines a flush mechanism for Customer MACs (CMAC-flush) that works for different Ethernet Segment Backbone MAC (BMAC) address allocation models. This document complements those CMAC-flush procedures for cases in which no PBB-EVPN Ethernet Segments are defined (the attachment circuit is associated to a zero Ethernet Segment Identifier) and a Service Instance Identifier based (ISID-based) CMAC-flush granularity is required.},
}