Re: [magma] Querier transition based on Group Specific Query?

Indranil Bhattacharya <myselfindranil@gmail.com> Tue, 31 January 2012 13:54 UTC

Return-Path: <myselfindranil@gmail.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 3605821F8601 for <magma@ietfa.amsl.com>; Tue, 31 Jan 2012 05:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.198
X-Spam-Level:
X-Spam-Status: No, score=-3.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1]
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 AGIpTKTMOfbu for <magma@ietfa.amsl.com>; Tue, 31 Jan 2012 05:54:10 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0188B21F85F4 for <magma@ietf.org>; Tue, 31 Jan 2012 05:54:09 -0800 (PST)
Received: by vcbfk14 with SMTP id fk14so11565vcb.31 for <magma@ietf.org>; Tue, 31 Jan 2012 05:54:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7IWW4rv/UeW557+WcJq+w5eXzhZMNn3IQWjq3ZjYgDw=; b=Vl4cGPbBhRr9WjJrt9+5VkugqB7B8SL/pK8XlN12eOQPthQDg7D4UByB9lNLzZGUtt LR20EHrGOx5g/7PequT73HzzpoJsPUnKVGa7f9M2E+dUzMVSUEEe6JXOTwTr5anIUyAw 1b0gYXPUprmjaxMuWyJo4OQY7amVitgpqKWQA=
MIME-Version: 1.0
Received: by 10.220.39.136 with SMTP id g8mr12067809vce.9.1328018049476; Tue, 31 Jan 2012 05:54:09 -0800 (PST)
Received: by 10.220.7.70 with HTTP; Tue, 31 Jan 2012 05:54:09 -0800 (PST)
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A118C41DA1E@BLRKECMBX02.ad.infosys.com>
References: <CAAaur95C6wF7FmQhyPhd-bZKU7VGK5oozbLwkZxC8Mx89Qq9-A@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A118C41DA1D@BLRKECMBX02.ad.infosys.com> <CAAaur96LJCdBtd8POr4ZRPg84O=XUf1n22XRMcHC1RgWj4C4DA@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A118C41DA1E@BLRKECMBX02.ad.infosys.com>
Date: Tue, 31 Jan 2012 19:24:09 +0530
Message-ID: <CAAaur94PU-fSwQ3QeMe+k9NieQu=iMonL8gxnVE02iwgkQO38A@mail.gmail.com>
From: Indranil Bhattacharya <myselfindranil@gmail.com>
To: Bharat Joshi <bharat_joshi@infosys.com>
Content-Type: multipart/alternative; boundary=bcaec54eeb2018273704b7d34c83
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: Tue, 31 Jan 2012 13:54:11 -0000

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>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]
> Sent: Tuesday, January 31, 2012 6:58 PM
> To: Bharat Joshi
> Cc: 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>> 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> [
> magma-bounces@ietf.org<mailto:magma-bounces@ietf.org>] On Behalf Of
> Indranil Bhattacharya [myselfindranil@gmail.com<mailto:
> myselfindranil@gmail.com>]
> Sent: Tuesday, January 31, 2012 8:56 AM
> To: 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***
>
>