[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [magma] Non-Querier behaviour on receiving grp specific orgrp-and-src specific queries



Hi Suvendu,

> >      I have an issue for which the RFC 3376 does not suggest anything.
> > Lets say in a Lan there are two igmpv3 routers and one igmpv3 host
> > present. Lets say Q1 is querier and Q2 is non-querier. Now Host1 sends
> > include s1 for grp G1. Both Q1 and Q2 will have an entry in their
> > respective database. Now Host1 sends a report block s1 for grp G1. Q1
> > on receipt of this block report will start LMQT timer, set the source
> > timer of s1 to LMQT and start sending group and source specific
> > queries for G1/s1. After LMQT expires Q1 will delete the entry of
> > G1/s1 from its database. Now what will be the non-querier's behaviour.
> > Will it also start LMQT,
>
> Please look at section 6.6.1. When a non-querier receives a query, it
> reduces its corresponding timer to LMQT which can be derived from
> max-response code.
> Suvendu : As per section 8.10, LMQT = LMQC*LMQI, I agree that LMQI is
> the max-response code in the specific query, but LMQC is configurable
> and MAY differ in querier and non-querier. That's where my doubt arises.

Non-querier need not use LMQT in turn LMQC at all. They can simply lower down their group/source timer to LMQI calculated based on Max-Response-Code and they do it for each group/group-source specific query.

> > in that case Querier's LMQT and non-querier's LMQT (which is
> > LMQC*LMQI) may differ based on different LMQC values. Non-querier
> > comes to know about the querier's LMQI from the Max Response Code in
> > the specific query pkt but what about querier's LMQC, non-querier has
> > no way to know about the querier's LMQI.
>
> Non-querier does not need to know LMQC as it is not required. LMQC is
> required for a querier to generate number of queries.
> Suvendu : Not only that, LMQC is used in calculating LMQT, pl refer
> section 8.10.

Please see above.

Thanks,
Bharat

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are not 
to copy, disclose, or distribute this e-mail or its contents to any other person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has taken 
every reasonable precaution to minimize this risk, but is not liable for any damage 
you may sustain as a result of any virus in this e-mail. You should carry out your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
magma mailing list
magma at ietf.org
https://www.ietf.org/mailman/listinfo/magma