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

From: ravikumar vj <[email-masked]>
Date: Sun, 25 May 2008 21:27:46 -0700 (PDT)

Hi Bharat,
            Why the non-querier have to wait till it receives a grp specific or grp-and-src specific query? Why cant the non-querier update the timers on receiving the reports it-self.
            As per given in the example when the Querier receives the BLOCK (S1), he updates the timer of S1 to LMQT and sends a Grp-and-src specific query for S1. Why can the non-qurier update the timer of S1 to LMQT as well (and DONT send query), when he receives the report. Why the non-querier have to wait till he receives the Grp-and-src specific query to update his timers?
   
  Thanks and Regards
  Ravikumar V J

Message: 1
Date: Fri, 23 May 2008 01:25:57 -0700
From: "Suvendu Mozumdar" 
Subject: [magma] Non-Querier behaviour on receiving grp specific or
grp-and-src specific queries
To: 
Message-ID:
<[email-masked]>
Content-Type: text/plain; charset="us-ascii"

Hi,

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, 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.

Can anyone throw some light on this?

Thanks

Suvendu.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.ietf.org/mailman/private/magma/attachments/20080523/7da46ef7/attachment-0001.htm 

------------------------------

Message: 2
Date: Fri, 23 May 2008 14:07:00 +0530
From: Bharat Joshi 
Subject: Re: [magma] Non-Querier behaviour on receiving grp specific
or grp-and-src specific queries
To: Suvendu Mozumdar 
Cc: "[email-masked]" 
Message-ID: <1211531820.22712.19.camel@magadha>
Content-Type: text/plain; charset=

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.

> 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.

Also most of the times, it is expected that all routers are configured
with same values but things should still work if they are not.

Hope this helps.

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
[email-masked]
https://www.ietf.org/mailman/listinfo/magma

End of magma Digest, Vol 46, Issue 1
************************************

_______________________________________________
magma mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/magma