%% You should probably cite draft-ietf-bess-evpn-ipvpn-interworking-18 instead of this revision.
@techreport{ietf-bess-evpn-ipvpn-interworking-16,
    number =    {draft-ietf-bess-evpn-ipvpn-interworking-16},
    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/16/},
    author =    {Jorge Rabadan and Ali Sajassi and Eric C. Rosen and John Drake and W. Lin and Jim Uttaro and Adam Simpson},
    title =     {{Interconnecting EVPN and IPVPN Domains}},
    pagetotal = 38,
    year =      2026,
    month =     feb,
    day =       28,
    abstract =  {Ethernet Virtual Private Network (EVPN) provides a unified BGP control plane for both intra- and inter-subnet forwarding within tenant networks. When a tenant network spans multiple domains, including any combination of EVPN and IPVPN domains, it becomes necessary to define the interworking mechanisms among these BGP domains (EVPN and VPN-IP) to ensure seamless end-to-end tenant connectivity. This document defines these interworking procedures. In addition, this document defines a new BGP Path Attribute, referred to as D-PATH (Domain PATH), which provides loop prevention for gateway nodes by protecting against control plane loops. The introduction of D-PATH modifies the BGP best path selection process for Multiprotocol BGP inter-subnet forwarding routes of SAFI 128 (IPVPN) and SAFI 70 (EVPN). As a result, this specification updates the BGP best path selection procedure, but only in the context of IPVPN and EVPN route families.},
}