Enhancements to Multicast Source Redundancy in EVPN Networks
draft-nagaraj-bess-evpn-redundant-mcast-src-update-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vinod Kumar Nagaraj , Vikram Nagarajan , Zhaohui (Jeffrey) Zhang , Jorge Rabadan | ||
| Last updated | 2023-04-27 (Latest revision 2022-10-24) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
draft-ietf-bess-evpn-redundant-mcast-source specifies Warm Standby (WS) and Hot Standby (HS) procedures for handling redundant multicast traffic into an EVPN tenant domain. With the Hot Standby procedure, multiple ingress PEs may inject traffic and an egress PE will decide from which ingress PE traffic will be accepted and forwarded. The decision is based on certain signaling messages and/or BFD status of provider tunnels from the ingress PEs, and the traffic is associated with ingress PEs based on Ethernet Segment Identifier (ESI) labels. As a result, the procedures in that document only apply to MPLS data plane. This document extends the Hot Standby procedures to non-MPLS data planes and EVPN Data Center Interconnect scenarios.
Authors
Vinod Kumar Nagaraj
Vikram Nagarajan
Zhaohui (Jeffrey) Zhang
Jorge Rabadan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)