EVPN-VPWS Seamless Integration with L2VPN VPWS
draft-ietf-bess-evpn-vpws-seamless-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Authors | Patrice Brissette , Wen Lin , Jorge Rabadan , Jim Uttaro , Bin Wen | ||
Last updated | 2023-12-29 (Latest revision 2023-06-20) | ||
Replaces | draft-brissette-bess-evpn-vpws-seamless | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
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 presents a solution for migrating L2VPN Virtual Private Wire Service (VPWS) to Ethernet VPN Virtual Private Wire Service (EVPN-VPWS) services. The solution allows the coexistence of EVPN and L2VPN services under the same point-to-point VPN instance. By using this seamless integration solution, a service provider can introduce EVPN into their existing L2VPN network or migrate from an existing L2VPN based network to EVPN. The migration may be done per pseudowire or per flexible-crossconnect (FXC) service basis. This document specifies control-plane and forwarding behaviors.
Authors
Patrice Brissette
Wen Lin
Jorge Rabadan
Jim Uttaro
Bin Wen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)