Re: [magma] IGMPV3 Reports

Bharat Joshi <bharat_joshi@infosys.com> Thu, 17 June 2010 10:45 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 8477D3A694C for <magma@core3.amsl.com>; Thu, 17 Jun 2010 03:45:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[AWL=0.604, 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 PhN3VHJ3Acbx for <magma@core3.amsl.com>; Thu, 17 Jun 2010 03:45:03 -0700 (PDT)
Received: from KECGATE03.infosys.com (Kecgate03.infosysconsulting.com [122.98.10.31]) by core3.amsl.com (Postfix) with ESMTP id 7DCCD3A6959 for <magma@ietf.org>; Thu, 17 Jun 2010 03:45:02 -0700 (PDT)
X-TM-IMSS-Message-ID: <25f0170c001fcb3d@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 25f0170c001fcb3d ; Thu, 17 Jun 2010 16:08:35 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub03.ad.infosys.com ([10.66.236.43]) with mapi; Thu, 17 Jun 2010 16:15:04 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: rajasekar bonthala <rajasekhar.bonthala@gmail.com>, "magma@core3.amsl.com" <magma@core3.amsl.com>, "magma@ietf.org" <magma@ietf.org>
Date: Thu, 17 Jun 2010 16:13:54 +0530
Thread-Topic: [magma] IGMPV3 Reports
Thread-Index: AcsOAoeG8mn62b3eSWuNuRjh30a+7QAB3Q1C
Message-ID: <31D55C4D55BEED48A4459EB64567589A102A09B295@BLRKECMBX02.ad.infosys.com>
References: <AANLkTinZlORYpBx6TU3M9kaje_B5rPDYMyuc8kdvCcXI@mail.gmail.com>
In-Reply-To: <AANLkTinZlORYpBx6TU3M9kaje_B5rPDYMyuc8kdvCcXI@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
Subject: Re: [magma] IGMPV3 Reports
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: Thu, 17 Jun 2010 10:45:05 -0000

IS_XXX reports are generated when a host receives general queries. So it is typically known as current state records.

TO_XXX reports are generally sent when a state change occur. TO_INC/TO_EXC is sent when filter mode changes and so typically known as filter-mode change report.

Thanks,
Bharat
________________________________________
From: magma-bounces@ietf.org [magma-bounces@ietf.org] On Behalf Of rajasekar bonthala [rajasekhar.bonthala@gmail.com]
Sent: Thursday, June 17, 2010 3:20 PM
To: magma@core3.amsl.com; magma@ietf.org
Subject: [magma] IGMPV3 Reports

Hello All,

What is the difference between IS_INCLUDE Report and TO_INCLUDE Report and similarily for IS_EXCL and TO_EXCL?

Thanks,
RajaSekhar