EVPN Virtual Ethernet Segment
draft-ietf-bess-evpn-virtual-eth-segment-06

Document Type Expired Internet-Draft (bess WG)
Last updated 2020-09-10 (latest revision 2020-03-09)
Replaces draft-sajassi-bess-evpn-virtual-eth-segment
Stream IETF
Intended RFC status (None)
Formats
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
https://www.ietf.org/archive/id/draft-ietf-bess-evpn-virtual-eth-segment-06.txt

Abstract

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 introduce Single-Active and All-Active 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 EVCs (e.g., VLANs) or other objects such as MPLS Label Switch Paths (LSPs) or Pseudowires (PWs), referred to as Virtual Ethernet Segments (vES). This draft describes the requirements and the extensions needed to support vES in EVPN and PBB-EVPN.

Authors

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.)