<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-bess-evpn-virtual-eth-segment" target="https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-virtual-eth-segment-15">
   <front>
      <title>EVPN Virtual Ethernet Segment</title>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="P." surname="Brissette" fullname="Patrice Brissette">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="R." surname="Schell" fullname="Rick Schell">
         <organization>Verizon</organization>
      </author>
      <author initials="J." surname="Drake" fullname="John Drake">
         <organization>Juniper</organization>
      </author>
      <author initials="J." surname="Rabadan" fullname="Jorge Rabadan">
         <organization>Nokia</organization>
      </author>
      <date month="February" day="28" year="2024" />
      <abstract>
	 <t>   Etheret VPN (EVPN) and Provider Backbone EVPN (PBB-EVPN) introduce a
   family of solutions for Ethernet services over MPLS/IP network with
   many advanced features including multi-homing capabilities.  These
   solutions introduce Single-Active and All-Active redundancy modes for
   an Ethernet Segment (ES), itself defined as a set of physical links
   between the multi-homed device/network and a set of PE devices that
   they are connected to.  This document extends the Ethernet Segment
   concept so that an ES can be associated to a set of Ethernet Virtual
   Circuits (EVCs e.g., VLANs) or other objects such as MPLS Label
   Switch Paths (LSPs) or Pseudowires (PWs).  Such an ES is referred to
   as Virtual Ethernet Segments (vES).  This draft describes the
   requirements and the extensions needed to support vES in EVPN and
   PBB-EVPN.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-bess-evpn-virtual-eth-segment-15" />
   
</reference>
