- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Sat, 15 Mar 2025 20:16:04 +0000
- To: public-webrtc-logs@w3.org
This becomes complex due to the way RTCP is structured. RTP is simple: If you have an SSRC in the header, that's the SSRC that the packet belongs to. But with destination-to-source RTCP, the SSRC in the header is the somewhat-arbitrarily assigned "SSRC used for report source", and the really relevant SSRCs (more than one!) are deeply buried in the payload. Suggestion: Make it clear that outbound-rtp only counts RTP packets for this SSRC. If we want to know how much goes to RTCP, we may add more counters - but I'd think that this should not be a counter indexed on SSRC. (Really happy to see transport + candidate-pair add up exactly in this case, though!) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/507#issuecomment-2726981179 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 15 March 2025 20:16:06 UTC