Hi Jorge,
Thanks for your explanation.
I doubt that the meaning of Ethernet Tag is not consistent in rfc7432bis. There
are some examples.
1) section 13.1 "If P2MP LSPs are being used, the packet MUST be sent on the
P2MP LSP of which the PE is the root, for the associated with the
Hi Yubao,
I would recommend reading RFC8584 section 4.1 for VLAN-aware bundle and AC-DF.
Also it is important to understand the difference between ethernet tag id and
ethernet tag. The latter is used for DF election, and not the former.
“Ethernet Tag:
Used to represent a BD that is configured
Hi Sasha,
However, neither 7432bis nor any other RFC or standard I am aware of says that
the same IP address PE address of the PE MUST (or, at least, SHOULD) be used as
the Administrator field of Type 1 RDs in per-ES A-D routes and Type 1 RDs
assigned to MAC-VRFs. And this is obviously a
Yubao hi!
Let us to differentiate between RDs that are used in per ES Ethernet A-D routes
and RDs that are assigned to MAC-VRFs.
* The latter may be auto-derived or manually configured – this is the
operator’s choice in most cases
* The former cannot be manually assigned because, as
Hi Sasha,
I agree with you on the following:
1) in the case of EVPN, it is really important to guarantee that MAC-VRFs that
locally represent the same EVI in different PEs are assigned with different RDs.
2) Type 1 RD is easier to achieve above goal, especially when the RD is
Hi all,
I noticed that the DF-election for VLAN-based/VLAN-bundle service interface has
been modified in section 8.5 of rfc7432bis.
"3. When the timer expires, each PE ... ... The ordinals are used to determine
which PE node will be the DF for a given EVPN instance on the Ethernet
Hi Yubao,
The scenario in which MAC-VRFs that locally represent the same EVI in
different nodes may have severe implications on the EVPN operation.
E.g., consider the scenario in which:
1. An EVI that implements LAN-based service interface:
* Is instantiated in 3 nodes – PE-1, PE-2
