IGMP routes are originated by IGMP module and are sent to L2RIB (MCT module) through RIB-LIB and transported to MCT Peers. IGMP Routes received from the remote peers are added to L2 RIB table in MCT and forwarded to IGMP through RIB-LIB.
Currently IGMP EVPN routes sent to MCT L2RIB are not exchanged with BGP. In future, this solution will be extended to support Multicast over BGP-EVPN, where MCT will exchange IGMP EVPN Routes with BGP and MCT Peers.
The EVI RT is an EVPN extended community of Type 6 and a subtype yet to be defined by IANA. The EVI RT extended community is NOT supported for IGMP routes.
Instead, the RT extended community with Type 0x00 and Subtype 0x02 is supported. This extended community carries the RT associated with the EVI (VLAN or bridge domain), so that the receiving PE can identify the EVI properly.
ES-Import (ES-I) Route Target (RT) is an EVPN extended community of Type 0x06 and Subtype 0x02. The 6-byte value calculated is based on the ES-Import.
The IGMP Join and Leave Sync routes carry the ES-Import RT for the ES on which the IGMP membership report was received. The report goes only to the PEs attached to that ES.
Only the VXLAN tunnel encapsulation type is supported. MPLS is not supported for ICLs in MCT scenarios.