EVPN Virtual Ethernet Segment
draft-sajassi-bess-evpn-virtual-eth-segment-03

Document Type Replaced Internet-Draft (bess WG)
Last updated 2018-12-04 (latest revision 2018-02-25)
Replaced by draft-ietf-bess-evpn-virtual-eth-segment
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-evpn-virtual-eth-segment
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

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-sajassi-bess-evpn-virtual-eth-segment-03.txt

Abstract

EVPN and PBB-EVPN introduce a family of solutions for multipoint Ethernet services over MPLS/IP network with many advanced capabilities 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 the 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.

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@alcatel-lucent.com)

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