@techreport{ietf-bess-evpn-ipvpn-interworking-10,
    number =    {draft-ietf-bess-evpn-ipvpn-interworking-10},
    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-ipvpn-interworking/10/},
    author =    {Jorge Rabadan and Ali Sajassi and Eric C. Rosen and John Drake and Wen Lin and Jim Uttaro and Adam Simpson},
    title =     {{EVPN Interworking with IPVPN}},
    pagetotal = 33,
    year =      2024,
    month =     apr,
    day =       11,
    abstract =  {Ethernet Virtual Private Network (EVPN) is used as a unified control plane for tenant network intra and inter-subnet forwarding. When a tenant network spans not only EVPN domains but also domains where BGP VPN-IP or IP families provide inter-subnet forwarding, there is a need to specify the interworking aspects between BGP domains of type EVPN, VPN-IP and IP, so that the end to end tenant connectivity can be accomplished. This document specifies how EVPN interworks with VPN-IPv4/VPN-IPv6 and IPv4/IPv6 BGP families for inter-subnet forwarding. The document also addresses the interconnect of EVPN domains for Inter-Subnet Forwarding routes. In addition, this specification defines a new BGP Path Attribute called D-PATH (Domain PATH) that protects gateways against control plane loops. D-PATH modifies the BGP best path selection for multiprotocol BGP routes of SAFI 128 and EVPN IP Prefix routes, and therefore this document updates the BGP best path selection in {[}RFC4271{]}, but only for IPVPN and EVPN families.},
}