%% You should probably cite draft-ietf-bess-evpn-virtual-eth-segment-19 instead of this revision. @techreport{ietf-bess-evpn-virtual-eth-segment-16, number = {draft-ietf-bess-evpn-virtual-eth-segment-16}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-virtual-eth-segment/16/}, author = {Ali Sajassi and Patrice Brissette and Rick Schell and John Drake and Jorge Rabadan}, title = {{EVPN Virtual Ethernet Segment}}, pagetotal = 25, year = 2024, month = nov, day = 3, abstract = {Ethernet VPN (EVPN) and Provider Backbone EVPN (PBB-EVPN) introduce a comprehensive suite of solutions for delivering Ethernet services over MPLS/IP networks. These solutions offer advanced features, including multi-homing capabilities. Specifically, they support Single-Active and All-Active redundancy modes for an Ethernet Segment (ES), which is defined as a collection of physical links connecting a multi-homed device or network to a set of Provider Edge (PE) devices. This document extends the concept of an Ethernet Segment by allowing an ES to be associated with a set of Ethernet Virtual Circuits (EVCs, such as VLANs) or other entities, including MPLS Label Switched Paths (LSPs) or Pseudowires (PWs). This extended concept is referred to as Virtual Ethernet Segments (vES). This draft outlines the requirements and necessary extensions to support vES in both EVPN and PBB-EVPN.}, }