%% You should probably cite rfc9014 instead of this I-D.
@techreport{ietf-bess-dci-evpn-overlay-08,
    number =    {draft-ietf-bess-dci-evpn-overlay-08},
    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-dci-evpn-overlay/08/},
    author =    {Jorge Rabadan and Senthil Sathappan and Wim Henderickx and Ali Sajassi and John Drake},
    title =     {{Interconnect Solution for EVPN Overlay networks}},
    pagetotal = 28,
    year =      2018,
    month =     feb,
    day =       8,
    abstract =  {This document describes how Network Virtualization Overlays (NVO) can be connected to a Wide Area Network (WAN) in order to extend the layer-2 connectivity required for some tenants. The solution analyzes the interaction between NVO networks running Ethernet Virtual Private Networks (EVPN) and other L2VPN technologies used in the WAN, such as Virtual Private LAN Services (VPLS), VPLS extensions for Provider Backbone Bridging (PBB-VPLS), EVPN or PBB-EVPN. It also describes how the existing Technical Specifications apply to the Interconnection and extends the EVPN procedures needed in some cases. In particular, this document describes how EVPN routes are processed on Gateways (GWs) that interconnect EVPN-Overlay and EVPN-MPLS networks, as well as the Interconnect Ethernet Segment (I-ES) to provide multi-homing, and the use of the Unknown MAC route to avoid MAC scale issues on Data Center Network Virtualization Edge (NVE) devices.},
}