We are looking for feedback on a scheme to enable TSs multicast in NVO3
environment without NVE doing extra work for IGMP/MLD messages (to be added to
the Section 3.3: Replication at a Multicast Service Node). This approach will
be very useful for Server based NVEs that don't support IGMP/MLD:
"Multicast Service Node" can send VN scoped broadcast "IGMP query", that
are encapsulated in overlay header. The overlay header has the following
property.
Inner Source = Multicast Service Node
Inner Dest Addr = IGMP multicast address
Outer Source = the NVE module embedded in (or attached to) Multi-Service
Node
Outer Dest Addr = NVEs that participate in the VN.
The NVEs perform the same procedure as other data frames: i.e.
decapsulate and forwarded to the attached TSs.
If the NVEs perform real time learning of inner-outer address mapping,
the NVE should have learned the following mapping:
Inner: the Multicast Service Node Address ==> Outer: Multicast Service
Node NVE address.
NVEs can also get their Multicast Service Node to its NVE address
mapping from NVA.
When the reply (IGMP report) from the targeted TSs arrives at the NVEs,
the normal encapsulation by the NVEs will have the outer DA as the Multicast
Service Node NVE address.
Your comments are appreciated.
Linda
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
