AC-influenced Designated Forwarder Election for (PBB-)EVPN
draft-rabadan-bess-evpn-ac-df-01
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Authors | Jorge Rabadan , Kiran Nagaraj , Senthil Sathappan , Vinod Prabhu , Wim Henderickx | ||
| Last updated | 2015-04-30 (latest revision 2014-10-27) | ||
| Replaced by | draft-ietf-bess-evpn-ac-df | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-rabadan-bess-evpn-ac-df-01.txt
Abstract
The Designated Forwarder (DF) in (PBB-)EVPN networks is the PE responsible for sending multicast, broadcast and unknown unicast traffic to a multi-homed CE, on a given Ethernet Tag on a particular Ethernet Segment (ES). The DF is selected based on the list of PEs that advertise the Ethernet Segment Identifier (ESI) to the EVPN network. While PE node or link failures trigger the DF re-election for a given <ESI, EVI>, individual Attachment Circuit (AC) or MAC-VRF failures do not trigger such DF re-election and the traffic may therefore be permanently impacted, even though there is an alternative path. This document improves the DF election algorithm so that the AC status can influence the result of the election and this type of "logical" failures can be protected too.
Authors
Jorge Rabadan
(jorge.rabadan@alcatel-lucent.com)
Kiran Nagaraj
(kiran.nagaraj@alcatel-lucent.com)
Senthil Sathappan
(senthil.sathappan@alcatel-lucent.com)
Vinod Prabhu
(vinod.prabhu@alcatel-lucent.com)
Wim Henderickx
(wim.henderickx@alcatel-lucent.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)