EVPN VPWS Flexible Cross-Connect Service
draft-ietf-bess-evpn-vpws-fxc-02
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ali Sajassi , Patrice Brissette , Jim Uttaro , John Drake , Sami Boutros , Jorge Rabadan | ||
| Last updated | 2021-03-12 (Latest revision 2020-09-08) | ||
| Replaces | draft-sajassi-bess-evpn-vpws-fxc | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
This document describes a new EVPN VPWS service type specifically for multiplexing multiple attachment circuits across different Ethernet Segments and physical interfaces into a single EVPN VPWS service tunnel and still providing Single-Active and All-Active multi-homing. This new service is referred to as flexible cross-connect service. After a description of the rationale for this new service type, the solution to deliver such service is detailed.
Authors
Ali Sajassi
Patrice Brissette
Jim Uttaro
John Drake
Sami Boutros
Jorge Rabadan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)