%% You should probably cite rfc9136 instead of this I-D.
@techreport{ietf-bess-evpn-prefix-advertisement-01,
    number =    {draft-ietf-bess-evpn-prefix-advertisement-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-evpn-prefix-advertisement/01/},
    author =    {Jorge Rabadan and Wim Henderickx and Senad Palislamovic and Florin Balus and Aldrin Isaac},
    title =     {{IP Prefix Advertisement in EVPN}},
    pagetotal = 24,
    year =      2015,
    month =     mar,
    day =       9,
    abstract =  {EVPN provides a flexible control plane that allows intra-subnet connectivity in an IP/MPLS and/or an NVO-based network. In NVO networks, there is also a need for a dynamic and efficient inter- subnet connectivity across Tenant Systems and End Devices that can be physical or virtual and may not support their own routing protocols. This document defines a new EVPN route type for the advertisement of IP Prefixes and explains some use-case examples where this new route- type is used.},
}