[magma] A question on multicast states in non-querier

Bharat Joshi <bharat_joshi@infosys.com> Mon, 14 February 2011 05:01 UTC

Return-Path: <bharat_joshi@infosys.com>
X-Original-To: magma@core3.amsl.com
Delivered-To: magma@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3ACA73A6C50 for <magma@core3.amsl.com>; Sun, 13 Feb 2011 21:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.166
X-Spam-Level:
X-Spam-Status: No, score=-6.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tDgCdBLWaiMi for <magma@core3.amsl.com>; Sun, 13 Feb 2011 21:01:23 -0800 (PST)
Received: from kecgate02.infosys.com (Kecgate02.infosys.com [122.98.14.32]) by core3.amsl.com (Postfix) with ESMTP id 81F663A6C48 for <magma@ietf.org>; Sun, 13 Feb 2011 21:01:22 -0800 (PST)
X-TM-IMSS-Message-ID: <1987ed440001100e@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id 1987ed440001100e ; Mon, 14 Feb 2011 10:27:40 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.25]) by blrkechub01.ad.infosys.com ([10.66.236.41]) with mapi; Mon, 14 Feb 2011 10:31:41 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "magma@ietf.org" <magma@ietf.org>
Date: Mon, 14 Feb 2011 10:31:40 +0530
Thread-Topic: A question on multicast states in non-querier
Thread-Index: AQHLzARDWv8XAToT7EGln7Yd2kdQOA==
Message-ID: <31D55C4D55BEED48A4459EB64567589A10908D6CCC@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
Subject: [magma] A question on multicast states in non-querier
X-BeenThere: magma@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast and Anycast Group Membership <magma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 14 Feb 2011 05:01:24 -0000

Hi All,

      If there are two IGMP routers on a LAN, one of them gets elected as querier and another as non-querier.

      The querier sends query and hosts on that LAN reply with the reports. Querier sees those report and create a database. Non-querier also sees those report and would create the same database.

      Question is whether Multicast routing protocol running on non-querier's upstream interface should use this database to join/leave the multicast group or not?

      IIRC, it is required because the DR for that LAN could be the non-querier router and if we do not join upstream, multicast data won't flow to this router. Is this a correct thinking?

Regards,
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***