%% You should probably cite draft-sr-bess-evpn-vpws-gateway-06 instead of this revision.
@techreport{sr-bess-evpn-vpws-gateway-05,
    number =    {draft-sr-bess-evpn-vpws-gateway-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sr-bess-evpn-vpws-gateway/05/},
    author =    {Jorge Rabadan and Senthil Sathappan and Vinod Prabhu and Wen Lin and Patrice Brissette},
    title =     {{Ethernet VPN Virtual Private Wire Services Gateway Solution}},
    pagetotal = 19,
    year =      2024,
    month =     aug,
    day =       14,
    abstract =  {Ethernet Virtual Private Network Virtual Private Wire Services (EVPN VPWS) need to be deployed in high scale multi-domain networks, where each domain can use a different transport technology, such as MPLS, VXLAN or Segment Routing with MPLS or IPv6 Segment Identifiers (SIDs). While transport interworking solutions on border routers spare the border routers from having to process service routes, they do not always meet the multi-homing, redundancy, and operational requirements, or provide the isolation that each domain requires. This document analyzes the scenarios in which an interconnect solution for EVPN VPWS using EVPN Domain Gateways is needed, and adds the required extensions to support it.},
}