E-TREE Support in E-VPN
draft-sajassi-l2vpn-evpn-etree-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Ali Sajassi , Samer Salam , Wim Henderickx , Jim Uttaro | ||
| Last updated | 2013-04-25 (Latest revision 2012-10-22) | ||
| Replaced by | draft-sajassi-bess-evpn-etree | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 E-VPN.
Authors
Ali Sajassi
Samer Salam
Wim Henderickx
Jim Uttaro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)