Hi,
The forwarding rule for {S,G} or {*,G} remains the same as IGMP V3 spec. Only
difference is about setting up tunnels between EVPN PE.
Source IP address for Querier will be picked from local config or IRB. But this
spec utilizes existing Querier config and procedures from IGMP implementation.
Mankamana
From: BESS <bess-boun...@ietf.org> on behalf of Nitsan Dolev
<nitsan.do...@rbbn.com>
Date: Sunday, March 17, 2024 at 8:19 AM
To: rfc9...@ietf.org <rfc9...@ietf.org>, bess@ietf.org <bess@ietf.org>
Subject: [bess] RFC9251
Dear RFC9251 Co-authors,
Your help with the following questions will be most appreciated,
RFC 9251 seems to assume that the receiving PE will forward:
1. (S,G1) traffic only to those host who explicitly sent IGMPv3 report
(S,G1) and those who sent IGMPv3 Report (*,G1)
2. (*,G1) traffic only to those host who explicitly sent IGMPv3 report
(*,G1) IGMPv2(G1)
Is this indeed the assumption?
Does it mean that the receiving PE shall do an IP Multicast lookup ? i.e. Has
MFIB entry with
(S,G1)==> OIF( a, b, c ..) for all local AC ports from which IGMPv3 Report
(S,G1) OR
(*,G1)==> OIF( a, b, c ..) for all local AC ports from which IGMPv3 Report
(*,G1) or IGMPv2 report (G1)
Another issue:
Referring to https://www.rfc-editor.org/rfc/rfc9251.html#name-proxy-querier
It says that “As mentioned in the previous sections, each PE MUST have proxy
querier functionality for the following reasons:
to enable the collection of EVPN PEs providing Layer 2 Virtual Private Network
(L2VPN) service to act as a distributed multicast router with an anycast IP
address for all attached hosts in that subnet
to enable suppression of IGMP Membership Reports and Membership Queries over
MPLS/IP core”
What shall be the source IP address of the IGMP queries?
Possible Alternatives: 1. The source IP of one of the Routers on the related PE
BD (if exists). 2. Some preconfigured dummy IRB Router Anycast IP address ?
Looking forward to getting your response,
Nitsan Dolev Elfassy
Ribbon Communications
Disclaimer
This e-mail together with any attachments may contain information of Ribbon
Communications Inc. and its Affiliates that is confidential and/or proprietary
for the sole use of the intended recipient. Any review, disclosure, reliance or
distribution by others or forwarding without express permission is strictly
prohibited. If you are not the intended recipient, please notify the sender
immediately and then delete all copies, including any attachments.
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
