%% You should probably cite rfc9136 instead of this I-D.
@techreport{ietf-bess-evpn-prefix-advertisement-11,
    number =    {draft-ietf-bess-evpn-prefix-advertisement-11},
    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/11/},
    author =    {Jorge Rabadan and Wim Henderickx and John Drake and Wen Lin and Ali Sajassi},
    title =     {{IP Prefix Advertisement in Ethernet VPN (EVPN)}},
    pagetotal = 31,
    year =      2018,
    month =     may,
    day =       18,
    abstract =  {The BGP MPLS-based Ethernet VPN (EVPN) (RFC 7432) mechanism provides a flexible control plane that allows intra-subnet connectivity in an MPLS and/or Network Virtualization Overlay (NVO) (RFC 7365) network. In some networks, there is also a need for dynamic and efficient inter-subnet connectivity across Tenant Systems and end devices that can be physical or virtual and do not necessarily participate in dynamic 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.},
}