[pim] RE: pim Digest, Vol 18, Issue 3

"Srikanth Rao" <srikanth@force10networks.com> Fri, 07 October 2005 17:25 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENvy0-000442-VB; Fri, 07 Oct 2005 13:25:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENvy0-00042k-2s for pim@megatron.ietf.org; Fri, 07 Oct 2005 13:25:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01372 for <pim@ietf.org>; Fri, 7 Oct 2005 13:25:04 -0400 (EDT)
Received: from corp.force10networks.com ([206.54.51.125] helo=mx.force10networks.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENw7J-0008J5-FQ for pim@ietf.org; Fri, 07 Oct 2005 13:34:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 07 Oct 2005 10:23:04 -0700
Message-ID: <B53A8EFF919E0A4BA9EC42775D99C470133E40@EXCH-CLUSTER-01.force10networks.com>
Thread-Topic: pim Digest, Vol 18, Issue 3
Thread-Index: AcXLWXLSvY7TmNSXSUqKilE9G0+jVgACVdfw
From: Srikanth Rao <srikanth@force10networks.com>
To: pim@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Subject: [pim] RE: pim Digest, Vol 18, Issue 3
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
Sender: pim-bounces@ietf.org
Errors-To: pim-bounces@ietf.org

James,

One way is to check the incoming interface. If the packet arrived on RPF 
interface towards RP, then it is forwarded to the receivers. If the packet 
arrived on an interface on which the router is the DF for the RP (mapping 
to the mutlicast group), then it is forwarded towards RP.

-srikanth

-----Original Message-----
From: pim-request@ietf.org [mailto:pim-request@ietf.org]
Sent: Friday, October 07, 2005 9:11 AM
To: pim@ietf.org
Subject: pim Digest, Vol 18, Issue 3


Send pim mailing list submissions to
	pim@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/pim
or, via email, send a message with subject or body 'help' to
	pim-request@ietf.org

You can reach the person managing the list at
	pim-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of pim digest..."


Today's Topics:

   1. pim-bidir (James Courtier-Dutton)


----------------------------------------------------------------------

Message: 1
Date: Fri, 7 Oct 2005 15:06:51 +0100
From: James Courtier-Dutton <james.dutton@gmail.com>
Subject: [pim] pim-bidir
To: pim@ietf.org
Message-ID: <ad2655cb0510070706n18974d0u@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I am trying to understand draft-ietf-pim-bidir-07.txt.

>From what I currently understand, there is a shared tree for passing
packets from the source to the RP, and another shared tree for passing
packets from the RP to the receiver.

When a router receives a packet, how does the router know if it is a
packet destined for the RP or destined for the Receiver?

James



------------------------------

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


End of pim Digest, Vol 18, Issue 3
**********************************

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