Re: [magma] IGMP Router Group Membership state

rajasekar bonthala <rajasekhar.bonthala@gmail.com> Tue, 19 January 2010 11:48 UTC

Return-Path: <rajasekhar.bonthala@gmail.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 DD1BE3A6765 for <magma@core3.amsl.com>; Tue, 19 Jan 2010 03:48:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level:
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_53=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 P8zT1bYLp4Xo for <magma@core3.amsl.com>; Tue, 19 Jan 2010 03:48:36 -0800 (PST)
Received: from mail-pw0-f41.google.com (mail-pw0-f41.google.com [209.85.160.41]) by core3.amsl.com (Postfix) with ESMTP id 64ABF3A68D9 for <magma@core3.amsl.com>; Tue, 19 Jan 2010 03:48:36 -0800 (PST)
Received: by pwj4 with SMTP id 4so2349422pwj.0 for <magma@core3.amsl.com>; Tue, 19 Jan 2010 03:48:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Vv4AULQn58o/zfxeJ7lEPMcfpjT689Kka1Jmq1ATw8A=; b=Nf04/CMKcXpmSrP/bXocVEvP6MJm4uHbAC6mO8ZzlXF0QHwD5IYNQD2OxK+2W4J921 yReEdl5Fp6WlQ7CEFGl9z/8N3BeyK5gJm6PC4lD4wPaBvbdtgj4jmt7FSL1O86Dw7ohl n1iE0HA6sCuiOr+teYMIH5y2rJNrZpmjTcxEM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=V+UbZ9e0q5p3MwG0C/1d6NvlanGYW6xnKUwvLASvQntsbfZ4Blc4lsaE7wvHKo3AuS i7uhQrjznQZi0BbDcmbGZdcsvJkTrtxQIJ1q8C8BFO5zLnj6vPa9zsNmJ8kqH2t+hNsK Lde0xWF+LOH+dLjDzVTOf5NLeNQ1kbSO1+rfQ=
MIME-Version: 1.0
Received: by 10.143.26.23 with SMTP id d23mr2974359wfj.84.1263901712782; Tue, 19 Jan 2010 03:48:32 -0800 (PST)
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A1010CEE9C5@BLRKECMBX02.ad.infosys.com>
References: <cddcb65a1001180300qb57bbdawbdbd7dc2257a5188@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A1010CEE9C4@BLRKECMBX02.ad.infosys.com> <cddcb65a1001180431v1c3bcb9axa318ccabe53e166@mail.gmail.com> <31D55C4D55BEED48A4459EB64567589A1010CEE9C5@BLRKECMBX02.ad.infosys.com>
Date: Tue, 19 Jan 2010 17:18:32 +0530
Message-ID: <cddcb65a1001190348y5d1d0be7j5cbc4f8257f67a0e@mail.gmail.com>
From: rajasekar bonthala <rajasekhar.bonthala@gmail.com>
To: Bharat Joshi <bharat_joshi@infosys.com>
Content-Type: multipart/alternative; boundary="001636e0accc9f166c047d830cdf"
Cc: "magma@ietf.org" <magma@ietf.org>, "magma@core3.amsl.com" <magma@core3.amsl.com>
Subject: Re: [magma] IGMP Router Group Membership state
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: Tue, 19 Jan 2010 11:48:38 -0000

Thanks a lot Bharath.

I have tried with an example to understand this entry in the table 6.4.2


Router State    Report Rec’d     New Router State     Action
------------    ------------     ----------------     -------

INCLUDE (A)        TO_EX (B)      EXCLUDE (A*B,B-A)    (B-A)=0

                                                      Delete (A-B)

                                                     Send Q(G,A*B)

                                                  Group Timer=GMI



Lets say that the router initially is in INCLUDE state for a group, with the
following sources.

10.10.10.10,  10.10.10.11, 10.10.10.12

Now it received a report "TO EXCLUDE 10.10.10.10"

So, as per the above entry, the router new state should be :

EXCLUDE (A*B,B-A).

So, the router new state is EXCLUDE, with the include list as A*B,

i.e 10.10.10.10, as this is the only one common in A and B.

And the exclude list is B-A, which is nothing but zero in this case.

So, the final state can be said as EXCLUDE nothing for the group (Exclude
list) with 10.10.10.10 requested for forwarding (Include List).

Please let me know whether the understanding is right.



Thanks,

RajaSekhar








On Mon, Jan 18, 2010 at 6:27 PM, Bharat Joshi <bharat_joshi@infosys.com>wrote:

> RajaSekhar,
>
>         I am not sure what you exactly mean by 'please explain on what is
> "EXCLUDE (A*B,B-A)". I understand that this does not look straight forward
> but if you do the calculation with a list of source and group address, you
> will see that this is just perfect. Same is true with the other rule. Please
> use a specific group-address and source address to check them out.
>
>        The sources in the include list are those which has been explicitly
> asked to be allowed. This is maintained so that a router can move from
> Exclude to Include mode as and when group-timer fires. Source in exclude
> list are simply not forwarded and is explicitly asked to be excluded by
> someone on LAN.
>
> Thanks,
> Bharat
> ________________________________________
> From: rajasekar bonthala [rajasekhar.bonthala@gmail.com]
> Sent: Monday, January 18, 2010 6:01 PM
> To: Bharat Joshi
> Cc: magma@ietf.org; magma@core3.amsl.com
> Subject: Re: [magma] IGMP Router Group Membership state
>
> Bharat,
>
> Thanks a lot for the reply.
> In the first rule can you please explain on what is "EXCLUDE (A*B,B-A)" and
> what is the meaning of action of the router i.e :-
>
>  (B-A)=0
>  Delete (A-B)
>  Send Q(G,A*B)
>  Group Timer=GMI
>
> In the seconds rule can you explain me the meaning of "EXCLUDE (X+A,Y-A)"
> and "(A)=GMI
> "
>
> You said that in the exclude mode, it maintains two lists, one is the
> exclude list and the other is the include list. Is it that Exclude list to
> inform about the blocked sources and Include list to inform the sources from
> which the multicast packets are allowed. Am i correct.
>
> Thanks,
> RajaSekhar
>
> On Mon, Jan 18, 2010 at 5:31 PM, Bharat Joshi <bharat_joshi@infosys.com
> <mailto:bharat_joshi@infosys.com>> wrote:
> Raja,
>
>       When the To_Ex(A) is received, router will change its mode to
> EXCLUDE. In exclude mode, it maintains two list. Following rule will apply:
>
>
>       INCLUDE (A)    TO_EX (B)    EXCLUDE (A*B,B-A)       (B-A)=0
>
>       Delete (A-B)
>
>       Send Q(G,A*B)
>
>       Group Timer=GMI
>
>        Now when router generates group-source specific query and it gets a
> response with IS_INC(A). Following rule will apply:
>
>        EXCLUDE (X,Y)  IS_IN (A)     EXCLUDE (X+A,Y-A)        (A)=GMI
>
>       The state as per this will be EXCLUDE mode with source 'A' in Include
> list and exclude list will now be empty.
>
>       Now if the response does not come, state will be EXCLUDE (A*B,B-A)
> which is an empty include list and source 'A' in exclude list.
>
> Thanks,
> Bharat
> ________________________________________
> From: magma-bounces@ietf.org<mailto:magma-bounces@ietf.org> [
> magma-bounces@ietf.org<mailto:magma-bounces@ietf.org>] On Behalf Of
> rajasekar bonthala [rajasekhar.bonthala@gmail.com<mailto:
> rajasekhar.bonthala@gmail.com>]
> Sent: Monday, January 18, 2010 4:30 PM
> To: magma@ietf.org<mailto:magma@ietf.org>; magma@core3.amsl.com<mailto:
> magma@core3.amsl.com>
>  Subject: [magma] IGMP Router Group Membership state
>
> Hi All,
>
> Section 6.4.2 of RFC 3376 talks about on how should IGMP routers respond on
> receiving Filter Mode Change and Source List Change records.
>
> I do not get about what should be the action of the IGMP router in the
> following scenario.
>
> Router is in "INCLUDE A"  state. It receives a report "TO EXCLUDE A". Here,
> IGMP Router sends a Group and Source specific query for the source A group
> B.
>
> Let us say that IGMP Router receives a response "IS INCLUDE A".
>
> What should be the state of the IGMP Router before and after receiving
> response?
> What should be the state of the IGMP Router if it doesn't receive any
> response before the last member query time expires?
>
> In my IGMP Router I could see the state as below :
>
> BEFORE RESPONSE :
>
> atca-f120#show ip igmp groups detail
> Interface:      ge45
> Group:          224.0.6.130
> Uptime:         00:00:20
> Group mode:     Exclude (Expires: 00:06:22)
> Last reporter:  192.168.1.8
> Group source list: (R - Remote, M - SSM Mapping, S - Static)
> Include Source List :
>  Source Address  Uptime    v3 Exp    Fwd  Flags
>  10.10.10.10     00:00:20  00:00:27  Yes  R
>
>
>
>
> NO RESPONSE :
>
> atca-f120#show ip igmp groups detail
> Interface:      ge45
> Group:          224.0.6.130
> Uptime:         00:00:49
> Group mode:     Exclude (Expires: 00:05:53)
> Last reporter:  192.168.1.8
> Group source list: (R - Remote, M - SSM Mapping, S - Static)
> Exclude Source List :
>  Source Address  Uptime    v3 Exp    Fwd  Flags
>  10.10.10.10     00:00:49  stopped   No   R
>
>
> But could not interpret the above outputs. Can anyone help me.
>
> Thanks,
> RajaSekhar
>
>
> **************** 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***
>
>