Re: [magma] igmp snooping querier recommendations

[Prashanth Badabagni <pbadabag at brocade.com>]

Are there any ways to avoid the problem mentioned in point 2 in the 
original post? The only way I see is using a source ip address 0.0.0.0;
But vendors like cisco generate the queries with a valid ip address
configured on the vlan on which snooping querier is enabled.

thanks

-----Original Message-----
From: Prashant Jhingran (pjhingra) [mailto:pjhingra at cisco.com] 
Sent: Tuesday, August 18, 2009 7:04 PM
To: Prashanth Badabagni
Cc: magma at ietf.org
Subject: RE: [magma] igmp snooping querier recommendations

Hi Prashanth,

Refer rfc 4541 & 4605, these would clarify your doubts.
 
Regards,
Prashant Jhingran
 
Phone:   +91-80-442 61800
 
-----Original Message-----
From: magma-bounces at ietf.org [mailto:magma-bounces at ietf.org] On Behalf
Of Prashanth Badabagni
Sent: Tuesday, August 18, 2009 4:49 PM
To: magma at ietf.org
Subject: [magma] igmp snooping querier recommendations


Hi,

I've the following questions regarding igmp snooping querier
implementation.
Please provide your thoughts on this.

1. Are there any recommendations for implementation igmp snooping
querier.

2. what should be the ip address of the queries sent. Should it always
be 0.0.0.0 or valid ip address should be allowed. There can be a problem
if the general queries are sent with valid ip address, if an l3 router
comes up in the vlan, by listening to the query message, it might assume
that there is another querier present, which can potentially make the l3
querier a non-querier on that interface.

3. what kinds of queries should be sent, only general queries, or group
specific queries should also be allowed.

4. what should be the behavior, if the switch listens to igmp activity
in the vlan on which snooping querier is enabled.

Thanks

_______________________________________________
magma mailing list
magma at ietf.org
https://www.ietf.org/mailman/listinfo/magma