%% You should probably cite rfc8365 instead of this I-D.
@techreport{ietf-bess-evpn-overlay-12,
    number =    {draft-ietf-bess-evpn-overlay-12},
    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-overlay/12/},
    author =    {Ali Sajassi and John Drake and Nabil Bitar and Ravi Shekhar and Jim Uttaro and Wim Henderickx},
    title =     {{A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)}},
    pagetotal = 33,
    year =      2018,
    month =     feb,
    day =       9,
    abstract =  {This document specifies how Ethernet VPN (EVPN) can be used as a Network Virtualization Overlay (NVO) solution and explores the various tunnel encapsulation options over IP and their impact on the EVPN control plane and procedures. In particular, the following encapsulation options are analyzed: Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), and MPLS over GRE. This specification is also applicable to Generic Network Virtualization Encapsulation (GENEVE); however, some incremental work is required, which will be covered in a separate document. This document also specifies new multihoming procedures for split-horizon filtering and mass withdrawal. It also specifies EVPN route constructions for VXLAN/NVGRE encapsulations and Autonomous System Border Router (ASBR) procedures for multihoming of Network Virtualization Edge (NVE) devices.},
}