@misc{rfc9014,
    series =    {Request for Comments},
    number =    9014,
    howpublished =  {RFC 9014},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC9014},
    url =       {https://www.rfc-editor.org/info/rfc9014},
    author =    {Jorge Rabadan and Senthil Sathappan and Wim Henderickx and Ali Sajassi and John Drake},
    title =     {{Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks}},
    pagetotal = 24,
    year =      2021,
    month =     may,
    abstract =  {This document describes how Network Virtualization Overlays (NVOs) 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 (EVPNs) and other Layer 2 VPN (L2VPN) technologies used in the WAN, such as Virtual Private LAN Services (VPLSs), 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 multihoming. This document also describes the use of the Unknown MAC Route (UMR) to avoid issues of a Media Access Control (MAC) scale on Data Center Network Virtualization Edge (NVE) devices.},
}