E-TREE Support in EVPN & PBB-EVPN
draft-sajassi-l2vpn-evpn-etree-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ali Sajassi , Samer Salam , Sami Boutros , Wim Henderickx , Jim Uttaro , Aldrin Isaac | ||
Last updated | 2014-10-28 (Latest revision 2013-10-21) | ||
Replaced by | draft-sajassi-bess-evpn-etree | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-sajassi-bess-evpn-etree | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Metro Ethernet Forum (MEF) has defined a rooted-multipoint Ethernet service known as Ethernet Tree (E-Tree). [ETREE-FMWK] proposes a solution framework for supporting this service in MPLS networks. This document discusses how those functional requirements can be easily met with EVPN.
Authors
Ali Sajassi
Samer Salam
Sami Boutros
Wim Henderickx
Jim Uttaro
Aldrin Isaac
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)