Re: [magma] Query on querier version in IGMPv3
Bharat Joshi <bharat_joshi@infosys.com> Mon, 19 July 2010 08:20 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 0D4993A6846 for <magma@core3.amsl.com>;
Mon, 19 Jul 2010 01:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,
BAYES_00=-2.599]
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 tbmxINybmui2 for
<magma@core3.amsl.com>; Mon, 19 Jul 2010 01:20:11 -0700 (PDT)
Received: from KECGATE03.infosys.com (Kecgate03.infosysconsulting.com
[122.98.10.31]) by core3.amsl.com (Postfix) with ESMTP id 8FB003A6452 for
<magma@ietf.org>; Mon, 19 Jul 2010 01:20:10 -0700 (PDT)
X-TM-IMSS-Message-ID: <6248e97b00013067@KECGATE03.infosys.com>
Received: from blrkechub02.ad.infosys.com ([10.66.236.42]) by
KECGATE03.infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service
7.0) id 6248e97b00013067 ; Mon, 19 Jul 2010 13:43:02 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.26]) by
blrkechub02.ad.infosys.com ([10.66.236.42]) with mapi;
Mon, 19 Jul 2010 13:50:23 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Indranil Bhattacharya <myselfindranil@gmail.com>
Date: Mon, 19 Jul 2010 13:45:23 +0530
Thread-Topic: [magma] Query on querier version in IGMPv3
Thread-Index: AcsnGlj3o4nOltyiTsCxJIt5FmvOwwAADCQf
Message-ID: <31D55C4D55BEED48A4459EB64567589A1070FA839A@BLRKECMBX02.ad.infosys.com>
References: <31D55C4D55BEED48A4459EB64567589A1070FA8397@BLRKECMBX02.ad.infosys.com>,
<AANLkTikgmJyRSZqcR-KWhkpxcKG1NuTgJzKmUsZOp86h@mail.gmail.com>
In-Reply-To: <AANLkTikgmJyRSZqcR-KWhkpxcKG1NuTgJzKmUsZOp86h@mail.gmail.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
Cc: "magma@ietf.org" <magma@ietf.org>
Subject: Re: [magma] Query on querier version in IGMPv3
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, 19 Jul 2010 08:20:13 -0000
Indranil,
Ok. But RFC 3376 clearly says that a router should lower its version to the lowest version of query heard on a network.
One thing I did not get in your reply is 'Let the v2 updates's it querier timer from v3 query...'. While second part of this statement is clear, I am not sure about the first part. A version 2 querier may/may not support V3 so things won't work any way and there will be multiple number of queries on network which may not be desirable.
Another thing I did not understand is the last sentence. What do you mean by 'reselection can happen after every general query'? I think RFC 3376 suggested this to avoid multiple queries on a network. If a router do what is suggested in RFC 3376, at least there will be only one query in the network.
I checked couple of open-source implementation and it seems none of them store this information and always use the highest configured version to send out an IGMP query. Not sure if there was any specific reason for not doing this.
Regards,
Bharat
________________________________________
From: Indranil Bhattacharya [myselfindranil@gmail.com]
Sent: Monday, July 19, 2010 1:43 PM
To: Bharat Joshi
Cc: magma@ietf.org
Subject: Re: [magma] Query on querier version in IGMPv3
Hi Bharat,
Do not lower the querier version. Let the v2 updates's it querier timer from v3 query or let it use it's configured query interval. Otherwise, the reselection can happen after every General query.
Thanks,
Indranil
On Mon, Jul 19, 2010 at 10:39 AM, Bharat Joshi <bharat_joshi@infosys.com<mailto:bharat_joshi@infosys.com>> wrote:
Hi All,
I was re-reading RFC 3376 for handling compatibility for lower version of querier.
In section 7.3.1, it is mentioned that a querier configured to run in V3 mode
should lower its version when it sees a lower version query on the same
network. From that time onwards, a router should send the lower version
queries.
Now the question is, when this router should revert back to its configured higher
version? The text in section 7.3.1 or elsewhere does not talk about this.
Should a timer 'lower_version_querier' be started and updated as and when lower
version queries are removed? Please note this is not same as other-querier-present
timer.
Can someone, who has implemented IGMPv3, let me know how this particular case
has been handled in their implementation?
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***
_______________________________________________
magma mailing list
magma@ietf.org<mailto:magma@ietf.org>
https://www.ietf.org/mailman/listinfo/magma
- [magma] Query on querier version in IGMPv3 Bharat Joshi
- Re: [magma] Query on querier version in IGMPv3 Indranil Bhattacharya
- Re: [magma] Query on querier version in IGMPv3 Bharat Joshi
- Re: [magma] Query on querier version in IGMPv3 Indranil Bhattacharya
- Re: [magma] Query on querier version in IGMPv3 Bharat Joshi
- Re: [magma] Query on querier version in IGMPv3 Kunal Shah