SSM, RTCP, SAP

["Tony Ballardie" <ballardie@dial.pipex.com>]

What's the current thinking about handling RTP apps with
SSM; RTP apps are intrinsically multi-sender (==> Receiver Reports)?

Similarly, what about (global) SAP?

Given that SAP comes under the category of "bootstrap" (I guess), wouldn't
it be an idea to RPF flood SAP (minus the prune), and not incur any state
for that flood? Such a flood would result in SAP announcements flowing
over redundant paths, but a) they're infrequent, b) all SDRs want them
within the flood (mcast) scope, c) they're bootstrap so they fit within
a flood model.

So, how to prevent (s,g) state for SAPs? Define a ToS bit pattern that tells
routers not to create fwd state for this packet??

I'm not suggesting doing the same for RTCP RRs, since they don't
fall under bootstrap, and require sender/member-constrained distribution.

thoughts?

Tony