From owner-bgmp@catarina.usc.edu Mon Jun 5 14:25:05 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08051 for ; Mon, 5 Jun 2000 14:25:05 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id LAA11237 for bgmp-list; Mon, 5 Jun 2000 11:08:32 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-bgmp@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id LAA11232 for ; Mon, 5 Jun 2000 11:08:27 -0700 (PDT) Received: from p-biset.issy.cnet.fr (p-biset.issy.cnet.fr [139.100.0.33]) by usc.edu (8.9.3.1/8.9.3/usc) with SMTP id LAA17003 for ; Mon, 5 Jun 2000 11:08:24 -0700 (PDT) Received: by p-biset.issy.cnet.fr with Internet Mail Service (5.5.2448.0) id ; Mon, 5 Jun 2000 20:06:33 +0200 Message-ID: <98388C05D464D111B61800805F150416010B03B7@p-ibis.issy.cnet.fr> From: BOURDON Gilles FTRD/DAC/ISS To: "'bgmp@catarina.usc.edu'" Subject: Prune messages Date: Mon, 5 Jun 2000 20:06:32 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-bgmp@catarina.usc.edu Precedence: bulk Hi, Section 5.3.2, the draft says : "Otherwise, the component or peer is removed from the target list. If the target list becomes null as a result, the next-hop peer towards G (for a (*,G) entry), or towards S (for an (S,G) entry if and only if the BGMP router does NOT have any corresponding (*,G) entry), must be notified as follows. ..." Something looks weird to me : there should be at least 2 entries in a target list, right ? Then if the component or peer from which the prune has been received is removed from the target list, it still remains one target (from which we can receive data) and it's useless. And the target list is not null, so no notification towards S or G... Am I wrong somewhere ? Gilles Bourdon. From owner-bgmp@catarina.usc.edu Thu Jun 8 13:59:34 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13096 for ; Thu, 8 Jun 2000 13:59:34 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id JAA31712 for bgmp-list; Thu, 8 Jun 2000 09:47:41 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-bgmp@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id JAA31707 for ; Thu, 8 Jun 2000 09:47:41 -0700 (PDT) From: zainprov@swbell.net Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id JAA02546 for ; Thu, 8 Jun 2000 09:47:40 -0700 (PDT) Received: from zainprov ([207.193.24.81]) by mta5.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0FVU00D84F8Y39@mta5.rcsntx.swbell.net> for bgmp@catarina.usc.edu; Thu, 8 Jun 2000 11:05:45 -0500 (CDT) Date: Thu, 08 Jun 2000 11:05:45 -0500 (CDT) Date-warning: Date header was inserted by mta5.rcsntx.swbell.net Subject: Shocking LOSE 10-100lbs. DESTINY To: bgmp@catarina.usc.edu Message-id: <0FVU00DSGFDJ39@mta5.rcsntx.swbell.net> MIME-version: 1.0 Content-type: text/plain; charset=unknown-8bit Sender: owner-bgmp@catarina.usc.edu Precedence: bulk Hello From Destiny, You will LOOSE 20-100 pounds easy! Do to Such a high demand for Destiny, we are able To Dramatically reduce our price for the entire System! You will LOVE our incredible offer on this Scientific Breakthrough in Weight Loss. Now with a 105% Money Back Guarantee! LOOK! http://home.swbell.net/zainprov/destiny.htm We hope things are going well for you. Good luck, God Bless, and HAVE A GREAT DAY! Either you are someone else subscribed to our list. To be removed Simply reply with a blank email. Thank you, Sherry Wilson From owner-bgmp@catarina.usc.edu Mon Jun 12 12:41:41 2000 Received: from catarina.usc.edu (catarina.usc.edu [128.125.51.47]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06339 for ; Mon, 12 Jun 2000 12:41:40 -0400 (EDT) Received: (from majordom@localhost) by catarina.usc.edu (8.9.3/8.9.3) id JAA56064 for bgmp-list; Mon, 12 Jun 2000 09:29:12 -0700 (PDT) X-Authentication-Warning: catarina.usc.edu: majordom set sender to owner-bgmp@catarina.usc.edu using -f Received: from usc.edu (root@usc.edu [128.125.253.136]) by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id JAA56033; Mon, 12 Jun 2000 09:28:04 -0700 (PDT) Received: from dthaler.microsoft.com ([131.107.152.20]) by usc.edu (8.9.3.1/8.9.3/usc) with ESMTP id JAA21810; Mon, 12 Jun 2000 09:28:04 -0700 (PDT) Received: (from dthaler@localhost) by dthaler.microsoft.com (8.8.7/8.8.7) id KAA26781; Mon, 12 Jun 2000 10:57:58 -0700 (PDT) (envelope-from dthaler) From: Dave Thaler Message-Id: <200006121757.KAA26781@dthaler.microsoft.com> Subject: Re: A modest proposal: get rid of (*,*,RP) state In-Reply-To: <200006121104.EAA96606@rumi.usc.edu> from Pavlin Ivanov Radoslavov at "Jun 12, 2000 4: 4:57 am" To: pavlin@catarina.usc.edu (Pavlin Ivanov Radoslavov) Date: Mon, 12 Jun 2000 10:57:57 -0700 (PDT) Cc: fenner@research.att.com, pim@catarina.usc.edu, bgmp@catarina.usc.edu X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bgmp@catarina.usc.edu Precedence: bulk Content-Transfer-Encoding: 7bit Pavlin asks: > I am probably missing something in the picture, but why do we need > (*,*,RP) if the RP is not a border router? > To "push" the data from the internal sources over the BGMP trees to > the dense-mode domains? (again, Domain-Wide Reports running in the > dense-mode domains will eliminate the need for this). > > A more detailed example here would be helpful :) Technically one would only need a bunch of (*,Gprefix,RP) joins per RP but those aren't specified, so a single (*,*,RP) per RP works :) The exit router for Gprefix (i.e. the one towards the root domain for Gprefix) needs to receive all data from the subtree under it for all groups G in Gprefix. If it's the RP for all such groups, there's no problem, all packets travelling uptree automatically get sent to it. If it's not the RP, it needs a way to join to all RPs that serve groups in Gprefix. (And any other Gprefix'es for which it is the best exit router.) DWRs don't help here, since this is a border router needing to set up a path to an internal RP. So to repeat, solutions I'm aware of are: 1) Don't run PIM-SM... run BGMP as the M-IGP (as Dino hinted, I think) 2) Run PIM-SM with RPs=BRs. 3) Run PIM-SM with MSDP for internal peerings only, between RPs & BRs. 4) Run PIM-SM with (*,*,RP) joins from exit BRs to RPs. -Dave