Re: [magma] Question about IGMPv3 state change

Kunal Shah <kunal.shah@ericsson.com> Wed, 09 March 2011 12:22 UTC

Return-Path: <kunal.shah@ericsson.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 ACF473A695E for <magma@core3.amsl.com>; Wed, 9 Mar 2011 04:22:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.771
X-Spam-Level:
X-Spam-Status: No, score=-1.771 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_21=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 kJAhYno4phyD for <magma@core3.amsl.com>; Wed, 9 Mar 2011 04:22:40 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 6E8EB3A67DA for <magma@ietf.org>; Wed, 9 Mar 2011 04:22:40 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id p29CNrFv025713; Wed, 9 Mar 2011 06:23:54 -0600
Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.208]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 9 Mar 2011 07:23:47 -0500
From: Kunal Shah <kunal.shah@ericsson.com>
To: Indranil Bhattacharya <myselfindranil@gmail.com>
Date: Wed, 9 Mar 2011 07:23:45 -0500
Thread-Topic: [magma] Question about IGMPv3 state change
Thread-Index: AcvdYwldiz0mSa54QV6UesQXmSCa2wA8bQ5g
Message-ID: <4FD1E7CD248BF84F86BD4814EDDDBCC150EC03474C@EUSAACMS0703.eamcs.ericsson.se>
References: <4FD1E7CD248BF84F86BD4814EDDDBCC150EA194541@EUSAACMS0703.eamcs.ericsson.se> <AANLkTi=eLgsxAA3xtMHyheASX0AdwWXHDtNhWaYWTzku@mail.gmail.com> <4FD1E7CD248BF84F86BD4814EDDDBCC150EBFAEDFF@EUSAACMS0703.eamcs.ericsson.se> <AANLkTim9aVmk0xkp9=gsRfkyUEqOJASQp_JnGbiZvN5w@mail.gmail.com> <4FD1E7CD248BF84F86BD4814EDDDBCC150EBFAEE10@EUSAACMS0703.eamcs.ericsson.se> <AANLkTinPkewOk2uCQzWjgoKX+a4UDbm0OyJL3cbsf4n9@mail.gmail.com>
In-Reply-To: <AANLkTinPkewOk2uCQzWjgoKX+a4UDbm0OyJL3cbsf4n9@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_4FD1E7CD248BF84F86BD4814EDDDBCC150EC03474CEUSAACMS0703e_"
MIME-Version: 1.0
Cc: "magma@ietf.org" <magma@ietf.org>
Subject: Re: [magma] Question about IGMPv3 state change
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, 09 Mar 2011 12:22:41 -0000

Hi Indranil,

Thanks for your thoughts.

Can someone else on the mailing list confirm this understanding??

Kunal

________________________________
From: Indranil Bhattacharya [mailto:myselfindranil@gmail.com]
Sent: Tuesday, March 08, 2011 1:03 PM
To: Kunal Shah
Cc: magma@ietf.org
Subject: Re: [magma] Question about IGMPv3 state change

Hi Kunal,

             The interpretation of the statement is different. It means router filter mode is exclude but you are receiving include mode reports. That's what is meant as conflict in desired reception state.

Thanks,
Indranil

On Mon, Mar 7, 2011 at 6:40 PM, Kunal Shah <kunal.shah@ericsson.com<mailto:kunal.shah@ericsson.com>> wrote:
Hi Indranil,

>From the RFC "

When a router filter-mode for a group is EXCLUDE, the source record
   list contains two types of sources.  The first type is the set which
   represents conflicts in the desired reception state; this set must be
   forwarded by some router on the network.

"
This means that a source can be in X only if it is being requested for being blocked as well as for being forwarded. In my example below s5 is not being requested to be blocked by any host. So what is the reason for keeping it in X??

Kunal

________________________________
From: Indranil Bhattacharya [mailto:myselfindranil@gmail.com<mailto:myselfindranil@gmail.com>]
Sent: Monday, March 07, 2011 6:33 PM

To: Kunal Shah
Cc: magma@ietf.org<mailto:magma@ietf.org>
Subject: Re: [magma] Question about IGMPv3 state change

Hi Kunal,
             X is for all INCLUDE mode sources. A is TO_IN report. So, s5 should be there in X. Why should s5 be blocked? Somebody wants data from this source.

Thanks,
Indranil

On Mon, Mar 7, 2011 at 5:52 PM, Kunal Shah <kunal.shah@ericsson.com<mailto:kunal.shah@ericsson.com>> wrote:
Hi Indranil,

Consider this,

X= s1,s2
Y= s3,s4

A=s4,s5

Then X+A= s1,s2,s4,s5
Y-A=s3

s5 is in X even when it is not being blocked ??

Kunal

________________________________
From: Indranil Bhattacharya [mailto:myselfindranil@gmail.com<mailto:myselfindranil@gmail.com>]
Sent: Monday, February 28, 2011 6:57 PM
To: Kunal Shah
Cc: magma@ietf.org<mailto:magma@ietf.org>
Subject: Re: [magma] Question about IGMPv3 state change

Hi Kunal,


x = s1,s2
y= s3,s4
a=s2,s3

x+a = s1,s2,s3
y-a = s4
Does it answer your question?

Thanks,
Indranil


On Tue, Feb 15, 2011 at 1:28 AM, Kunal Shah <kunal.shah@ericsson.com<mailto:kunal.shah@ericsson.com>> wrote:
Hi all,

I have a question about IGMPv3 state machine. If a group is in EX(X,Y) and a TO_IN(A) is received, the new state according to the RFC is EX (X+A, Y-A). I think this mean remove all the elements of A from Y and add all elements of A to X. This also implies that sources not removed from Y will still end up being added to X. My question is why cant we add only those elemets of A to X which are removed from Y as opposed to adding all the elements of A to X ??

If only the elements that are removed from Y are added to X, the new state would look like EX (X+(Y*A), Y-A).

Am I missing something here??

Kunal


_______________________________________________
magma mailing list
magma@ietf.org<mailto:magma@ietf.org>
https://www.ietf.org/mailman/listinfo/magma