On 03/13/2014 10:31 AM, Holger Kummert wrote: > > Hello, > > I do not understand XORP's behavior when running PIM/SM and Register > messages (that encapsulate multicast traffic) are received by the > RP from S. > What I am really missing is the Join msg towards S in order to avoid > the encapsulating overhead. Therefore the Register-Stop (in order to > stop sending the Register msgs) is also not sent by RP. > > Shouldn't both messages be sent according to RFC 4601, ch. 3.2? > > The only situation where I could force the Register-Stop to be sent > was by enabling and setting 'switch-to-spt-threshold' to '0'. > This sending is independent of any Join'ed receivers and happens > immediately after the receive of the first Register message. > But this is obviously not the intended usage. > > Anyhow under no circumstances any Join messages are sent by RP to S. > > Could someone give more insight on this?
I'm afraid I never knew much about multicast, and what I did learn while hacking on xorp mcast logic I have mostly forgotten. But, if you figure out a patch that makes xorp work better, please post it and I will try to review it. Thanks, Ben > > > Thanks in advance, > Holger > > _______________________________________________ > Xorp-users mailing list > [email protected] > http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users > -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Xorp-users mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
