Is periodic RTCP RR needed on a video receive stream that is not receiving RTP?

[Roman Yuan]

Hi,

We are trying to understand whether libwebrtc should keep sending RTCP Receiver Reports on a video receive stream that is not receiving RTP.

Typical setup: Unified Plan, BUNDLE, remote SDP lists SSRCs, but the local side is inactive or receive is disabled (SetReceive(false)). We may pre-allocate several such receive paths. On the wire we still see periodic RTCP (~1 Hz per stack), often compound packets with empty RR (no report blocks).

From the code path:

A VideoReceiveStream still gets a receiver-only ModuleRtpRtcpImpl2 (compound RTCP, ~1 s interval).
Inbound RTP can be gated (receiving_ / SetReceive(false)), so the stream is not really “receiving” in the media sense.
The RTCP stack can still schedule and build RR without any received RTP; in compound mode, empty RR is allowed.
So the design seems to treat “receive stream exists” and “periodic RR sender exists” as separate from “currently receiving RTP.”

Our question: For a video receive stream that is not accepting RTP, is there a normative or implementation reason to keep sending periodic RTCP RR (including empty compound RR)? Or is that mainly legacy RFC 3550 compound behavior with little benefit when no media is being received?

Thanks a lot.

[Philipp Hancke]

does this go away if you negotiate rtcp-risze?

--
This list falls under the WebRTC Code of Conduct - https://webrtc.org/support/code-of-conduct.
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/discuss-webrtc/ca6f7aed-0cff-4161-8e3a-1f5fb12acc46n%40googlegroups.com.