I agree with you with that it is literally clear in RFC7432.
So the DF timer in RFC7432 and draft-ietf-bess-evpn-df-election-framework is
the same timer,
And it's only used to collect the remote routes for the same ES (but delay the
usage of them) ,
So the timer is not used in the
The DF Election framework draft does not change that aspect of RFC7432. The ES
route is advertised when the ES goes up, and the timer allows some time to
collect the other routes for the same ES. IMHO RFC7432 is pretty clear about
that...
Thx
Jorge
From: "wang.yub...@zte.com.cn"
Date:
Hi Jorge,
I read the draft-ietf-bess-evpn-df-election-framework-08 and find it seemed not
clear in the DF election FSM .
I didn't find clear explanation about when to advertise the ES route(RT-4)
according to the FSM.
I think it is the DF_TIMER (not ES_UP) event that triggers the
