From magma-bounces@ietf.org Wed Nov 01 21:52:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfSfb-00018S-0A; Wed, 01 Nov 2006 21:51:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfSfa-00018A-2F for magma@ietf.org; Wed, 01 Nov 2006 21:51:06 -0500 Received: from ug-out-1314.google.com ([66.249.92.171]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GfSfU-0003rg-PU for magma@ietf.org; Wed, 01 Nov 2006 21:51:06 -0500 Received: by ug-out-1314.google.com with SMTP id 72so21531ugd for ; Wed, 01 Nov 2006 18:50:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=WoHTm3W3F/GipcmF5kwTuN9Br0MVfedx+Mxt7w4JP+sZ9ku7eCmTcl+X1LWTFLimnWUS1AkMM9Fjdn7TFRn/HYGj7h/8UhrLTkfY+xbiv/75IyFIc8gJYq5oG6TD5EQK9aOEeyglYuBdsgR5/9j3dGf3Pc/W2jzsxMy1Qtfx9yI= Received: by 10.67.105.19 with SMTP id h19mr9233378ugm; Wed, 01 Nov 2006 18:50:57 -0800 (PST) Received: from IBMADCB826D286 ( [59.177.26.243]) by mx.google.com with ESMTP id e33sm1497122ugd.2006.11.01.18.50.55; Wed, 01 Nov 2006 18:50:57 -0800 (PST) Message-ID: <000901c5dfca$10585760$a22d100a@IBMADCB826D286> From: "P K S" To: Date: Mon, 24 Oct 2005 00:09:33 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 3.4 (+++) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [magma] IGMP report suppression X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0544899262==" Errors-To: magma-bounces@ietf.org This is a multi-part message in MIME format. --===============0544899262== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C5D82F.36125200" This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C5D82F.36125200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Why is the IGMP report suppression required in the first place?=20 Regards=20 Parit ------=_NextPart_000_000A_01C5D82F.36125200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Why is the IGMP report suppression = required in the=20 first place?
 
Regards
 Parit
------=_NextPart_000_000A_01C5D82F.36125200-- --===============0544899262== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0544899262==-- From magma-bounces@ietf.org Fri Nov 03 00:33:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfrfB-0002SN-Fa; Fri, 03 Nov 2006 00:32:21 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfrfA-0002NM-4m for magma@ietf.org; Fri, 03 Nov 2006 00:32:20 -0500 Received: from web53503.mail.yahoo.com ([206.190.37.64]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gfrf4-0000Ik-QS for magma@ietf.org; Fri, 03 Nov 2006 00:32:20 -0500 Received: (qmail 76574 invoked by uid 60001); 3 Nov 2006 05:32:12 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=DJ4ng2s05NwWKEBTExyRm0jU6ojrCsjPuqZyMfGgr0VQA+X1F2skPpbuFPDsxG3/mLsqnA6aBLscg93X6cBb4hJACURNnj+4t6gUEMos7iarVGUJOzuRi7S/W5AZMG5A2Ptm4dpJmvqOaaMRy1HqX4oL36cUrW7ZJxXlEi/CDIA= ; Message-ID: <20061103053212.76572.qmail@web53503.mail.yahoo.com> Received: from [59.145.141.130] by web53503.mail.yahoo.com via HTTP; Thu, 02 Nov 2006 21:32:12 PST Date: Thu, 2 Nov 2006 21:32:12 -0800 (PST) From: Princy Elizabeth Subject: Re: [magma] IGMP report suppression To: P K S , magma@ietf.org In-Reply-To: <000901c5dfca$10585760$a22d100a@IBMADCB826D286> MIME-Version: 1.0 X-Spam-Score: 0.1 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0455881696==" Errors-To: magma-bounces@ietf.org --===============0455881696== Content-Type: multipart/alternative; boundary="0-925587461-1162531932=:76322" Content-Transfer-Encoding: 8bit --0-925587461-1162531932=:76322 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit IGMP V1 and V2 reports are sent per group. Consider a LAN with 10 hosts each interested in the same 10 groups. If reports suppression were not employed, every Query interval there would be 10 reports sent out by each of the 10 hosts ==> 100 reports which unnecessarily increase the traffic on the LAN. For the router, it is sufficient to know that there is one interested member for a group on the LAN. So 1 report per group would have sufficed. This precisely is what is done through report suppression. In IGMP V3, a single report can contain the report for all the groups a host is interested in. Thus there is no need for report suppression here since the number of reports would be generally, equal to the number of hosts only. I hope that clarifies your query. - Princy P K S wrote: Why is the IGMP report suppression required in the first place? Regards Parit _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --------------------------------- Get your email and see which of your friends are online - Right on the new Yahoo.com --0-925587461-1162531932=:76322 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
IGMP V1 and V2 reports are sent per group. Consider a LAN with 10 hosts each interested in the same 10 groups. If reports suppression were not employed, every Query interval there would be 10 reports sent out by each of the 10 hosts ==> 100 reports which unnecessarily increase the traffic on the LAN. For the router, it is sufficient to know that there is one interested member for a group on the LAN. So 1 report per group would have sufficed. This precisely is what is done through report suppression. In IGMP V3, a single report can contain the report for all the groups a host is interested in. Thus there is no need for report suppression here since the number of reports would be generally, equal to the number of hosts only.
 
I hope that clarifies your query.
 
- Princy


P K S <paritoshkshah@gmail.com> wrote:
Why is the IGMP report suppression required in the first place?
 
Regards
 Parit
_______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma

Get your email and see which of your friends are online - Right on the new Yahoo.com --0-925587461-1162531932=:76322-- --===============0455881696== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0455881696==-- From magma-bounces@ietf.org Fri Nov 03 03:21:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfuHC-0007D8-5E; Fri, 03 Nov 2006 03:19:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfuHA-0007Cw-GU for magma@ietf.org; Fri, 03 Nov 2006 03:19:44 -0500 Received: from web53509.mail.yahoo.com ([206.190.37.70]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GfuH5-0008JU-6m for magma@ietf.org; Fri, 03 Nov 2006 03:19:44 -0500 Received: (qmail 77266 invoked by uid 60001); 3 Nov 2006 08:19:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=awy9o06QdMNzx53zGPYxHHTDb/OQq0M2lSnie+/tqMTLHgNr1VQ/nrzNYX1F/yn5XzNPXes4mhBGcQ/clRACHsxcaU/E5elYfebMR8g3jTUUNFsu7J/t22gY557ayTHpBaH8rnN/mjSKnCeCbxN8i3HI0d3HxW+NpwbtXFcaQ0w= ; Message-ID: <20061103081939.77264.qmail@web53509.mail.yahoo.com> Received: from [59.145.141.130] by web53509.mail.yahoo.com via HTTP; Fri, 03 Nov 2006 00:19:39 PST Date: Fri, 3 Nov 2006 00:19:39 -0800 (PST) From: Princy Elizabeth To: magma@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [magma] IP Router alert option in IGMP messages X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0464559245==" Errors-To: magma-bounces@ietf.org --===============0464559245== Content-Type: multipart/alternative; boundary="0-1179712294-1162541979=:77124" Content-Transfer-Encoding: 8bit --0-1179712294-1162541979=:77124 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi all, I had a query on the usage of the IP Router alert option in IGMP messages. I do not understand what exactly is the significance of this option. What does a non-multicast enabled router do on receiving an IGMP 'Join' or a 'Query' with the IP Router alert option set? Does a multicast enabled router actually require this option for recognising IGMP packets in its fast path? Don't most routers look at the IGMP protocol field for identifying IGMP packets? Thanks and regards, Princy __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-1179712294-1162541979=:77124 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hi all,
 
I had a query on the usage of the IP Router alert option in IGMP messages. I do not understand what exactly is the significance of this option. What does a non-multicast enabled router do on receiving an IGMP 'Join' or a 'Query' with the IP Router alert option set? Does a multicast enabled router actually require this option for recognising IGMP packets in its fast path? Don't most routers look at the IGMP protocol field for identifying IGMP packets?
 
Thanks and regards,
Princy

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-1179712294-1162541979=:77124-- --===============0464559245== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0464559245==-- From magma-bounces@ietf.org Fri Nov 03 17:39:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gg7fp-0000cv-L5; Fri, 03 Nov 2006 17:38:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gg7fn-0000cn-Qa for magma@ietf.org; Fri, 03 Nov 2006 17:38:03 -0500 Received: from e3.ny.us.ibm.com ([32.97.182.143]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gg7fm-0000mh-Bl for magma@ietf.org; Fri, 03 Nov 2006 17:38:03 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e3.ny.us.ibm.com (8.13.8/8.12.11) with ESMTP id kA3MbvQX023160 for ; Fri, 3 Nov 2006 17:37:57 -0500 Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay02.pok.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id kA3MbvWO253080 for ; Fri, 3 Nov 2006 17:37:57 -0500 Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id kA3MbvNo004710 for ; Fri, 3 Nov 2006 17:37:57 -0500 Received: from RCHASA14.RCHLAND.IBM.COM (d27mc103.rchland.ibm.com [9.10.229.52]) by d01av01.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id kA3MbuHO004692 for ; Fri, 3 Nov 2006 17:37:57 -0500 In-Reply-To: <20061103053212.76572.qmail@web53503.mail.yahoo.com> To: magma@ietf.org MIME-Version: 1.0 Subject: Re: [magma] IGMP report suppression X-Mailer: Lotus Notes Release 7.0 HF85 November 04, 2005 From: Christy L Norman Message-ID: Date: Fri, 3 Nov 2006 16:37:55 -0600 X-MIMETrack: Serialize by Router on D27mc103/27/M/IBM(Release 7.0.2|September 26, 2006) at 11/03/2006 04:37:56 PM, Serialize complete at 11/03/2006 04:37:56 PM X-Spam-Score: 0.1 (/) X-Scan-Signature: 25eb6223a37c19d53ede858176b14339 X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0176913014==" Errors-To: magma-bounces@ietf.org This is a multipart message in MIME format. --===============0176913014== Content-Type: multipart/alternative; boundary="=_alternative 007C47C98625721B_=" This is a multipart message in MIME format. --=_alternative 007C47C98625721B_= Content-Type: text/plain; charset="US-ASCII" I agree with the answer to Parit's question. IGMPv1 and v2 reports can be suppressed to reduce unnecessary traffic. However, in regards to the reason for the absence of report suppression in v3 - I believe it is due to the presence of sources in an IGMPv3 report. One record could easily be omitted from a report (record suppression?). All listeners to a group may have different sources making up their per-interface states and to check the sources of all hosts' reports would be a bit of work for the host. In addition to this reason, RFC 2236 states in 5.2, "Instead of using a single interface timer, implementations are recommended to spread transmission of such Report messages over the interval (0, [Max Resp Time])." In this case, the operation will be much like IGMPv1 & v2 - but report suppression isn't required if you happen to be implementing that method of reporting - because of the issue with the sources. Do you agree? - Christy Princy Elizabeth 11/02/2006 11:32 PM To P K S , magma@ietf.org cc Subject Re: [magma] IGMP report suppression IGMP V1 and V2 reports are sent per group. Consider a LAN with 10 hosts each interested in the same 10 groups. If reports suppression were not employed, every Query interval there would be 10 reports sent out by each of the 10 hosts ==> 100 reports which unnecessarily increase the traffic on the LAN. For the router, it is sufficient to know that there is one interested member for a group on the LAN. So 1 report per group would have sufficed. This precisely is what is done through report suppression. In IGMP V3, a single report can contain the report for all the groups a host is interested in. Thus there is no need for report suppression here since the number of reports would be generally, equal to the number of hosts only. I hope that clarifies your query. - Princy P K S wrote: Why is the IGMP report suppression required in the first place? Regards Parit _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma Get your email and see which of your friends are online - Right on the new Yahoo.com _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --=_alternative 007C47C98625721B_= Content-Type: text/html; charset="US-ASCII"
I agree with the answer to Parit's question. IGMPv1 and v2 reports can be suppressed to reduce unnecessary traffic. However, in regards to the reason for the absence of report suppression in v3 - I believe it is due to the presence of sources in an IGMPv3 report. One record could easily be omitted from a report (record suppression?). All listeners to a group may have different sources making up their per-interface states and to check the sources of  all hosts' reports would be a bit of work for the host.  

In addition to this reason, RFC 2236 states in 5.2,  "Instead of using a single interface timer, implementations are recommended to spread transmission of such Report messages over the interval (0, [Max Resp Time])."  In this case, the operation will be much like IGMPv1 & v2 - but report suppression isn't required if you happen to be implementing that method of reporting - because of the issue with the sources.

Do you agree?

- Christy


Princy Elizabeth <princyte@yahoo.com>

11/02/2006 11:32 PM

To
P K S <paritoshkshah@gmail.com>, magma@ietf.org
cc
Subject
Re: [magma] IGMP report suppression





IGMP V1 and V2 reports are sent per group. Consider a LAN with 10 hosts each interested in the same 10 groups. If reports suppression were not employed, every Query interval there would be 10 reports sent out by each of the 10 hosts ==> 100 reports which unnecessarily increase the traffic on the LAN. For the router, it is sufficient to know that there is one interested member for a group on the LAN. So 1 report per group would have sufficed. This precisely is what is done through report suppression. In IGMP V3, a single report can contain the report for all the groups a host is interested in. Thus there is no need for report suppression here since the number of reports would be generally, equal to the number of hosts only.
 
I hope that clarifies your query.
 
- Princy


P K S <paritoshkshah@gmail.com> wrote:
Why is the IGMP report suppression required in the first place?
 
Regards
 Parit
_______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma

 

Get your email and see which of your friends are online - Right on the new Yahoo.com _______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma

--=_alternative 007C47C98625721B_=-- --===============0176913014== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0176913014==-- From magma-bounces@ietf.org Fri Nov 03 20:01:57 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gg9uU-0001Hq-IA; Fri, 03 Nov 2006 20:01:22 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gg9uT-0001Hb-6g for magma@ietf.org; Fri, 03 Nov 2006 20:01:21 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gg9uQ-0007o7-Ra for magma@ietf.org; Fri, 03 Nov 2006 20:01:21 -0500 Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-4.cisco.com with ESMTP; 03 Nov 2006 17:01:12 -0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAFZ1S0WrR7MV/2dsb2JhbAA X-IronPort-AV: i="4.09,386,1157353200"; d="scan'208"; a="1861984069:sNHT34226824" Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA411Cxx029431; Fri, 3 Nov 2006 17:01:12 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kA411CAo003292; Fri, 3 Nov 2006 17:01:12 -0800 (PST) Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 3 Nov 2006 17:01:12 -0800 Received: from [192.168.1.27] ([10.21.112.161]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 3 Nov 2006 17:01:11 -0800 In-Reply-To: <20061103081939.77264.qmail@web53509.mail.yahoo.com> References: <20061103081939.77264.qmail@web53509.mail.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: John Zwiebel Subject: Re: [magma] IP Router alert option in IGMP messages Date: Fri, 3 Nov 2006 17:01:11 -0800 To: Princy Elizabeth X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 04 Nov 2006 01:01:11.0853 (UTC) FILETIME=[B852CDD0:01C6FFAC] DKIM-Signature: a=rsa-sha1; q=dns; l=1452; t=1162602072; x=1163466072; c=relaxed/simple; s=sjdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:John=20Zwiebel=20 |Subject:Re=3A=20[magma]=20IP=20Router=20alert=20option=20in=20IGMP=20messages; X=v=3Dcisco.com=3B=20h=3DJzj1jCdOKNjFNrjVbO2AC7iYCVA=3D; b=X6MVaQFbL/DfbKN/nTuGIDaoUWtB4n3LhsRgyd+45VpW5j0qs+LQgP1gPV4CUckEQjt0HAAq hMOI/UytUAGARBAGmaooQpODiRkuMTbtq1WaA+XA7OhWUAR+OlKUwMSc; Authentication-Results: sj-dkim-1.cisco.com; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: magma@ietf.org X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org On Nov 3, 2006, at 12:19 AM, Princy Elizabeth wrote: > Hi all, > > I had a query on the usage of the IP Router alert option in IGMP > messages. I do not understand what exactly is the significance of > this option. What does a non-multicast enabled router do on > receiving an IGMP 'Join' or a 'Query' with the IP Router alert > option set? Does a multicast enabled router actually require this > option for recognising IGMP packets in its fast path? Don't most > routers look at the IGMP protocol field for identifying IGMP packets? Most routers have implemented it. (The RA option) It should be configurable since some hosts have not. Its most useful for igmpv2 because IGMP host reports are sent to the multicast group address not a specific address (as in IGMPv3) which the router is a member of. Yes if the RA is not configured the router looks at the IP protocol field, but the problem is that the router must listen to the complete multicast group range just to see if there might be an IGMP packet. Using RA, the router doesn't have to work so hard. > > Thanks and regards, > Princy > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > _______________________________________________ > magma mailing list > magma@ietf.org > https://www1.ietf.org/mailman/listinfo/magma _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Sun Nov 05 15:03:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgoC5-0001hc-0t; Sun, 05 Nov 2006 15:02:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgoC3-0001h8-FL for magma@ietf.org; Sun, 05 Nov 2006 15:02:11 -0500 Received: from smtp10.poczta.interia.pl ([80.48.65.10] helo=smtp4.poczta.interia.pl) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GgoBz-0000wP-PA for magma@ietf.org; Sun, 05 Nov 2006 15:02:11 -0500 Received: by smtp4.poczta.interia.pl (INTERIA.PL, from userid 502) id 42A38376F3E; Sun, 5 Nov 2006 21:02:03 +0100 (CET) Received: from poczta.interia.pl (f33.poczta.interia.pl [10.217.2.33]) by smtp4.poczta.interia.pl (INTERIA.PL) with ESMTP id 46FA4376EE4; Sun, 5 Nov 2006 21:01:57 +0100 (CET) Received: by poczta.interia.pl (Postfix, from userid 502) id 575CC4B3246; Sun, 5 Nov 2006 21:01:57 +0100 (CET) Received: from localhost (localhost.interia.pl [127.0.0.1]) by poczta.interia.pl (Postfix) with ESMTP id 0540D4B3237; Sun, 5 Nov 2006 21:01:56 +0100 (CET) Date: 05 Nov 2006 21:01:55 +0100 From: tbartcz@interia.pl Subject: Re: Re: [magma] IGMP report suppression To: Christy L Norman MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1804289383-1162756915=:70193" X-ORIGINATE-IP: 194.187.181.11 IMPORTANCE: Normal X-MSMAIL-PRIORITY: Normal X-PRIORITY: 3 X-Mailer: PSE3 Message-Id: <20061105200156.0540D4B3237@poczta.interia.pl> X-EMID: bb540acc X-Spam-Score: 0.8 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Cc: magma@ietf.org X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org --0-1804289383-1162756915=:70193 Content-Type: TEXT/HTML; CHARSET=ISO-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE =0A=0A= =0A=0A=0A=0A=0AHell= o,
=0AI hope that you do not mind that I has joined your discussion. =0AI was recently studying IGMPv3 quite hard in order to get all ins and o= uts of=0Athis protocol version. I agree with the preceding speaker that in = case of=0AIGMPv1 and v2 reports are suppressed in order to reduce the traff= ic. I also=0Ashare the view that there is no point to suppress receiver Rep= orts messages in=0Acase of IGMPv3 due to the issue with sources.
=0A=0AHowever I not quite get the intention of the second part of the email. = Let's=0Aextend the example presented in the first reply. Assume that we hav= e Ethernet=0Asegment with then receivers, ten groups and 100 sources in eac= h group. As it=0Awas mentioned earlier we will have 10 Report messages in r= eply to Query message=0Ain case of IGMPv1 and v2. Each Report message will = concern to different group.=0ADue to report suppression only one receiver w= ill answer per group and the=0AReports will be sent per group address.
= =0AIn case of IGMPv3 situation is a bit different. All router will answer t= o Query=0Amessage but they will not sent separate Report message for each g= roup. Each one=0Aof receivers will sent just one Report message, on address= 224.0.0.22,=0Acontaining information about reception stage for each of 10 = groups. Since there=0Ais only one message sent by receiver it has informati= on about many groups.=0AMoreover information for each group contains list o= f sources (in our case there=0Aare 100 sources so the list can be quite lon= g). As a result Report messages in=0Acase of IGMPv3 are quite large. For th= at reason RFC 3376 states:
=0A "Instead of using a=0Asingle interface timer, implementations a= re recommended to spread transmission=0Aof such Report messages over the in= terval (0, [Max Resp Time])."
=0AAdvising to = not set single Report message in response to Query but divide it=0Aand sent= it spread over some time interval. Nevertheless it does not seem to me=0At= hat this behavior is similar to behavior of  I= GMPv1 and v2 because all receivers will sent Report message for=0Aone parti= cular group. Not like in case of IGMPv1 and v2 where only one router=0Aansw= ers per group. What are your views on that? Do you are with me?
=0A
= =0ARegards
=0ATomasz Bartczak
Christy L Norman napisa= =B3(a):

=0A
I agree with the answer = to Parit's question.=0AIGMPv1 and v2 reports can be suppressed to reduce un= necessary traffic.=0AHowever, in regards to the reason for the absence of r= eport suppression=0Ain v3 - I believe it is due to the presence of sources = in an IGMPv3 report.=0AOne record could easily be omitted from a report (re= cord suppression?).=0AAll listeners to a group may have different sources m= aking up their per-interface=0Astates and to check the sources of  all= hosts' reports would be a=0Abit of work for the host.  =0A
= =0A
In addition to this reason, RFC= 2236=0Astates in 5.2,  "Instead of using = a single=0Ainterface timer, implementations are recommended to spread trans= mission=0Aof such Report messages over the interval (0, [Max Resp Time])."=0A In this case, the = operation will be much like IGMPv1 & v2 - but=0Areport suppression isn'= t required if you happen to be implementing that=0Amethod of reporting - be= cause of the issue with the sources.=0A
=0A
Do you agree?=0A
=0A
- Christy
=0A=0A
=0A
=0A
=0A=0A=0A
Princy Elizabeth <princyte@yahoo.com>=0A= =0A

11/02/2006 11:32 PM=0A

=0A=0A=0A=0A=0A
=0A
To
=0A		P K S &l= t;paritoshkshah@gmail.com>,=0Amagma@ietf.org=0A
=0A
cc
=0A		=0A
=0ASubject=0ARe: [magma] IGMP report s= uppression
=0A
=0A=0A=0A
=0A
=0A
=0A
=0A
=0A
IGMP V1 and V2 repor= ts are sent per group. Consider a=0ALAN with 10 hosts each interested in th= e same 10 groups. If reports suppression=0Awere not employed, every Query i= nterval there would be 10 reports sent=0Aout by each of the 10 hosts =3D=3D= > 100 reports which unnecessarily increase=0Athe traffic on the LAN. For= the router, it is sufficient to know that there=0Ais one interested member= for a group on the LAN. So 1 report per group=0Awould have sufficed. This = precisely is what is done through report suppression.=0AIn IGMP V3, a singl= e report can contain the report for all the groups a=0Ahost is interested i= n. Thus there is no need for report suppression here=0Asince the number of = reports would be generally, equal to the number of=0Ahosts only. =0A=
 =0A
I hope that clari= fies your query.=0A
 =0A
- Princy
=0A
=0A
=0AP K S <paritoshkshah@gmail.c= om> wrote:=0A
Why is t= he IGMP report suppression required=0Ain the first place? =0A
 =0A
Regards <= /font>=0A
 Parit=0A
_______________________________________________
=0Amagma mai= ling list
=0Amagma@ietf.org
=0Ahttps://www1.ietf.org/mailman/listinfo= /magma=0A
=0A

 =0A

Get your email and see which of your friends are online=0A- Right = on the new=0AYahoo.com _______________________= ________________________
=0Amagma mailing list
=0Amagma@ietf.org
= =0Ahttps://www1.ietf.org/mailman/listinfo/magma
=0A=0A



=0A
----------------------------------------------------------------------
Jestes kierowca? To poczytaj! >>> http://link.interia.pl/f199e
--0-1804289383-1162756915=:70193 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-2 Content-ID: Content-Disposition: ATTACHMENT; FILENAME=BRAK_NAZWY _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --0-1804289383-1162756915=:70193 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --0-1804289383-1162756915=:70193-- From magma-bounces@ietf.org Wed Nov 08 18:32:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghwt5-0008KQ-TP; Wed, 08 Nov 2006 18:31:19 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghwt5-0008KL-HN for magma@ietf.org; Wed, 08 Nov 2006 18:31:19 -0500 Received: from bay12-f10.bay12.hotmail.com ([64.4.35.10] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ghwt4-0005Z5-8o for magma@ietf.org; Wed, 08 Nov 2006 18:31:19 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 8 Nov 2006 15:31:17 -0800 Message-ID: Received: from 216.31.211.11 by by12fd.bay12.hotmail.msn.com with HTTP; Wed, 08 Nov 2006 23:31:16 GMT X-Originating-IP: [216.31.211.11] X-Originating-Email: [klltm@hotmail.com] X-Sender: klltm@hotmail.com From: "K T" To: magma@ietf.org Bcc: Date: Wed, 08 Nov 2006 23:31:16 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 08 Nov 2006 23:31:17.0355 (UTC) FILETIME=[FD047BB0:01C7038D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [magma] source specific multicast X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org Hi, I am little new to multicast/igmp code here. I am looking for some info on following issues. 1) In Linux, How do we initialize variable "ipv4_devconf.force_igmp_version" to version 3. by default it is inialized to 2 in old kernel. I need to find a place where this variable is initialized. 2) Is there any multimedia player for windows XP through which you can send a source specific multicast (SSM)/IGMPv3 request to the network from XP machine by selecting a particular source.? Thank you BC _________________________________________________________________ Use your PC to make calls at very low rates https://voiceoam.pcs.v2s.live.com/partnerredirect.aspx _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Wed Nov 08 22:36:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gi0gn-0003Co-VF; Wed, 08 Nov 2006 22:34:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gi0gl-0003Ce-JM for magma@ietf.org; Wed, 08 Nov 2006 22:34:51 -0500 Received: from mail1.rz.fhtw-berlin.de ([141.45.5.103]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gi0gh-00045B-99 for magma@ietf.org; Wed, 08 Nov 2006 22:34:51 -0500 Received: from itchy.rz.fhtw-berlin.de ([141.45.5.94] helo=itchy) by mail1.rz.fhtw-berlin.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.42 (FreeBSD)) id 1Gi0gc-000C2s-Ay; Thu, 09 Nov 2006 04:34:42 +0100 Date: Thu, 9 Nov 2006 04:34:42 +0100 (CET) From: Matthias Waehlisch X-X-Sender: mw@itchy.rz.fhtw-berlin.de To: K T Subject: Re: [magma] source specific multicast In-Reply-To: Message-ID: References: Organization: HRZ - FHTW Berlin MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: magma@ietf.org X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org Hi, On Wed, 8 Nov 2006, K T wrote: > 1) In Linux, How do we initialize variable "ipv4_devconf.force_igmp_version" > to version 3. by default it is inialized to 2 in old kernel. I need to > find a place where this variable is initialized. > in general you use the "sysctl" command or editing /etc/sysctl.conf. > 2) Is there any multimedia player for windows XP through which you can send > a source specific multicast (SSM)/IGMPv3 request to the network from XP > machine by selecting a particular source.? > I don't know ... But there is a ssmping tool by Stig Venaas running also under Windows XP: http://www.venaas.no/multicast/ssmping/. best regards matthias -- Matthias Waehlisch :. HRZ - FHTW Berlin :. link-lab :. Treskowallee 8, 10318 Berlin, Germany :. Hoenower Str. 35/PF16, 10318 Berlin :. mailto:mw@fhtw-berlin.de :. mailto:mw@link-lab.net :. http://home.fhtw-berlin.de/~mw :. http://www.link-lab.net _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Thu Nov 09 12:31:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiDkM-0004VZ-FR; Thu, 09 Nov 2006 12:31:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GiDkM-0004VT-4D for magma@ietf.org; Thu, 09 Nov 2006 12:31:26 -0500 Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GiDkK-0002s7-PX for magma@ietf.org; Thu, 09 Nov 2006 12:31:26 -0500 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 09 Nov 2006 09:31:24 -0800 Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id kA9HVNQR008340; Thu, 9 Nov 2006 09:31:23 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id kA9HVNW6014825; Thu, 9 Nov 2006 09:31:23 -0800 (PST) Received: from xmb-sjc-22c.amer.cisco.com ([128.107.191.47]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Nov 2006 09:31:23 -0800 Received: from [192.168.1.27] ([10.21.112.197]) by xmb-sjc-22c.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 9 Nov 2006 09:31:23 -0800 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: John Zwiebel Subject: Re: [magma] source specific multicast Date: Thu, 9 Nov 2006 09:31:32 -0800 To: K T X-Mailer: Apple Mail (2.752.2) X-OriginalArrivalTime: 09 Nov 2006 17:31:23.0115 (UTC) FILETIME=[E042B3B0:01C70424] DKIM-Signature: a=rsa-sha1; q=dns; l=759; t=1163093484; x=1163957484; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jzwiebel@cisco.com; z=From:John=20Zwiebel=20 |Subject:Re=3A=20[magma]=20source=20specific=20multicast |Sender:; X=v=3Dcisco.com=3B=20h=3Dd/YlAY83CzuTj8ASJqaBZz4SXPw=3D; b=VxvgXj6k/LJYLpHfc+OhKX6LKtkl1m5vWSvxEoDeGZQZz5gbsbh1m8dzpi9fxnYoGkafgRZH ZWL/qC1fTL8zpiOM3c36RFxTqNvdbwgQ/jYE+Fnunnykj/Q454qGMoqG; Authentication-Results: sj-dkim-4; header.From=jzwiebel@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: magma@ietf.org X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org On Nov 8, 2006, at 3:31 PM, K T wrote: > > 2) Is there any multimedia player for windows XP through which you > can send a source specific multicast (SSM)/IGMPv3 request to the > network from XP machine by selecting a particular source.? > Absolutely: VLC videolan.org You can source just about anything and send it out via IPv4 or IPv6 unicast and/or multicast. even multiple streams at the same time. You can even receive a unicast stream and convert it to a multicast stream On those hosts (windows) that support IGMPv3 the manual says: To receive a SSM (source specific multicast) stream, you can use: % vlc udp:server_address@multicast_address[:server_port] This is a very nice application and it is free. _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Wed Nov 15 03:11:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkFq5-0004x5-Jq; Wed, 15 Nov 2006 03:09:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkFpM-0004T8-Cd for magma@ietf.org; Wed, 15 Nov 2006 03:09:00 -0500 Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177] helo=mail.alcatel-sbell.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkFdl-00023a-F9 for magma@ietf.org; Wed, 15 Nov 2006 02:57:03 -0500 Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1]) by mail.alcatel-sbell.com.cn (8.13.8/8.13.8/Alcanet1.0) with ESMTP id kAF7uTto009978 for ; Wed, 15 Nov 2006 15:56:30 +0800 Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Wed, 15 Nov 2006 15:56:51 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 15 Nov 2006 15:56:51 +0800 Message-ID: <9570C1261494D54D9D3115BC2C83429A03407EB8@asbmail2.sbell.com.cn> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: About how to subscribe Magma mailing list Thread-Index: AccIi5xBKwGCarOmQvyATgFMclvYag== From: "CTO YAO Chunyan" To: X-OriginalArrivalTime: 15 Nov 2006 07:56:51.0859 (UTC) FILETIME=[9C44F630:01C7088B] X-imss-version: 2.044 X-imss-result: Passed X-imss-approveListMatch: *@alcatel-sbell.com.cn X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Subject: [magma] About how to subscribe Magma mailing list X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0130728257==" Errors-To: magma-bounces@ietf.org This is a multi-part message in MIME format. --===============0130728257== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7088B.9C323486" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7088B.9C323486 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Dear all, sorry to disturb you. could you tell me how to subscribe Magma mailing list?=20 I sent the a mail to magma-request@ietf.org with only subscribe in the mail body as illustrated in Magma WG Web page, But there is no any response. =20 Thanks in advance! =20 =20 with regards!=20 Chunyan ------_=_NextPart_001_01C7088B.9C323486 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
Dear all, sorry to = disturb you.=20 could you tell me how to subscribe Magma mailing = list? 
          I = sent the a=20 mail to magma-request@ietf.org with only subscribe in = the mail=20 body as illustrated in Magma WG Web page, But there is no any=20 response.
 
          Thanks = in=20 advance!
          &nbs= p;          
 
          &nbs= p;    =20 with regards! 
          &nbs= p;            = ;  =20 Chunyan
------_=_NextPart_001_01C7088B.9C323486-- --===============0130728257== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0130728257==-- From magma-bounces@ietf.org Wed Nov 15 03:57:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkGZw-0007Zi-GT; Wed, 15 Nov 2006 03:57:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GkGZv-0007Zd-2u for magma@ietf.org; Wed, 15 Nov 2006 03:57:07 -0500 Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177] helo=mail.alcatel-sbell.com.cn) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GkGZs-00032y-Qq for magma@ietf.org; Wed, 15 Nov 2006 03:57:07 -0500 Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1]) by mail.alcatel-sbell.com.cn (8.13.8/8.13.8/Alcanet1.0) with ESMTP id kAF8uLpE000907 for ; Wed, 15 Nov 2006 16:56:35 +0800 Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); Wed, 15 Nov 2006 16:56:59 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [magma] About how to subscribe Magma mailing list Date: Wed, 15 Nov 2006 16:56:10 +0800 Message-ID: <9570C1261494D54D9D3115BC2C83429A03407FAA@asbmail2.sbell.com.cn> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [magma] About how to subscribe Magma mailing list Thread-Index: AccIi5xBKwGCarOmQvyATgFMclvYagAByPlA From: "CTO YAO Chunyan" To: X-OriginalArrivalTime: 15 Nov 2006 08:56:59.0374 (UTC) FILETIME=[028410E0:01C70894] X-imss-version: 2.044 X-imss-result: Passed X-imss-approveListMatch: *@alcatel-sbell.com.cn X-Spam-Score: 0.0 (/) X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0355741094==" Errors-To: magma-bounces@ietf.org This is a multi-part message in MIME format. --===============0355741094== content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C70893.E5A2EAC2" This is a multi-part message in MIME format. ------_=_NextPart_001_01C70893.E5A2EAC2 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Dear all, I have received from = magma-request@ietf.org, and now I suuceed in subscribing the Mailing = list.It seems i am a bit precipitant. ;-{ =20 =20 Could some one tell me why there is no other Anycast Group = Management proposals for recent four years? =20 =20 There was a prosal in the year 2002: = "draft-haberman-ipngwg-host-anycast-01.txt".The title of the proposal if = "Host-based Anycast using MLD", but there seems no other development on = the draft from then on. =20 =20 =20 Thanks in advance! =20 Chunyan =20 =20 =20 -----Original Message----- From: CTO YAO Chunyan=20 Sent: 2006=C4=EA11=D4=C215=C8=D5 15:57 To: magma@ietf.org Subject: [magma] About how to subscribe Magma mailing list Dear all, sorry to disturb you. could you tell me how to subscribe Magma = mailing list?=20 I sent the a mail to = magma-request@ietf.org with only subscribe in the mail body as = illustrated in Magma WG Web page, But there is no any response. =20 Thanks in advance! =20 =20 with regards!=20 Chunyan ------_=_NextPart_001_01C70893.E5A2EAC2 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable Message
Dear all, I have=20 received from magma-request@ietf.org, and now I suuceed in=20 subscribing the Mailing list.It seems i am a bit precipitant.=20 ;-{
 
 
       &nbs= p; =20 Could some one tell me why there is no other Anycast Group = Management=20 proposals for recent four years?
 
 
       &nbs= p;  There=20 was a prosal in the year 2002: "draft-haberman-ipngwg-host-anycast-01.txt".The = title of the=20 proposal if "Host-based Anycast using MLD", but there seems = no other=20 development on the draft from then on.
       &nbs= p;   =20
       &nbs= p;   
 
       &nbs= p;    Thanks=20 in advance!
 
       &nbs= p;            = ;            =             &= nbsp;   =20 Chunyan
       &nbs= p;    =20
       &nbs= p;  =20
       &nbs= p;      =20  
-----Original Message-----
From: CTO = YAO Chunyan=20
Sent: 2006=C4=EA11=D4=C215=C8=D5 15:57
To:=20 magma@ietf.org
Subject: [magma] About how to subscribe Magma = mailing=20 list

Dear all, sorry = to disturb=20 you. could you tell me how to subscribe Magma mailing=20 list? 
          I = sent the=20 a mail to magma-request@ietf.org with only subscribe in = the mail=20 body as illustrated in Magma WG Web page, But there is no any=20 response.
 
          Thanks = in=20 advance!
          &nbs= p;          
 
          &nbs= p;    =20 with regards! 
          &nbs= p;            = ;  =20 Chunyan
------_=_NextPart_001_01C70893.E5A2EAC2-- --===============0355741094== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============0355741094==-- From magma-bounces@ietf.org Fri Nov 24 01:44:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnUlt-0001jb-GK; Fri, 24 Nov 2006 01:42:49 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnUls-0001f3-I4 for magma@ietf.org; Fri, 24 Nov 2006 01:42:48 -0500 Received: from [203.196.196.71] (helo=BLR-MAIL.NETD.COM) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnUlp-0000yk-Nb for magma@ietf.org; Fri, 24 Nov 2006 01:42:48 -0500 Received: from netd.com ([10.91.2.5]) (authenticated bits=0) by BLR-MAIL.NETD.COM (8.12.8/8.12.8) with ESMTP id kAO6pQRC021058; Fri, 24 Nov 2006 12:21:33 +0530 Message-ID: <456693BB.1070304@netd.com> Date: Fri, 24 Nov 2006 12:09:55 +0530 From: AJAY THAKUR User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: magma@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-NetD-India-MailScanner-Information: Please contact the NetD-India Sysadmin for more information X-NetD-India-MailScanner: Found to be clean X-MailScanner-From: tajay@netd.com X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [magma] rfc 4601 PIM query X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org HI, I have one doubt about PIM register messages. rfc 4601 sec. 4.4 PIM register messsages : "The Designated Router (DR) on a LAN or point-to-point link encapsulates multicast packets from local sources to the RP for the relevant group unless it recently received a Register-Stop message for that (S,G) or (*,G) from the RP. When the DR receives a Register-Stop message from the RP, it starts a Register-Stop Timer to maintain this state. Just before the Register-Stop Timer expires, the DR sends a Null-Register Message to the RP to allow the RP to refresh the Register-Stop information at the DR. If the Register- Stop Timer actually expires, the DR will resume encapsulating packets from the source to the RP." I m confused after reading " Just before the Register-Stop Timer expires". Does this mean we need one more timer here? Thanks Ajay _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Fri Nov 24 01:59:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnV1S-00013A-Vl; Fri, 24 Nov 2006 01:58:54 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnV1R-00012X-Ia for magma@ietf.org; Fri, 24 Nov 2006 01:58:53 -0500 Received: from gateout02.mbox.net ([165.212.64.22]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnV1O-0003dn-8J for magma@ietf.org; Fri, 24 Nov 2006 01:58:53 -0500 Received: from gateout02.mbox.net (gateout02.mbox.net [165.212.64.22]) by gateout02.mbox.net (Postfix) with ESMTP id DBF9E194A; Fri, 24 Nov 2006 06:58:40 +0000 (GMT) Received: from gateout02.mbox.net [127.0.0.1] by gateout02.mbox.net via mtad (C8.MAIN.3.31J) with ESMTP id 304kkXg7n0260Mo2; Fri, 24 Nov 2006 06:58:39 GMT Received: from gateout02.mbox.net [127.0.0.1] by gateout02.mbox.net via mtad (C8.MAIN.3.31J) with ESMTP id 303kkXg7l0125Mo2; Fri, 24 Nov 2006 06:58:37 GMT X-USANET-Routed: 2 gwsout-vs R:localhost:1825 Received: from GW2.EXCHPROD.USA.NET [165.212.116.254] by gateout02.mbox.net via smtad (C8.MAIN.3.32M); Fri, 24 Nov 2006 06:58:37 GMT X-USANET-Source: 165.212.116.254 IN slakshman@nexthop.com GW2.EXCHPROD.USA.NET X-USANET-MsgId: XID258kkXg7l3425Xo2 Received: from VS4.EXCHPROD.USA.NET ([10.116.208.142]) by GW2.EXCHPROD.USA.NET with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Nov 2006 23:58:36 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [magma] rfc 4601 PIM query Date: Thu, 23 Nov 2006 23:57:40 -0700 Message-ID: <7ADC90A5E95BA74DA5CA5A6C390D530507AD3F5D@VS4.EXCHPROD.USA.NET> In-Reply-To: <456693BB.1070304@netd.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [magma] rfc 4601 PIM query Thread-Index: AccPlDDd22zHmRo2TWWjwLrQCHeKRgAAZenA From: "Santosh Lakshmana Rao" To: "AJAY THAKUR" , X-OriginalArrivalTime: 24 Nov 2006 06:58:36.0797 (UTC) FILETIME=[F6C492D0:01C70F95] X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: magma-bounces@ietf.org Another timer is not required.=20 Register-Stop Timer can serve the purpose. However two timeout values are needed - Register_Suppression_Time and Register_Probe_Time as mentioned in the RFC. Santosh -----Original Message----- From: AJAY THAKUR [mailto:tajay@netd.com]=20 Sent: Friday, November 24, 2006 12:10 PM To: magma@ietf.org Subject: [magma] rfc 4601 PIM query HI, I have one doubt about PIM register messages. rfc 4601 sec. 4.4 PIM register messsages : "The Designated Router (DR) on a LAN or point-to-point link encapsulates multicast packets from local sources to the RP for the relevant group unless it recently received a Register-Stop message for that (S,G) or (*,G) from the RP. When the DR receives a Register-Stop message from the RP, it starts a Register-Stop Timer to maintain this state. Just before the Register-Stop Timer expires, the DR sends a Null-Register Message to the RP to allow the RP to refresh the Register-Stop information at the DR. If the Register- Stop Timer actually expires, the DR will resume encapsulating packets from the source to the RP." I m confused after reading " Just before the Register-Stop Timer=20 expires". Does this mean we need one more timer here? Thanks Ajay _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma From magma-bounces@ietf.org Fri Nov 24 02:02:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnV4y-0001Th-3x; Fri, 24 Nov 2006 02:02:32 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GnV4w-0001TZ-0p for magma@ietf.org; Fri, 24 Nov 2006 02:02:30 -0500 Received: from ug-out-1314.google.com ([66.249.92.174]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GnV4u-0004SM-KY for magma@ietf.org; Fri, 24 Nov 2006 02:02:30 -0500 Received: by ug-out-1314.google.com with SMTP id 72so530297ugd for ; Thu, 23 Nov 2006 23:02:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=d69EC//iCBV7XtrB/zmnBFgcJdHsbGbahUlpZfKTwwSt7mSCtqAO4jsJ3o50kgGW7vCitEfyzoZqkX9VdLuSDKd2grj1ztR4Kvolwj/tkvkuThdY7SNngFIqpgenHS3RETti72c8IdqAbBSrAcpZz4haF8TX+/rb1kZMmuDq+hE= Received: by 10.67.30.6 with SMTP id h6mr6428847ugj.1164351747207; Thu, 23 Nov 2006 23:02:27 -0800 (PST) Received: by 10.66.224.18 with HTTP; Thu, 23 Nov 2006 23:02:27 -0800 (PST) Message-ID: <84f679e0611232302g37747bb7id021edaec935686f@mail.gmail.com> Date: Fri, 24 Nov 2006 12:32:27 +0530 From: "Suresh kannan" To: "AJAY THAKUR" Subject: Re: [magma] rfc 4601 PIM query In-Reply-To: <456693BB.1070304@netd.com> MIME-Version: 1.0 References: <456693BB.1070304@netd.com> X-Spam-Score: 0.1 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: magma@ietf.org X-BeenThere: magma@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multicast and Anycast Group Membership List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1143027200==" Errors-To: magma-bounces@ietf.org --===============1143027200== Content-Type: multipart/alternative; boundary="----=_Part_27764_25747217.1164351747028" ------=_Part_27764_25747217.1164351747028 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Ajay, Its upto your implementation. Register-Stop timer is required as per RFC. You can use another timer to send NULL register message or you can use the same timer to implement sending NULL register before actually it expiring. means you should have some mechanism that let register-stop let expire before actuall timer and reset to somemore time. ( as per calculation of probe, suppression timeout). Thanks, Regards, Suresh kannan. On 11/24/06, AJAY THAKUR wrote: > > HI, > I have one doubt about PIM register messages. > > rfc 4601 sec. 4.4 PIM register messsages : > > "The Designated Router (DR) on a LAN or point-to-point link > encapsulates multicast packets from local sources to the RP for the > relevant group unless it recently received a Register-Stop message > for that (S,G) or (*,G) from the RP. When the DR receives a > Register-Stop message from the RP, it starts a Register-Stop Timer to > maintain this state. Just before the Register-Stop Timer expires, > the DR sends a Null-Register Message to the RP to allow the RP to > refresh the Register-Stop information at the DR. If the Register- > Stop Timer actually expires, the DR will resume encapsulating packets > from the source to the RP." > > I m confused after reading " Just before the Register-Stop Timer > expires". Does this mean we need one more timer here? > > Thanks > Ajay > > > _______________________________________________ > magma mailing list > magma@ietf.org > https://www1.ietf.org/mailman/listinfo/magma > ------=_Part_27764_25747217.1164351747028 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi Ajay,

Its upto your implementation. Register-Stop timer is required as per RFC. You can use another timer to send NULL register message or you can use the same timer to implement sending NULL register before actually it expiring. means you should have some mechanism that let register-stop let expire before actuall timer and reset to somemore time. ( as per calculation of probe, suppression timeout).

Thanks,
Regards,
Suresh kannan.


On 11/24/06, AJAY THAKUR <tajay@netd.com> wrote:
HI,
I have one doubt about PIM register messages.

rfc 4601 sec. 4.4 PIM register messsages :

    "The Designated Router (DR) on a LAN or point-to-point link
    encapsulates multicast packets from local sources to the RP for the
    relevant group unless it recently received a Register-Stop message
    for that (S,G) or (*,G) from the RP.  When the DR receives a
    Register-Stop message from the RP, it starts a Register-Stop Timer to
    maintain this state.  Just before the Register-Stop Timer expires,
    the DR sends a Null-Register Message to the RP to allow the RP to
    refresh the Register-Stop information at the DR.  If the Register-
    Stop Timer actually expires, the DR will resume encapsulating packets
    from the source to the RP."

I m confused after reading " Just before the Register-Stop Timer
expires". Does this mean we need one more timer here?

Thanks
Ajay


_______________________________________________
magma mailing list
magma@ietf.org
https://www1.ietf.org/mailman/listinfo/magma

------=_Part_27764_25747217.1164351747028-- --===============1143027200== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ magma mailing list magma@ietf.org https://www1.ietf.org/mailman/listinfo/magma --===============1143027200==--