Re: IGMP NonQuerier Adopted Robustness value

Bharat Joshi <[email protected]> Mon, 30 Nov 2009 12:16:48 +0530
Newsgroups gmane.ietf.magma
Message-ID <31D55C4D55BEED48A4459EB64567589A100C680823@BLRKECMBX02.ad.infosys.com>
Rajsekhar,

    Yes. You are right. Adoption of the robustness value is done for such usage.

    Startup-query count need not be based on the learnt value. When IGMP is started on an interface, it does not know who is the present querier and what is the robustness value. It assumes itself to be the querier and start sending query with whatever it is configured with.

Thanks,
Bharat
________________________________________
From: [email protected] [[email protected]] On Behalf Of rajasekar bonthala [[email protected]]
Sent: Monday, November 30, 2009 11:58 AM
To: [email protected]; [email protected]
Subject: [magma] IGMP NonQuerier Adopted Robustness value

Hi,

In the IGMP RFC it is mentioned that Non-Querier adopts the Robustness value of the querier.
There are some IGMP Protocol parameters, where they depend on Robustness to derive their value, for example non-querier timeout, start-up query count etc... I think these should also change accordingly, after adopting robustness.

In the case of start-up query count,  is it required that start-up query count should also change ?

Thanks,
RajaSekhar