From owner-bgmp@catarina.usc.edu  Thu Apr 27 12:11: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 MAA03068
	for <bgmp-archive@odin.ietf.org>; Thu, 27 Apr 2000 12:11:33 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id IAA04593
	for bgmp-list; Thu, 27 Apr 2000 08:48:00 -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] (may be forged))
	by catarina.usc.edu (8.9.3/8.9.3) with ESMTP id IAA04588
	for <bgmp@catarina.usc.edu>; Thu, 27 Apr 2000 08:47:59 -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 IAA26035 for <bgmp@catarina.usc.edu>; Thu, 27 Apr 2000 08:45:46 -0700 (PDT)
Received: by p-biset.issy.cnet.fr with Internet Mail Service (5.5.2448.0)
	id <2K2J38DR>; Thu, 27 Apr 2000 17:43:40 +0200
Message-ID: <98388C05D464D111B61800805F150416010B0374@p-ibis.issy.cnet.fr>
From: BOURDON Gilles FTRD/DAC/ISS <gilles.bourdon@rd.francetelecom.fr>
To: "'bgmp@catarina.usc.edu'" <bgmp@catarina.usc.edu>
Date: Thu, 27 Apr 2000 17:43:38 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by catarina.usc.edu id IAA04589
Sender: owner-bgmp@catarina.usc.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,

Could anyone explain what exactly Poison-Reverse message solves ? Maybe a
quick word on it in the draft would be useful.

I am also wondering how the (S,G) target list is populated in the case you
have a Join(S,G) coming from an external peer (and (S,G) entry is then
created), but you already have a (*,G) entry. Is target list copied from
(*,G) to (S,G), and (*,G) Joins update (S,G) target list ?

Thank you.

Gilles.

> ________________________________________________
> Gilles Bourdon
> Research and Development Engineer
> IP Routing, Routers and VPN lab
> 
> France Télécom R&D
> 38-40 rue du Général-Leclerc  
> 92794 Issy Moulineaux Cedex 9  France
> phone : (+33).1.45.29.46.45     fax : (+33).1.45.29.54.11
> ________________________________________________
> 


From owner-bgmp@catarina.usc.edu  Thu Apr 27 14:50:37 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 OAA05310
	for <bgmp-archive@odin.ietf.org>; Thu, 27 Apr 2000 14:50:37 -0400 (EDT)
Received: (from majordom@localhost)
	by catarina.usc.edu (8.9.3/8.9.3) id LAA05396
	for bgmp-list; Thu, 27 Apr 2000 11:31:55 -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 LAA05391
	for <bgmp@catarina.usc.edu>; Thu, 27 Apr 2000 11:31:54 -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 LAA18591 for <bgmp@catarina.usc.edu>; Thu, 27 Apr 2000 11:31:53 -0700 (PDT)
Received: (from dthaler@localhost)
	by dthaler.microsoft.com (8.8.7/8.8.7) id NAA00562;
	Thu, 27 Apr 2000 13:02:04 -0700 (PDT)
	(envelope-from dthaler)
From: Dave Thaler <dthaler@dthaler.microsoft.com>
Message-Id: <200004272002.NAA00562@dthaler.microsoft.com>
Subject: Re: your mail
In-Reply-To: <98388C05D464D111B61800805F150416010B0374@p-ibis.issy.cnet.fr> from BOURDON Gilles FTRD/DAC/ISS at "Apr 27, 2000  5:43:38 pm"
To: gilles.bourdon@rd.francetelecom.fr (BOURDON Gilles FTRD/DAC/ISS)
Date: Thu, 27 Apr 2000 13:02:04 -0700 (PDT)
Cc: 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

Gilles Bourdon writes:
> Could anyone explain what exactly Poison-Reverse message solves ? Maybe a
> quick word on it in the draft would be useful.

I think it's been explained on the list... Isidor Kouvelas originally
brought up the problem 2 IETF meetings ago.

In short, it solves the problem of knowing whether to forward
packets towards the root or not when you're receiving data on
an (S,G) branch.

> I am also wondering how the (S,G) target list is populated in the case you
> have a Join(S,G) coming from an external peer (and (S,G) entry is then
> created), but you already have a (*,G) entry. Is target list copied from
> (*,G) to (S,G), and (*,G) Joins update (S,G) target list ?

Right.

-Dave


