Re: [magma] Querier transition based on Group Specific Query?
"V, Magesh (Magesh)" <magesh.v@alcatel-lucent.com> Wed, 01 February 2012 13:05 UTC
Return-Path: <magesh.v@alcatel-lucent.com>
X-Original-To: magma@ietfa.amsl.com
Delivered-To: magma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C64721F8786 for <magma@ietfa.amsl.com>; Wed, 1 Feb 2012 05:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.999
X-Spam-Level:
X-Spam-Status: No, score=-9.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqEg-Nt8Lbmt for <magma@ietfa.amsl.com>; Wed, 1 Feb 2012 05:05:11 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id C8E0721F877B for <magma@ietf.org>; Wed, 1 Feb 2012 05:05:10 -0800 (PST)
Received: from inbansmailrelay2.in.alcatel-lucent.com (h135-250-11-33.lucent.com [135.250.11.33]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q11D56Z7007564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 1 Feb 2012 07:05:08 -0600 (CST)
Received: from INBANSXCHHUB01.in.alcatel-lucent.com (inbansxchhub01.in.alcatel-lucent.com [135.250.12.32]) by inbansmailrelay2.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q11D55ic024197 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 1 Feb 2012 18:35:05 +0530
Received: from INBANSXCHMBSA2.in.alcatel-lucent.com ([135.250.12.50]) by INBANSXCHHUB01.in.alcatel-lucent.com ([135.250.12.32]) with mapi; Wed, 1 Feb 2012 18:35:05 +0530
From: "V, Magesh (Magesh)" <magesh.v@alcatel-lucent.com>
To: Bharat Joshi <bharat_joshi@infosys.com>, Indranil Bhattacharya <myselfindranil@gmail.com>
Date: Wed, 01 Feb 2012 18:35:04 +0530
Thread-Topic: [magma] Querier transition based on Group Specific Query?
Thread-Index: AczgH9SzQT/0xofvQD6DX88M608awgAAhKMFAC8q/WA=
Message-ID: <05D3B4AA7527D74EBF492123846357532165A394EA@INBANSXCHMBSA2.in.alcatel-lucent.com>
References: <CAAaur95C6wF7FmQhyPhd-bZKU7VGK5oozbLwkZxC8Mx89Qq9-A@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A118C41DA1D@BLRKECMBX02.ad.infosys.com> <CAAaur96LJCdBtd8POr4ZRPg84O=XUf1n22XRMcHC1RgWj4C4DA@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A118C41DA1E@BLRKECMBX02.ad.infosys.com>, <CAAaur94PU-fSwQ3QeMe+k9NieQu=iMonL8gxnVE02iwgkQO38A@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A118C41DA1F@BLRKECMBX02.ad.infosys.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A118C41DA1F@BLRKECMBX02.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Mailman-Approved-At: Wed, 01 Feb 2012 05:44:56 -0800
Cc: "magma@ietf.org" <magma@ietf.org>
Subject: Re: [magma] Querier transition based on Group Specific Query?
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/magma>, <mailto:magma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/magma>
List-Post: <mailto:magma@ietf.org>
List-Help: <mailto:magma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/magma>, <mailto:magma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2012 13:05:14 -0000
Hi, I believe querier election is driven by only Gen.Quer msgs. An igmp router can be in either 'Querier' or 'Non-Querier' state. Since GSQs will be sent only by 'Querier' then we have to see what a 'Non-Querier' is recommended to do upon reception of GSQ. The 'Non-Querier' should ONLY update its grp membership timer. The below snippet from last paragraph of section-3 explains this. <<<<<<<<<<<<<<<<<<<< When a non-Querier receives a Group-Specific Query message, if its existing group membership timer is greater than [Last Member Query Count] times the Max Response Time specified in the message, it sets its group membership timer to that value. >>>>>>>>>>>>>>>>>>> Also, the 'Non-Querier' state diagram reiterates the above interpretation. Thanks, Magesh. -----Original Message----- From: magma-bounces@ietf.org [mailto:magma-bounces@ietf.org] On Behalf Of Bharat Joshi Sent: Tuesday, January 31, 2012 7:39 PM To: Indranil Bhattacharya Cc: magma@ietf.org Subject: Re: [magma] Querier transition based on Group Specific Query? Indranil. Looks like what you are saying is correct. So it seems querier election logic should run when either group-specific queries or general queries are received. Regards, Bharat ________________________________________ From: Indranil Bhattacharya [myselfindranil@gmail.com] Sent: Tuesday, January 31, 2012 7:24 PM To: Bharat Joshi Cc: magma@ietf.org Subject: Re: [magma] Querier transition based on Group Specific Query? Hi Bharat, RFC 2236, from Section 2.1 0x11 = Membership Query There are two sub-types of Membership Query messages: - General Query, used to learn which groups have members on an attached network. - Group-Specific Query, used to learn if a particular group has any members on an attached network. So Membership Query means both. Thanks, Indranil On Tue, Jan 31, 2012 at 7:00 PM, Bharat Joshi <bharat_joshi@infosys.com<mailto:bharat_joshi@infosys.com>> wrote: Hi Indranil, Is this defined in an RFC like that? Can you point me to the reference where it says what you mean below? I just did a google search on this and few top results for this seems to refer to general query only. Regards, Bharat ________________________________________ From: Indranil Bhattacharya [myselfindranil@gmail.com<mailto:myselfindranil@gmail.com>] Sent: Tuesday, January 31, 2012 6:58 PM To: Bharat Joshi Cc: magma@ietf.org<mailto:magma@ietf.org> Subject: Re: [magma] Querier transition based on Group Specific Query? Hi Bharat, "IGMP Membership Query"query does not mean only General Query. It means both GQ and GSQ. Anything on this? Thanks, Indranil On Tue, Jan 31, 2012 at 4:33 PM, Bharat Joshi <bharat_joshi@infosys.com<mailto:bharat_joshi@infosys.com><mailto:bharat_joshi@infosys.com<mailto:bharat_joshi@infosys.com>>> wrote: Hi Indranil, I think a router should always be looking at general queries. This is what is available in RFC 2236: >>> The following three events can cause the router to change states: - "query timer expired" occurs when the timer set for query transmission expires. - "query received from a router with a lower IP address" occurs when an IGMP Membership Query is received from a router on the same network with a lower IP address. - "other querier present timer expired" occurs when the timer set to note the presence of another querier with a lower IP address on the network expires. <<< The second point clearly says that it should be an "IGMP Membership Query" which can trigger a change in querier state. Regards, Bharat ________________________________________ From: magma-bounces@ietf.org<mailto:magma-bounces@ietf.org><mailto:magma-bounces@ietf.org<mailto:magma-bounces@ietf.org>> [magma-bounces@ietf.org<mailto:magma-bounces@ietf.org><mailto:magma-bounces@ietf.org<mailto:magma-bounces@ietf.org>>] On Behalf Of Indranil Bhattacharya [myselfindranil@gmail.com<mailto:myselfindranil@gmail.com><mailto:myselfindranil@gmail.com<mailto:myselfindranil@gmail.com>>] Sent: Tuesday, January 31, 2012 8:56 AM To: magma@ietf.org<mailto:magma@ietf.org><mailto:magma@ietf.org<mailto:magma@ietf.org>> Subject: [magma] Querier transition based on Group Specific Query? Hi, In the querier transition state machine, RFC 2236 only mentions 'Query' and does not specify GQ or GSQ. Can a querier transition take place based on GSQ? Or is it okay to for a querier to ignore GSQ? Can anyone please help me with this? Thanks, Indranil **************** 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@ietf.org https://www.ietf.org/mailman/listinfo/magma
- [magma] Querier transition based on Group Specifi… Indranil Bhattacharya
- Re: [magma] Querier transition based on Group Spe… Kudachi, Deepak S
- Re: [magma] Querier transition based on Group Spe… Bharat Joshi
- Re: [magma] Querier transition based on Group Spe… Indranil Bhattacharya
- Re: [magma] Querier transition based on Group Spe… Indranil Bhattacharya
- Re: [magma] Querier transition based on Group Spe… Bharat Joshi
- Re: [magma] Querier transition based on Group Spe… Indranil Bhattacharya
- Re: [magma] Querier transition based on Group Spe… Bharat Joshi
- Re: [magma] Querier transition based on Group Spe… Bharat Joshi
- Re: [magma] Querier transition based on Group Spe… V, Magesh (Magesh)
- Re: [magma] Querier transition based on Group Spe… V, Magesh (Magesh)
- Re: [magma] Querier transition based on Group Spe… Bharat Joshi