Ethernet VPN Virtual Private Wire Services Gateway Solution
draft-sr-bess-evpn-vpws-gateway-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Jorge Rabadan , Senthil Sathappan , Vinod Prabhu , Wen Lin , Patrice Brissette | ||
| Last updated | 2023-04-13 (Latest revision 2022-10-10) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Ethernet VPN 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.
Authors
Jorge Rabadan
Senthil Sathappan
Vinod Prabhu
Wen Lin
Patrice Brissette
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)