Skip to main content

Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents
RFC 8560

Revision differences

Document history

Date By Action
2019-05-09
(System)
Received changes through RFC Editor sync (created alias RFC 8560, changed title to 'Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service …
Received changes through RFC Editor sync (created alias RFC 8560, changed title to 'Seamless Integration of Ethernet VPN (EVPN) with Virtual Private LAN Service (VPLS) and Their Provider Backbone Bridge (PBB) Equivalents', changed abstract to 'This document specifies mechanisms for backward compatibility of Ethernet VPN (EVPN) and Provider Backbone Bridge Ethernet VPN (PBB-EVPN) solutions with Virtual Private LAN Service (VPLS) and Provider Backbone Bridge VPLS (PBB-VPLS) solutions.  It also provides mechanisms for the seamless integration of these two technologies in the same MPLS/IP network on a per-VPN-instance basis.  Implementation of this document enables service providers to introduce EVPN/PBB-EVPN Provider Edges (PEs) in their brownfield deployments of VPLS/PBB-VPLS networks.  This document specifies the control-plane and forwarding behavior needed for the auto-discovery of the following: 1) a VPN instance, 2) multicast and unicast operation, and 3) a Media Access Control (MAC) mobility operation.  This enables seamless integration between EVPN and VPLS PEs as well as between PBB-VPLS and PBB-EVPN PEs.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2019-05-09, changed IESG state to RFC Published)
2019-05-09
(System) RFC published