EVPN Virtual Ethernet Segment

The information below is for an old version of the document
Document Type Expired Internet-Draft (bess WG)
Authors Ali Sajassi  , Patrice Brissette  , Rick Schell  , John Drake  , Jorge Rabadan 
Last updated 2019-07-22 (latest revision 2019-01-18)
Replaces draft-sajassi-bess-evpn-virtual-eth-segment
Stream IETF
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd LucAndré Burdet
Shepherd write-up Show (last changed 2019-02-20)
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Luc André Burdet <lburdet@cisco.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


EVPN and PBB-EVPN introduce a family of solutions for multipoint Ethernet services over MPLS/IP network with many advanced features among which their multi-homing capabilities. These solutions define two types of multi-homing for an Ethernet Segment (ES): 1) Single- Active and 2) All-Active, where an Ethernet Segment is defined as a set of links between the multi-homed device/network and a set of PE devices that they are connected to. Some Service Providers want to extend the concept of the physical links in an ES to Ethernet Virtual Circuits (EVCs) where many of such EVCs can be aggregated on a single physical External Network-to- Network Interface (ENNI). An ES that consists of a set of EVCs instead of physical links is referred to as a virtual ES (vES). This draft describes the requirements and the extensions needed to support vES in EVPN and PBB-EVPN.


Ali Sajassi (sajassi@cisco.com)
Patrice Brissette (pbrisset@cisco.com)
Rick Schell (richard.schell@verizon.com)
John Drake (jdrake@juniper.net)
Jorge Rabadan (jorge.rabadan@nokia.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)