From owner-idmr@cs.ucl.ac.uk Fri Jun 1 06:54:13 2001 Received: from pan2.cs.ucl.ac.uk ([128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA04151 for ; Fri, 1 Jun 2001 06:54:13 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 1 Jun 2001 10:48:38 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 1 Jun 2001 10:48:32 +0100 Received: from snowstorm.mail.pipex.net by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 1 Jun 2001 10:48:58 +0100 Received: (qmail 14649 invoked from network); 1 Jun 2001 09:48:56 -0000 Received: from usercn10.uk.uudial.com (HELO vaionote) (62.188.155.95) by smtp-6.dial.pipex.com with SMTP; 1 Jun 2001 09:48:56 -0000 Message-ID: <004e01c0ea80$051d65a0$df9bbc3e@vaionote> Reply-To: Tony Ballardie From: Tony Ballardie To: tpagtzis , idmr , fenner References: <3B16A368.6449D603@iprg.nokia.com> Subject: Re: multicast and load balancing Date: Fri, 1 Jun 2001 10:42:00 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit Theo, > IGMPvX and MLD mention that the router has to be a Querier in the > particular interface so that multicast packets can be forwarded. When > one has two multicast enabled routers and would like to load balance > traffic between the two routers it seems to me that there is problem > with load balancing since only the interface in any of the 2 IGMP-enable > routers, with the lowest IPv6 addr will win the Querier election. So in > that case the second router cannot load balance multicast forwarding on > that link. there's usually a distinction made between the IGMP Querier and the multicast routing protocol's "designated router" (DR), which is responsible for forwarding mcast traffic to/from the LAN. The explicit join protocols, including PIM, have a DR and a DR election mechanism (usually via priority config'd Hellos) so the DR need not be the Querier. But, the elected DR is DR for *all* groups, so it's not really load balancing. To enable group based load balancing there'd need to be one DR per group (or better... group range). But that makes DR election more complex and ramps up the DR election traffic on the LAN. Not done at present, though it would be the ideal. cheers Tony From owner-idmr@cs.ucl.ac.uk Fri Jun 1 12:43:14 2001 Received: from pan2.cs.ucl.ac.uk ([128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11898 for ; Fri, 1 Jun 2001 12:43:13 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 1 Jun 2001 15:16:52 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 1 Jun 2001 14:48:48 +0100 Received: from mailhost.iprg.nokia.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 1 Jun 2001 14:49:19 +0100 Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id GAA20756; Fri, 1 Jun 2001 06:49:15 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f51DnEX13430; Fri, 1 Jun 2001 06:49:14 -0700 X-mProtect: Fri, 1 Jun 2001 06:49:14 -0700 Nokia Silicon Valley Messaging Protection Received: from tpagtzis.iprg.nokia.com (205.226.2.115, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com(P1.5 smtpdxkAJbs; Fri, 01 Jun 2001 06:49:12 PDT Message-ID: <3B179D58.DECB953E@iprg.nokia.com> Date: Fri, 01 Jun 2001 06:49:12 -0700 From: Theo Pagtzis Reply-To: tpagtzis@IPRG.nokia.com Organization: UCL/NOKIA X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1-STABLE i386) X-Accept-Language: el, en MIME-Version: 1.0 To: Tony Ballardie CC: idmr@cs.ucl.ac.uk, fenner@research.att.com Subject: Re: multicast and load balancing References: <3B16A368.6449D603@iprg.nokia.com> <004e01c0ea80$051d65a0$df9bbc3e@vaionote> Content-Type: text/plain; charset=us-ascii Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Hi Tony, thanks for that. If, however, the DR router is empowered to fwd multicast traffic to/fro the LAN, regardless of being the Querier or not, then what's the real benefit of having the Querier election and even more why should the router be constraint by the rule that if the router is not a querier in that interface it cannot forward traffic to it? It seems to me that the DR overrides that and the IGMP protocol makes no mention about it..that is that the IGMP querier can be overriden if the multicast enabled routers is a DR one.. Theo UCL/ Mobile Systems Tony Ballardie wrote: > Theo, > > > IGMPvX and MLD mention that the router has to be a Querier in the > > particular interface so that multicast packets can be forwarded. When > > one has two multicast enabled routers and would like to load balance > > traffic between the two routers it seems to me that there is problem > > with load balancing since only the interface in any of the 2 IGMP-enable > > routers, with the lowest IPv6 addr will win the Querier election. So in > > that case the second router cannot load balance multicast forwarding on > > that link. > > there's usually a distinction made between the IGMP Querier and > the multicast routing protocol's "designated router" (DR), which is > responsible for forwarding mcast traffic to/from the LAN. The explicit join > protocols, including PIM, have a DR and a DR election mechanism > (usually via priority config'd Hellos) so the DR need not be the Querier. > But, the elected DR is DR for *all* groups, so it's not really load > balancing. > > To enable group based load balancing there'd need to be one DR per > group (or better... group range). But that makes DR election more complex > and ramps up the DR election traffic on the LAN. Not done at present, > though it would be the ideal. > > cheers > > Tony From owner-idmr@cs.ucl.ac.uk Fri Jun 1 14:19:01 2001 Received: from pan2.cs.ucl.ac.uk ([128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA15324 for ; Fri, 1 Jun 2001 14:19:00 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 1 Jun 2001 17:48:11 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 1 Jun 2001 17:48:06 +0100 Received: from mail-blue.research.att.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 1 Jun 2001 17:48:34 +0100 Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 9E1B54DDA3; Fri, 1 Jun 2001 12:48:33 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA26232; Fri, 1 Jun 2001 12:48:33 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA17565; Fri, 1 Jun 2001 09:48:32 -0700 (PDT) Message-Id: <200106011648.JAA17565@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: tpagtzis@iprg.nokia.com Subject: Re: multicast and load balancing Cc: ballardie@dial.pipex.com, idmr@cs.ucl.ac.uk References: <3B16A368.6449D603@iprg.nokia.com> <004e01c0ea80$051d65a0$df9bbc3e@vaionote> <3B179D58.DECB953E@iprg.nokia.com> Date: Fri, 1 Jun 2001 09:48:31 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk >why should the >router be constraint by the rule that if the router is not a querier in that >interface it cannot forward traffic to it? It's not. This is a constraint imposted by IGMP proxying, but is not a general rule. Bill From owner-idmr@cs.ucl.ac.uk Tue Jun 5 14:46:26 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA28065 for ; Tue, 5 Jun 2001 14:46:25 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Tue, 5 Jun 2001 18:11:21 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Tue, 5 Jun 2001 18:11:15 +0100 Received: from lorraine.loria.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 5 Jun 2001 18:11:33 +0100 Received: from loria.fr (pcscanner1.loria.fr [152.81.12.42]) by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with ESMTP id TAA22754 for ; Tue, 5 Jun 2001 19:11:26 +0200 (MET DST) Message-ID: <3B1D12BE.278C3AE5@loria.fr> Date: Tue, 05 Jun 2001 19:11:26 +0200 From: lahmadi Organization: LORIA X-Mailer: Mozilla 4.7 [fr]C-CCK-MCD (WinNT; I) X-Accept-Language: fr, en MIME-Version: 1.0 To: idmr@cs.ucl.ac.uk Subject: when member leaves the group Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit hi, how the multicast router knows that a member leaves the group ? does it will use a timer per member ? regards, From owner-idmr@cs.ucl.ac.uk Wed Jun 6 01:12:45 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA07922 for ; Wed, 6 Jun 2001 01:12:44 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 04:48:24 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 04:48:17 +0100 Received: from wiproecmx1.wipro.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 04:48:00 +0100 Received: from ecvwall1.wipro.com (ecvwall1.wipro.com [192.168.181.23]) by wiproecmx1.wipro.com (8.11.3/8.11.3) with SMTP id f56E3nr15821 for ; Wed, 6 Jun 2001 09:04:04 -0500 (GMT) Received: from 192 ([192.168.91.136]) by ecmail.mail.wipro.com (Netscape Messaging Server 4.15) with SMTP id GEHOUR00.5IT; Wed, 6 Jun 2001 09:10:03 +0530 Message-ID: <006001c0ee3a$8aabc280$885ba8c0@168.245.18.wipinfo.soft.net> From: gangadhar singh To: lahmadi , idmr References: <3B1D12BE.278C3AE5@loria.fr> Subject: Re: when member leaves the group Date: Wed, 6 Jun 2001 09:11:16 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit hi, When a host leaves a multicast group , if it is the last host to reply to a query with the membership report for that group , it send a leave group message to all-router group (224.0.0.2). When a querier router receives a Leave group message for a group that has group members on the reception interface , it sends Group-Specific queries every [Last member query Interval] to the group being left. If no reports are received after the response time of the last query expires , the mulitcast routers assume that the group has no local member for the group and that it need not forward remotely-originated multicasts messages for that group onto the attach network. So basically a timer will be running for each group.If no periodic report are sent within the[ Last member query Interval ] ,routers will know that the members have left the group. regards singh ----- Original Message ----- From: lahmadi To: Sent: Tuesday, June 05, 2001 10:41 PM Subject: when member leaves the group > hi, > how the multicast router knows that a member leaves the group ? does it > will use a timer per member ? > > regards, From owner-idmr@cs.ucl.ac.uk Wed Jun 6 01:16:20 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA08142 for ; Wed, 6 Jun 2001 01:16:19 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 06:03:41 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 06:03:33 +0100 Received: from 202.54.64.6 by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 06:04:04 +0100 Received: from grofw (router.hclt.co.in [202.54.64.1]) by saraswathi.hclt.co.in with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id ML81QZAD; Wed, 6 Jun 2001 10:46:40 +0530 Received: from VIJAYC ([192.168.232.219]) by gayatri.hclt.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id L8Z2DM5C; Wed, 6 Jun 2001 10:31:53 +0530 From: Vijayanand C To: lahmadi Cc: idmr Subject: RE: when member leaves the group Date: Wed, 6 Jun 2001 10:38:43 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3B1D12BE.278C3AE5@loria.fr> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit IGMP takes care of sending a leave message to the router Vijay -----Original Message----- From: owner-idmr@cs.ucl.ac.uk [mailto:owner-idmr@cs.ucl.ac.uk]On Behalf Of lahmadi Sent: Tuesday, June 05, 2001 10:41 PM To: idmr@cs.ucl.ac.uk Subject: when member leaves the group hi, how the multicast router knows that a member leaves the group ? does it will use a timer per member ? regards, From owner-idmr@cs.ucl.ac.uk Wed Jun 6 08:09:00 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA27122 for ; Wed, 6 Jun 2001 08:09:00 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 12:07:40 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 12:07:34 +0100 Received: from lorraine.loria.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 12:07:58 +0100 Received: from euvezin.loria.fr (euvezin.loria.fr [152.81.11.90]) by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with SMTP id NAA23420 for ; Wed, 6 Jun 2001 13:07:55 +0200 (MET DST) From: Abdelkader Lahmadi To: idmr Subject: member leaves the group in IGMPv3 Date: Wed, 6 Jun 2001 13:03:56 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <01060613075400.06675@euvezin.loria.fr> Content-Transfer-Encoding: 8bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 8bit hi, IGMv2 take the care of sending a leave message, but in IGNPv3, there`nt this kind of messages, so in IGMPv3 when the router know that a member leave a group ? regards -- --------------------------------------------- Lahmadi Abdelkader LORIA - UHP NANCY I CAMPUS SCIENTIFIQUE B.P.239 54506 VANDOEUVRE-LES-NANCY CEDEX E-mail : lahmadi@loria.fr --------------------------------------------- From owner-idmr@cs.ucl.ac.uk Wed Jun 6 10:02:53 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01210 for ; Wed, 6 Jun 2001 10:02:51 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 13:53:19 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 13:53:13 +0100 Received: from sky.irisa.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 13:53:44 +0100 Received: from irisa.fr (rocha.irisa.fr [131.254.13.52]) by sky.irisa.fr (8.9.3/8.9.3) with ESMTP id OAA17626 for ; Wed, 6 Jun 2001 14:53:43 +0200 (MET DST) Message-ID: <3B1E27D7.AE69365E@irisa.fr> Date: Wed, 06 Jun 2001 14:53:44 +0200 From: Ali Boudani Organization: INRIA - RENNES X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en, fr MIME-Version: 1.0 To: idmr@cs.ucl.ac.uk Subject: IGMP- DR and querier Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit If the DR and the querier are different in a network, how the DR knows about the group memberships?? (this case can exist in PIM where DR is the highest IP address and the querier is the lowest IP address) Thanx From owner-idmr@cs.ucl.ac.uk Wed Jun 6 10:05:44 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01279 for ; Wed, 6 Jun 2001 10:05:43 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 13:55:36 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 13:55:30 +0100 Received: from sky.irisa.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 13:56:03 +0100 Received: from irisa.fr (rocha.irisa.fr [131.254.13.52]) by sky.irisa.fr (8.9.3/8.9.3) with ESMTP id OAA17900; Wed, 6 Jun 2001 14:56:00 +0200 (MET DST) Message-ID: <3B1E2861.1E2CBF72@irisa.fr> Date: Wed, 06 Jun 2001 14:56:01 +0200 From: Ali Boudani Organization: INRIA - RENNES X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en, fr MIME-Version: 1.0 To: Abdelkader Lahmadi CC: idmr Subject: Re: member leaves the group in IGMPv3 References: <01060613075400.06675@euvezin.loria.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit More specific !!!! there is a leave message from (S, G) Abdelkader Lahmadi wrote: > hi, > IGMv2 take the care of sending a leave message, but in IGNPv3, there`nt this > kind of messages, so in IGMPv3 when the router know that a member leave a group > ? > regards -- > --------------------------------------------- > Lahmadi Abdelkader > LORIA - UHP NANCY I > CAMPUS SCIENTIFIQUE B.P.239 > 54506 VANDOEUVRE-LES-NANCY CEDEX > E-mail : lahmadi@loria.fr > --------------------------------------------- From owner-idmr@cs.ucl.ac.uk Wed Jun 6 12:48:04 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05120 for ; Wed, 6 Jun 2001 12:48:03 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 16:36:18 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 16:36:11 +0100 Received: from presque.djinesys.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 16:36:35 +0100 Received: from shaitan.nexthop.com ([141.211.130.156]) by presque.djinesys.com (8.11.1/8.11.1) with ESMTP id f56FaWH18037; Wed, 6 Jun 2001 11:36:32 -0400 (EDT) (envelope-from dhb@shaitan.nexthop.com) Received: (from dhb@localhost) by shaitan.nexthop.com (8.11.0/8.11.0) id f56FaVM17573; Wed, 6 Jun 2001 11:36:31 -0400 (EDT) Date: Wed, 6 Jun 2001 11:36:31 -0400 From: David Barnett To: Ali Boudani Cc: idmr@cs.ucl.ac.uk Subject: Re: IGMP- DR and querier Message-ID: <20010606113631.A17527@shaitan.nexthop.com> References: <3B1E27D7.AE69365E@irisa.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B1E27D7.AE69365E@irisa.fr>; from aboudani@irisa.fr on Wed, Jun 06, 2001 at 02:53:44PM +0200 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk On Wed, Jun 06, 2001 at 02:53:44PM +0200, Ali Boudani wrote: > If the DR and the querier are different in a network, how the DR knows > about the group memberships?? > (this case can exist in PIM where DR is the highest IP address and the > querier is the lowest IP address) > Thanx > In my understanding... The goal of the querier mechanism in IGMP is not to have one machine on a lan keeping all of the group state, but instead to reduce the amount of routing trafic. In the case of IGMP the membership reports are sent to a multicast group, which allows any router on the lan to listen to reports without actively querying. Any router on the lan can and will need to listen to these reports to keep track of group memberships. In the case of IGMPv3 all membership reports are multicast to the IGMPv3-CAPABLE multicast routers group. For IGMPv2 or v1 the reports are multicast to the group of interest. So basically, the fact that a router is not querier only relieves it of the duty of querying the multicast listeners. It still must listen and process the IGMP traffic. -Dave From owner-idmr@cs.ucl.ac.uk Wed Jun 6 12:48:12 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05131 for ; Wed, 6 Jun 2001 12:48:11 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 16:37:40 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 16:37:33 +0100 Received: from presque.djinesys.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 16:38:04 +0100 Received: from nexthop.com ([141.211.130.160]) by presque.djinesys.com (8.11.1/8.11.1) with ESMTP id f56FbvH18089; Wed, 6 Jun 2001 11:37:57 -0400 (EDT) (envelope-from ctbrown@nexthop.com) Message-Id: <200106061537.f56FbvH18089@presque.djinesys.com> From: Christopher Thomas Brown Subject: Re: member leaves the group in IGMPv3 To: Abdelkader Lahmadi CC: idmr@cs.ucl.ac.uk In-Reply-To: Your message of "Wed, 06 Jun 2001 13:03:56 +0200." <01060613075400.06675@euvezin.loria.fr> Date: Wed, 06 Jun 2001 11:37:57 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk The member leaving the group sends a V3 membership report for the group with mode INCLUDE and sources NULL. ctbrown On Wed, 06 Jun 2001 13:03:56 +0200 Abdelkader Lahmadi wrote: > > hi, > IGMv2 take the care of sending a leave message, but in IGNPv3, there`nt thi >s >kind of messages, so in IGMPv3 when the router know that a member leave a grou >p >? >regards -- >--------------------------------------------- > Lahmadi Abdelkader > LORIA - UHP NANCY I > CAMPUS SCIENTIFIQUE B.P.239 > 54506 VANDOEUVRE-LES-NANCY CEDEX > E-mail : lahmadi@loria.fr >--------------------------------------------- > From owner-idmr@cs.ucl.ac.uk Wed Jun 6 12:51:44 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA05262 for ; Wed, 6 Jun 2001 12:51:42 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 17:49:19 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 17:49:09 +0100 Received: from net013s.hetnet.nl by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 17:49:42 +0100 Received: from wdegraafdp866 ([209.131.52.217]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.687.68); Wed, 6 Jun 2001 18:49:03 +0200 Message-ID: <001b01c0eea8$ae39bdb0$d93483d1@inktomi.com> From: Wilbert de Graaf To: Abdelkader Lahmadi Cc: idmr References: <01060613075400.06675@euvezin.loria.fr> Subject: Re: member leaves the group in IGMPv3 Date: Wed, 6 Jun 2001 09:49:39 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit Hi Lahmadi, > IGMv2 take the care of sending a leave message, but in IGNPv3, there`nt this > kind of messages, so in IGMPv3 when the router know that a member leave a group > ? There is something similar in IGMPv3, although there are two cases: 1) The host is in exclude mode, like ex {A}. Then it will send to_in {} 2) The host is in include mode, like inc {A}. Then it will send block {A} So only for 1) it is similar to an IGMPv2 leave. For 2) it shouldn't matter for the router. (For a layer 2 switch such a s ethernetswitch it's a little bit more difficult I guess). Wilbert From owner-idmr@cs.ucl.ac.uk Wed Jun 6 13:04:26 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA05667 for ; Wed, 6 Jun 2001 13:04:26 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 16:33:42 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 16:33:36 +0100 Received: from presque.djinesys.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 16:34:08 +0100 Received: from nexthop.com ([141.211.130.160]) by presque.djinesys.com (8.11.1/8.11.1) with ESMTP id f56FXwH17905; Wed, 6 Jun 2001 11:33:58 -0400 (EDT) (envelope-from ctbrown@nexthop.com) Message-Id: <200106061533.f56FXwH17905@presque.djinesys.com> From: Christopher Thomas Brown Subject: Re: IGMP- DR and querier To: Ali Boudani CC: idmr@cs.ucl.ac.uk In-Reply-To: Your message of "Wed, 06 Jun 2001 14:53:44 +0200." <3B1E27D7.AE69365E@irisa.fr> Date: Wed, 06 Jun 2001 11:33:57 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk A non-querier keeps take of group memberships also. It just never sends out query messages. ctbrown On Wed, 06 Jun 2001 14:53:44 +0200 Ali Boudani wrote: >If the DR and the querier are different in a network, how the DR knows >about the group memberships?? >(this case can exist in PIM where DR is the highest IP address and the >querier is the lowest IP address) >Thanx > > From owner-idmr@cs.ucl.ac.uk Wed Jun 6 17:39:06 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA09563 for ; Wed, 6 Jun 2001 17:39:06 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 21:28:28 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 21:28:22 +0100 Received: from lorraine.loria.fr by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 21:28:55 +0100 Received: from vignot.loria.fr (IDENT:lahmadi@vignot.loria.fr [152.81.2.146]) by lorraine.loria.fr (8.9.3/8.9.3/8.9.3/JCG-DG) with SMTP id WAA09303; Wed, 6 Jun 2001 22:28:53 +0200 (MET DST) Content-Type: text/plain; charset="iso-8859-1" From: Abdelkader Lahmadi To: Wilbert de Graaf Subject: leave the group in IGMPv3 Date: Wed, 6 Jun 2001 22:28:53 +0200 X-Mailer: KMail [version 1.2] Cc: idmr@cs.ucl.ac.uk MIME-Version: 1.0 Message-Id: <01060622285300.01060@vignot.loria.fr> Content-Transfer-Encoding: 8bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 8bit hi Wilbert, but in the 2) case the router can confuse between a host that want to block{A} and a host just want to leave the group .In my implementation of IGMPv3 router side, i want to know if a particular member had leave a group, so i think to use a timer by member and the router state will be: (group, fmode, sources, members) and a member will have this state: (adress, timer). the member timer will be update when the router receive a report from this host, if the member timer expires then the router will know that this host had leave the group. Lahmadi From owner-idmr@cs.ucl.ac.uk Wed Jun 6 18:45:51 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA10149 for ; Wed, 6 Jun 2001 18:45:50 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 6 Jun 2001 21:43:52 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 6 Jun 2001 21:43:45 +0100 Received: from net013s.hetnet.nl by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 6 Jun 2001 21:44:18 +0100 Received: from wdegraafdp866 ([209.131.52.217]) by hetnet.nl with Microsoft SMTPSVC(5.5.1877.687.68); Wed, 6 Jun 2001 22:43:37 +0200 Message-ID: <00e001c0eec9$73a51610$d93483d1@inktomi.com> From: Wilbert de Graaf To: Abdelkader Lahmadi Cc: idmr References: <01060622285300.01060@vignot.loria.fr> Subject: Re: leave the group in IGMPv3 Date: Wed, 6 Jun 2001 13:44:14 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit Hi Lahmadi, That's right. If your implementation keeps track of membership of indivual hosts, including it's source filters, you'll be able to tell that a host dropped actually membership after you received it's BLOCK{A} since your implementation could tell whether or not it's previous mode was INC{A}. Wilbert > but in the 2) case the router can confuse between a host that want to > block{A} and a host just want to leave the group .In my implementation of > IGMPv3 router side, i want to know if a particular member had leave a group, > so i think to use a timer by member and the router state will be: > (group, fmode, sources, members) > and a member will have this state: > (adress, timer). > the member timer will be update when the router receive a report from this > host, if the member timer expires then the router will know that this host > had leave the group. > Lahmadi From owner-idmr@cs.ucl.ac.uk Tue Jun 19 12:26:18 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25911 for ; Tue, 19 Jun 2001 12:26:18 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Tue, 19 Jun 2001 16:30:55 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Tue, 19 Jun 2001 16:30:48 +0100 Received: from cvis22.marconicomms.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 19 Jun 2001 16:30:46 +0100 Received: from cvis01.gpt.co.uk (unverified) by cvis22.marconicomms.com (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Tue, 19 Jun 2001 16:30:39 +0100 Received: from marconicomms.com by cvis01.gpt.co.uk with SMTP (8.8.8+Sun/cvms-32) id QAA14677; Tue, 19 Jun 2001 16:30:44 +0100 (BST) Received: by marconicomms.com(Lotus SMTP MTA v4.6.7 (934.1 12-30-1999)) id 80256A70.0055195B ; Tue, 19 Jun 2001 16:29:30 +0100 X-Lotus-FromDomain: MCMAIN@MCEXT From: Fabio Poggi To: idmr@cs.ucl.ac.uk Message-ID: <80256A70.00550D83.00@marconicomms.com> Date: Tue, 19 Jun 2001 16:58:57 +0200 Subject: Question about IGMP MIB Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Hi all, I'm reading RFC 2933. I was not taking part in discussion about this RFC and probably you have already discussed it in deep. Could you help me with some clarifications ? igmpInterfaceQueryInterval This object has no range of values. So, it's possible to set this object to any value allowed by its syntax (unsigned32), but a value of 2^32 [sec] is operationally impossible, isn't it ? It shouldn't better to provide a feasible range of values ? (e.g. (0 .. 1024)) The same for igmpInterfaceLastMembQueryIntvl igmpCacheLastReporter When is this object used ? Is this object used in a router that is also member of the same group address on the same interface ? igmpCacheStatus Why this object has a read/create access ? I've understand that this table is created dinamically by the IGMP querier/host. Is it possible to add an entry in the igmpCacheTable from management ? Thanks Fabio From owner-idmr@cs.ucl.ac.uk Tue Jun 19 12:27:09 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA25973 for ; Tue, 19 Jun 2001 12:27:08 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Tue, 19 Jun 2001 16:16:06 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Tue, 19 Jun 2001 16:15:59 +0100 Received: from emerson.torrentnet.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 19 Jun 2001 16:15:57 +0100 Received: from imperial.torrentnet.com (imperial.torrentnet.com [198.78.51.109]) by emerson.torrentnet.com (8.11.2/8.11.2) with ESMTP id f5JFFua49961 for ; Tue, 19 Jun 2001 11:15:56 -0400 (EDT) Received: from bacardi.torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by imperial.torrentnet.com (8.11.2/8.11.2) with ESMTP id f5JFFuK94156 for ; Tue, 19 Jun 2001 11:15:56 -0400 (EDT) Received: from bacardi.torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by bacardi.torrentnet.com (8.10.2/8.10.2) with SMTP id f5JFFqv15540 for ; Tue, 19 Jun 2001 11:15:52 -0400 (EDT) Date: Tue, 19 Jun 2001 11:15:52 -0400 (EDT) From: Todd Hayton To: idmr@cs.ucl.ac.uk Subject: MIB implementation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Hello, I've recently been tasked with implementing the multicast routing MIB (rfc 2932) and have a question about the indexes used in one of the tables. Specifically, I'm confused about the ipMRouteNextHopAddress index of the ipMRouteNextHopTable. The name ipMRouteNextHopAddress seems to imply that the index is actually the IP address of the next receiver on the outgoing interface. However, the rfc makes the following comment on this index: "The address of the next-hop specific to this entry. For most interfaces, this is identical to ipMRouteNextHopGroup. NBMA interfaces, however, may have multiple next-hop addresses out a single outgoing interface." So, I guess I'm unclear about how this is a useful index, as ipMRouteNextHopGroup already specifies the group being sent to. The distinction seems to be for NBMA interfaces, but that part of the description I'm honestly a bit lost on. If anybody has any clarifications, I'd really appreciate it. Regards, Todd H From owner-idmr@cs.ucl.ac.uk Wed Jun 20 13:47:56 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15755 for ; Wed, 20 Jun 2001 13:47:55 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 20 Jun 2001 17:47:05 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 20 Jun 2001 17:47:00 +0100 Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 20 Jun 2001 17:47:00 +0100 Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id E83941EF46; Wed, 20 Jun 2001 12:46:57 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA07306; Wed, 20 Jun 2001 12:46:56 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA04011; Wed, 20 Jun 2001 09:46:56 -0700 (PDT) Message-Id: <200106201646.JAA04011@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: thayton@torrentnet.com Subject: Re: MIB implementation Cc: idmr@cs.ucl.ac.uk Date: Wed, 20 Jun 2001 09:46:52 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk >The distinction seems to be for NBMA interfaces It is. For interfaces that have a layer 2 multicast or broadcast, the ipMRouteNextHopAddress is simply the same as ipMRouteNextHopGroup. However, if you have an interface that does not have a layer 2 multicast or broadcast, and yet you have multiple neighbors, you have to replicate the packet on that network once to each interested neighbor. (Maybe all of the multicast-capable systems on the link, maybe some subset). In this situation, ipMRouteNextHopAddress is used to list the relevant neighbors. Bill From owner-idmr@cs.ucl.ac.uk Wed Jun 20 13:52:04 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15950 for ; Wed, 20 Jun 2001 13:52:03 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 20 Jun 2001 17:56:07 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 20 Jun 2001 17:56:01 +0100 Received: from H-135-207-30-103.research.att.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 20 Jun 2001 17:56:00 +0100 Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id BF8871E038; Wed, 20 Jun 2001 12:55:52 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA07599; Wed, 20 Jun 2001 12:55:52 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA04137; Wed, 20 Jun 2001 09:55:51 -0700 (PDT) Message-Id: <200106201655.JAA04137@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: fabio.poggi@marconi.com Subject: Re: Question about IGMP MIB Cc: idmr@cs.ucl.ac.uk Date: Wed, 20 Jun 2001 09:55:50 -0700 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk >igmpInterfaceQueryInterval > This object has no range of values. > So, it's possible to set this object to any value allowed by its syntax >(unsigned32), but a value of 2^32 [sec] is operationally impossible, isn't >it ? > It shouldn't better to provide a feasible range of values ? (e.g. (0 .. >1024)) But that's an operational decision. I don't think we could necessarily agree on a range that will satisfy everyone's requirements. >igmpCacheLastReporter > When is this object used ? Mostly debugging; it allows for a small insight into what systems are reporting membership. >igmpCacheStatus > Why this object has a read/create access ? > I've understand that this table is created dinamically by the IGMP >querier/host. > Is it possible to add an entry in the igmpCacheTable from management ? Yes, it is possible to cause a system to join a group (e.g. create a row with igmpCacheSelf = true). Bill From owner-idmr@cs.ucl.ac.uk Thu Jun 21 12:57:39 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA06799 for ; Thu, 21 Jun 2001 12:57:38 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Thu, 21 Jun 2001 16:46:39 +0100 Received: from haig.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Thu, 21 Jun 2001 16:44:06 +0100 Received: from odin.ietf.org by haig.cs.ucl.ac.uk with Internet SMTP id ; Thu, 21 Jun 2001 16:43:49 +0100 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18115; Mon, 18 Jun 2001 15:30:05 -0400 (EDT) Message-Id: <200106181930.PAA18115@ietf.org> To: IETF-Announce:; Cc: idmr@cs.ucl.ac.uk From: The IESG SUBJECT: Last Call: IGMP Multicast Router Discovery to Proposed Standard Reply-to: iesg@ietf.org Date: Mon, 18 Jun 2001 15:30:05 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk The IESG has received a request from the Inter-Domain Multicast Routing Working Group to consider IGMP Multicast Router Discovery as a Proposed Standard. The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by July 2, 2001. Files can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mrdisc-06.txt From owner-idmr@cs.ucl.ac.uk Thu Jun 21 20:53:17 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22420 for ; Thu, 21 Jun 2001 20:53:17 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 22 Jun 2001 01:45:05 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 22 Jun 2001 01:40:28 +0100 Received: from mail5.microsoft.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 22 Jun 2001 01:40:27 +0100 Received: from 157.54.9.100 by mail5.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 21 Jun 2001 16:51:52 -0700 (Pacific Daylight Time) Received: from red-imc-02.redmond.corp.microsoft.com ([157.54.9.107]) by inet-imc-03.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2883); Thu, 21 Jun 2001 16:51:06 -0700 Received: from win-imc-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.39]) by red-imc-02.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.2883); Thu, 21 Jun 2001 16:51:05 -0700 Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-imc-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 21 Jun 2001 16:49:32 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: IANA-RTPROTO-MIB reference in RFC 2932 Date: Thu, 21 Jun 2001 16:49:31 -0700 Message-ID: <2E33960095B58E40A4D3345AB9F65EC101671DCC@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> Thread-Topic: IANA-RTPROTO-MIB reference in RFC 2932 Thread-Index: AcD6rCzaT0X1KN0GQJ2RA8tG9BSoGwAAIzmg From: Dave Thaler To: Mike , idmr X-OriginalArrivalTime: 21 Jun 2001 23:49:32.0289 (UTC) FILETIME=[D185A710:01C0FAAC] Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id UAA22420 ftp://ftp.iana.org/mib/ianaiprouteprotocol.mib > -----Original Message----- > From: Mike [mailto:mdavison@juniper.net] > Sent: Thursday, June 21, 2001 4:48 PM > To: idmr@cs.ucl.ac.uk; Dave Thaler > Subject: IANA-RTPROTO-MIB reference in RFC 2932 > > > RFC 2932, 'IPv4 Multicast Routing MIB,' references IANA-RTPROTO-MIB, but > fails to provide the RFC number or draft name. After some searching, I > have > not located this MIB document as either an RFC or a draft. Can anyone > provide > a pointer to this document? > > Thanks, > Mike From owner-idmr@cs.ucl.ac.uk Thu Jun 21 20:53:33 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA22431 for ; Thu, 21 Jun 2001 20:53:33 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 22 Jun 2001 00:59:19 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 22 Jun 2001 00:46:08 +0100 Received: from red.juniper.net by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 22 Jun 2001 00:46:09 +0100 Received: from lytle (ssh.juniper.net [207.17.136.39]) by red.juniper.net (8.9.3/8.9.3) with SMTP id QAA20002; Thu, 21 Jun 2001 16:46:05 -0700 (PDT) Content-Type: text/plain; charset="iso-8859-1" From: Mike To: idmr@cs.ucl.ac.uk, dthaler@microsoft.com Subject: IANA-RTPROTO-MIB reference in RFC 2932 Date: Thu, 21 Jun 2001 16:47:34 -0700 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <0106211647340G.22981@lytle> Content-Transfer-Encoding: 8bit Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 8bit RFC 2932, 'IPv4 Multicast Routing MIB,' references IANA-RTPROTO-MIB, but fails to provide the RFC number or draft name. After some searching, I have not located this MIB document as either an RFC or a draft. Can anyone provide a pointer to this document? Thanks, Mike From owner-idmr@cs.ucl.ac.uk Fri Jun 22 11:36:00 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA26562 for ; Fri, 22 Jun 2001 11:35:59 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 22 Jun 2001 15:47:11 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 22 Jun 2001 15:47:05 +0100 Received: from alpo.casc.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 22 Jun 2001 15:47:06 +0100 Received: from msablic ([62.172.151.6]) by alpo.casc.com (8.9.1a/8.9.1) with SMTP id KAA19088 for ; Fri, 22 Jun 2001 10:47:00 -0400 (EDT) Message-ID: <005a01c0fb2a$315005a0$0697ac3e@ukip> From: Mladen Sablic To: idmr Subject: Differences in query retransmission scheduling between IGMP v2 & v3 Date: Fri, 22 Jun 2001 15:46:58 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit Hi all, I was looking at "6.6.3 Building and Sending Specific Queries" in draft-ietf-idmr-igmp-v3-07.txt and I see that the scheduling of queries and lowering of expiry time has changed with respect to [Last Member Query Interval] or LMQI. In IGMPv2 RFC 2236 section 6: - Group timer is lowered to LMQI*[Last Member Query Count]. - Queries were retransmitted separated by LMQI with Max Response Time of LMQI. This implies that if reports from all but the last query were lost then the last report would still arrive before group timer expires. The logic behind 6.6.3 is that the Max Resp Time in queries must be set to some value other than LMQI even tough this is nowhere explicitly mentioned. If the Max Resp Code is set with Max Resp Time = LMQI the response from retransmitted queries could possibly not arrive before group or source timer expires. Does this mean that Max Resp Time should be set to: LMQI/[Last Member Query Count]? Is this correct or am I missing something? Thanks, Mladen From owner-idmr@cs.ucl.ac.uk Tue Jun 26 11:08:22 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA18538 for ; Tue, 26 Jun 2001 11:08:21 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Tue, 26 Jun 2001 14:57:42 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Tue, 26 Jun 2001 14:57:35 +0100 Received: from juicer02.bigpond.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 26 Jun 2001 14:57:21 +0100 Received: from derek ([139.134.4.53]) by mailin5.bigpond.com (Netscape Messaging Server 4.15) with SMTP id GFJJ0X00.1GX for ; Wed, 27 Jun 2001 00:02:57 +1000 Received: from CPE-144-132-131-53.nsw.bigpond.net.au ([144.132.131.53]) by mail0.bigpond.com (Claudes-Statistical-MailRouter V2.9c 13/7271701); 26 Jun 2001 23:57:03 Message-ID: <004401c0fe37$ea7de730$0901010a@derek> From: Ronnie Sahlberg To: idmr Subject: [OT]MRDISC protocol dissector Date: Tue, 26 Jun 2001 22:02:47 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Content-Transfer-Encoding: 7bit Hi list, I have implemented MRDISC protocol dissection to the free GPL analyzer ethereal (www.ethereal.com) and would like to find any example capture files or implementations to verify the implementation in the tool. If anyone could provide me with pointers to where I can find an implementation or tcpdump capture files for this protocol (or DVMRP) I would be grateful. Thanks Best regards ronnie sahlberg From owner-idmr@cs.ucl.ac.uk Tue Jun 26 14:58:45 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA03281 for ; Tue, 26 Jun 2001 14:58:44 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Tue, 26 Jun 2001 18:39:56 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Tue, 26 Jun 2001 18:35:45 +0100 Received: from usc.edu by bells.cs.ucl.ac.uk with Internet SMTP id ; Tue, 26 Jun 2001 18:35:45 +0100 Received: from ceng.usc.edu (helmy@ceng.usc.edu [128.125.72.78]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id KAA14505; Tue, 26 Jun 2001 10:35:42 -0700 (PDT) Received: from localhost (helmy@localhost) by ceng.usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id KAA13577; Tue, 26 Jun 2001 10:35:41 -0700 (PDT) Date: Tue, 26 Jun 2001 10:35:41 -0700 (PDT) From: helmy To: Ronnie Sahlberg cc: idmr Subject: Re: [OT]MRDISC protocol dissector In-Reply-To: <004401c0fe37$ea7de730$0901010a@derek> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Hi Ronnie, Our research group at USC is developing a framework for systematic testing of multicast protocols (called Stress). We have used it to analyze/test PIM-SM, and PIM-DM. It mainly takes a finite state machine (FSM) description of the protocol, and correctness criteria. Then performs forward/backward search, to output a set of test scenarios that lead to protocol errors. So far, we have mainly used Stress for 'design' and protocol/spec testing, not implementation testing. The case studies and papers published are available at catarina.usc.edu/stress or through my web site below (more up-to-date), hope this helps, Regards, Ahmed Helmy Assistant Professor of Computer Networks Electrical Engineering-Systems Department University of Southern California http://ceng.usc.edu/~helmy On Tue, 26 Jun 2001, Ronnie Sahlberg wrote: > Hi list, > > I have implemented MRDISC protocol dissection to the free GPL analyzer > ethereal (www.ethereal.com) > and would like to find any example capture files or implementations to > verify the implementation in the tool. > > If anyone could provide me with pointers to where I can find an > implementation or tcpdump capture files for > this protocol (or DVMRP) I would be grateful. > > Thanks > Best regards > ronnie sahlberg > > From owner-idmr@cs.ucl.ac.uk Wed Jun 27 19:36:28 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA13114 for ; Wed, 27 Jun 2001 19:36:27 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Wed, 27 Jun 2001 23:54:41 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Wed, 27 Jun 2001 23:54:35 +0100 Received: from stephens.ittc.ku.edu by bells.cs.ucl.ac.uk with Internet SMTP id ; Wed, 27 Jun 2001 23:54:21 +0100 Received: from george.ittc.ku.edu (george.ittc.ku.edu [129.237.126.117]) by stephens.ittc.ku.edu (8.11.2/8.11.2/ITTC-NOSPAM-NOVIRUS-2.2) with ESMTP id f5RMsK732658 for ; Wed, 27 Jun 2001 17:54:20 -0500 Received: from localhost by george.ittc.ku.edu (8.9.3/KU-4.0-client) id RAA03820; Wed, 27 Jun 2001 17:54:24 -0500 Date: Wed, 27 Jun 2001 17:54:24 -0500 (CDT) From: Magesh Kannan To: idmr@cs.ucl.ac.uk Subject: DVMRP Prune question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk Hi All, I have a question regarding the transmission of DVMRP prune messages. I refer to the Internet draft 'draft-ietf-idmr-dvmrp-v3-10.txt' Is it correct to say that prune messages are sent only in response to the following two events? (Pl. ignore prune retransmissions) 1. Arrival of a multicast datagram (for which there are no interested listeners). 2. Arrival of a prune message from a dependent downstream router. This question is meant to clarify this scenario: Some hosts in a network have subscribed to a multicast group to which no source is sending traffic. After some time, all these hosts leave this group (and still no source is sending traffic to this group). When the last member leaves this group, will the DVMRP router for this network send a prune message upstream? Thanks, Magesh From owner-idmr@cs.ucl.ac.uk Wed Jun 27 21:04:22 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA14214 for ; Wed, 27 Jun 2001 21:04:22 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Thu, 28 Jun 2001 01:04:13 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Thu, 28 Jun 2001 00:33:35 +0100 Received: from red.juniper.net by bells.cs.ucl.ac.uk with Internet SMTP id ; Thu, 28 Jun 2001 00:33:35 +0100 Received: from juniper.net (garnet.juniper.net [172.17.28.17]) by red.juniper.net (8.9.3/8.9.3) with ESMTP id QAA07997; Wed, 27 Jun 2001 16:33:27 -0700 (PDT) Message-Id: <200106272333.QAA07997@red.juniper.net> To: Magesh Kannan cc: idmr@cs.ucl.ac.uk, pusateri@juniper.net Subject: Re: DVMRP Prune question In-Reply-To: Message from Magesh Kannan of "Wed, 27 Jun 2001 17:54:24 CDT." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <51288.993684806.1@juniper.net> Date: Wed, 27 Jun 2001 16:33:26 -0700 From: Tom Pusateri Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk No, there are more conditions that cause prune messages to be generated. For instance, all of your downstream dependent neighbors could either timeout or their routing information could change which would cause them to stop being dependents. I'm sure there other scenarios as well. Tom In message you wri te: >Hi All, > >I have a question regarding the transmission of DVMRP prune messages. I >refer to the Internet draft 'draft-ietf-idmr-dvmrp-v3-10.txt' > >Is it correct to say that prune messages are sent only in response to the >following two events? (Pl. ignore prune retransmissions) >1. Arrival of a multicast datagram (for which there are no interested >listeners). >2. Arrival of a prune message from a dependent downstream router. > >This question is meant to clarify this scenario: Some hosts in a network >have subscribed to a multicast group to which no source is sending >traffic. After some time, all these hosts leave this group (and still no >source is sending traffic to this group). When the last member leaves this >group, will the DVMRP router for this network send a prune message >upstream? > >Thanks, >Magesh > From owner-idmr@cs.ucl.ac.uk Wed Jun 27 21:06:33 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA15697 for ; Wed, 27 Jun 2001 21:06:32 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Thu, 28 Jun 2001 01:32:15 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Thu, 28 Jun 2001 01:32:09 +0100 Received: from presque.djinesys.com by bells.cs.ucl.ac.uk with Internet SMTP id ; Thu, 28 Jun 2001 01:32:09 +0100 Received: from nexthop.com ([141.211.130.160]) by presque.djinesys.com (8.11.1/8.11.1) with ESMTP id f5S0W4Z44374; Wed, 27 Jun 2001 20:32:04 -0400 (EDT) (envelope-from ctbrown@nexthop.com) Message-Id: <200106280032.f5S0W4Z44374@presque.djinesys.com> From: Christopher Thomas Brown Subject: Re: DVMRP Prune question To: Magesh Kannan , idmr@cs.ucl.ac.uk In-Reply-To: Your message of "Wed, 27 Jun 2001 17:54:24 CDT." Date: Wed, 27 Jun 2001 20:32:03 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk On Wed, 27 Jun 2001 17:54:24 CDT Magesh Kannan wrote: >Hi All, > >I have a question regarding the transmission of DVMRP prune messages. I >refer to the Internet draft 'draft-ietf-idmr-dvmrp-v3-10.txt' > >Is it correct to say that prune messages are sent only in response to the >following two events? (Pl. ignore prune retransmissions) >1. Arrival of a multicast datagram (for which there are no interested >listeners). >2. Arrival of a prune message from a dependent downstream router. Not quite correct. 2 should be: If the forwarding cache entry to transitions to a NULL outgoing interface list. This implies recent s,g data flow or else you would not have a forwarding cache entry. >This question is meant to clarify this scenario: Some hosts in a network >have subscribed to a multicast group to which no source is sending >traffic. After some time, all these hosts leave this group (and still no >source is sending traffic to this group). When the last member leaves this >group, will the DVMRP router for this network send a prune message >upstream? If data has never flowed then you do not have a forwarding cache entry for s,g. So, you do not send a prune. Chris Brown NextHop Technologies From owner-idmr@cs.ucl.ac.uk Fri Jun 29 12:41:32 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA18284 for ; Fri, 29 Jun 2001 12:41:31 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 29 Jun 2001 16:45:36 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 29 Jun 2001 16:41:20 +0100 Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 29 Jun 2001 16:41:00 +0100 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11290; Thu, 28 Jun 2001 07:15:57 -0400 (EDT) Message-Id: <200106281115.HAA11290@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: idmr@cs.ucl.ac.uk From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-idmr-igmp-mrdisc-07.txt Date: Thu, 28 Jun 2001 07:15:57 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Multicast Routing Working Group of the IETF. Title : IGMP Multicast Router Discovery Author(s) : S. Biswas, B. Cain, B. Haberman Filename : draft-ietf-idmr-igmp-mrdisc-07.txt Pages : 15 Date : 27-Jun-01 The concept of IGMP snooping requires the ability to identify the location of multicast routers. Since IGMP snooping is not standardized, there are many mechanisms in use to identify the multicast routers. However, this scenario can lead to interoperability issues between multicast routers and layer-2 switches from different vendors. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idmr-igmp-mrdisc-07.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idmr-igmp-mrdisc-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idmr-igmp-mrdisc-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010627143540.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idmr-igmp-mrdisc-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idmr-igmp-mrdisc-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010627143540.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-idmr@cs.ucl.ac.uk Fri Jun 29 12:41:50 2001 Received: from pan2.cs.ucl.ac.uk (pan2.cs.ucl.ac.uk [128.16.8.208]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA18304 for ; Fri, 29 Jun 2001 12:41:49 -0400 (EDT) Received: from pan2.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk via Local Delivery channel id ; Fri, 29 Jun 2001 16:45:11 +0100 Received: from bells.cs.ucl.ac.uk by pan2.cs.ucl.ac.uk with local SMTP id ; Fri, 29 Jun 2001 16:41:02 +0100 Received: from odin.ietf.org by bells.cs.ucl.ac.uk with Internet SMTP id ; Fri, 29 Jun 2001 16:40:58 +0100 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10958; Thu, 28 Jun 2001 07:14:51 -0400 (EDT) Message-Id: <200106281114.HAA10958@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce:; Cc: idmr@cs.ucl.ac.uk From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-idmr-snoop-01.txt Date: Thu, 28 Jun 2001 07:14:51 -0400 Sender: owner-idmr@cs.ucl.ac.uk Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Inter-Domain Multicast Routing Working Group of the IETF. Title : IGMPv3 and IGMP Snooping switches Author(s) : M. Christensen, F. Solensky Filename : draft-ietf-idmr-snoop-01.txt Pages : 16 Date : 27-Jun-01 This memo describes the interoperability problems and issues that can arise when a mixed deployment of IGMPv3 and IGMPv2 capable hosts and routers are interconnected by a switch with IGMP snooping capabilities. The memo also covers MLDv2 for IPv6. It is intended as an accompanying document to the IGMPv3 and MLDv2 specifications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-idmr-snoop-01.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-idmr-snoop-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-idmr-snoop-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20010627132518.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-idmr-snoop-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-idmr-snoop-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20010627132518.I-D@ietf.org> --OtherAccess-- --NextPart--