MVPN/EVPN Composite Tunnel
draft-zzhang-bess-mvpn-evpn-composite-tunnel-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , Jorge Rabadan , Ali Sajassi | ||
| Last updated | 2019-09-12 (Latest revision 2019-03-11) | ||
| 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
EVPN E-Tree defines a composite tunnel to be used for a Root PE to simultaneously indicate a non-Ingress-Replication tunnel (e.g., P2MP tunnel) in the transmit direction and an Ingress Replication tunnel in the receive direction for BUM traffic. This document extends it to more generic use in both MVPN and general EVPN.
Authors
Zhaohui (Jeffrey) Zhang
Jorge Rabadan
Ali Sajassi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)