From: Jack Heney (jheneyccie@xxxxxxxxxxx)
Date: Tue Oct 24 2000 - 22:11:38 GMT-3
The RP isn't really like a designated router because there isn't one per
data link....The RP is where multicast messages and requests to join groups
are sent....It is where the senders and receivers "rendezvous" (the
multicast traffic is sent to the RP, the RP knows where the receivers
are)...Once the sender and receiver have established a data flow through the
RP, the receiver can look at the source address and determine if there is a
shorter path between the two than the path through the RP. If a shorter
path exists, the multicast traffic can be sent along the shorter path,
bypassing the RP (for this articular sender/receiver).
hth,
Jack
>From: "Eddie Parra" <eparra@cisco.com>
>Reply-To: "Eddie Parra" <eparra@cisco.com>
>To: "CCIE Group Study" <ccielab@groupstudy.com>
>Subject: Multicasting Question - RP question.
>Date: Tue, 24 Oct 2000 20:11:37 -0400
>
>My understanding of a RP is sort of like a OSPF "DR". What I can't figure
>out is how this applies to a multicast network. If my client PC sense a
>IGMP join to a multicast server I am then registered with that server, and
>I
>will start to receive multicast packets via PIM-Sparse mode. So what does
>the RP do in this??? I don't understand the application point of it.
>
>-Eddie
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:29 GMT-3