Re: [magma] Igmp Group-Source specific Retransmission

Bharat Joshi <bharat_joshi@infosys.com> Wed, 02 June 2010 12:37 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 B7C003A6A26 for <magma@core3.amsl.com>; Wed, 2 Jun 2010 05:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level:
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5 tests=[BAYES_50=0.001, J_CHICKENPOX_31=0.6]
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 V8EX5biQympq for <magma@core3.amsl.com>; Wed, 2 Jun 2010 05:37:20 -0700 (PDT)
Received: from KECGATE03.infosys.com (Kecgate03.infosys.com [122.98.10.31]) by core3.amsl.com (Postfix) with ESMTP id C163B3A69BE for <magma@ietf.org>; Wed, 2 Jun 2010 05:37:17 -0700 (PDT)
X-TM-IMSS-Message-ID: <d917917500174174@KECGATE03.infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by KECGATE03.infosys.com ([122.98.10.31]) with ESMTP (TREND IMSS SMTP Service 7.0) id d917917500174174 ; Wed, 2 Jun 2010 18:00:56 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub03.ad.infosys.com ([10.66.236.43]) with mapi; Wed, 2 Jun 2010 18:07:02 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "Kudachi, Deepak S" <deepak.kudachi@hp.com>, "magma@core3.amsl.com" <magma@core3.amsl.com>, "magma@ietf.org" <magma@ietf.org>
Date: Wed, 2 Jun 2010 18:07:00 +0530
Thread-Topic: [magma] Igmp Group-Source specific Retransmission
Thread-Index: AcsCRJ9W3LAdoIoSQAW743092YBjfAAASjjgAAJj1Z8=
Message-ID: <31D55C4D55BEED48A4459EB64567589A102A09B227@BLRKECMBX02.ad.infosys.com>
References: <AANLkTilLU9c4Duz-NcMa-vbQbBNVu-JyOWR54t9p15rE@mail.gmail.com>, <BF084A81AE527F4FB1447EA170E8A76547AEB1F894@GVW1157EXB.americas.hpqcorp.net>
In-Reply-To: <BF084A81AE527F4FB1447EA170E8A76547AEB1F894@GVW1157EXB.americas.hpqcorp.net>
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: Re: [magma] Igmp Group-Source specific Retransmission
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: Wed, 02 Jun 2010 12:37:21 -0000

Deepak,

      It would be better if you handle the example with IP addresses. Also consider how the state in the hosts are and what final state should be there after things stabilize.

      For the below example, I think you should attach the robustness count as query count with the source addresses and then as and when timer fires, you prepare a group-source specific query, send it out and reduce the query count for each source address you include in the query. Once the query count for a source address reaches zero, it is removed from the list and when all sources are removed from the list, we do not restart the timer.

      So we will end up sending three queries. But all the three queries will carry different sources in the list.

      I hope this helps.

Regards,
Bharat
________________________________________
From: magma-bounces@ietf.org [magma-bounces@ietf.org] On Behalf Of Kudachi, Deepak S [deepak.kudachi@hp.com]
Sent: Wednesday, June 02, 2010 5:50 PM
To: magma@core3.amsl.com; magma@ietf.org
Subject: [magma]  Igmp Group-Source specific Retransmission

Hi All,

I was going through the IGMPv3 RFC 3376  and was not clear on the below
Mentioned section.

/*---------------------------------------------------------------------------------------------------------*/
6.6.3.2. Building and Sending Group and Source Specific Queries

   When a table action "Send Q(G,X)" is encountered by a querier in the
   table in section 6.4.2, the following actions must be performed for
   each of the sources in X of group G, with source timer larger than
   LMQT:

   o Set number of retransmissions for each source to [Last Member Query
     Count].

   o Lower source timer to LMQT.

   The router must then immediately send a group and source specific
   query as well as schedule [Last Member Query Count - 1] query
   retransmissions to be sent every [Last Member Query Interval] over
   [Last Member Query Time].  The contents of these queries are
   calculated as follows.
/*-----------------------------------------------------------------*/


This section talks about how the group-source specific queries are build and
Send out.

Suppose our robustness variable is set to 2(default value).
And Last Member Query Interval is 10 Sec.

Any group-source specific query need to be transmitted robustness number of times
That is 2 times in our case and separated by LMQI which 10 sec.
So 2 queries has to be sent across Last Member Query Time which is 20 sec.


Now suppose we already sent Q(G,X) query for a group at T1 with set of sources. And we received
A report which causes new Q(G,(X+Y)) needs to be sent and T2( before T1+LMQI). Where Y is new set of sources to be
Queried. New Query will be sent with all sources merged from previous and new(x + y).

So the sources x already two queries will be sent and not separated by LMQI in this scenario.

My question is whether we need to send one more query after LMQI ( at T1+LMQI) for x
Set of sources for this group?

If we need to then we will be sending 3 queries for x set of sources as follows.

Time interval T1
Time interval T2
Time interval T1+LMQI

Which is not correct.

Let me know whether we should send query for x set of sources for this group
At T1+LMQI interval.

Thanks and Regards
Deepak