- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Apr 2025 00:03:17 +0000
- To: public-webrtc-logs@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-stats: == RTCRemoteOutboundRtpStreamStats definition is off? == https://w3c.github.io/webrtc-stats/#remoteoutboundrtpstats-dict* defines reportsSent as > the total number of [RTCP Sender Report](https://w3c.github.io/webrtc-stats/#dfn-sender-report) (SR) blocks sent for this [SSRC](https://w3c.github.io/webrtc-stats/#dfn-ssrc). However, those stats are about the SRs which do not define a "I sent you this many SRs" mechanism, see [here](https://datatracker.ietf.org/doc/html/rfc3550#section-6.4.1) for the format. libWebRTC counts received SRs [here](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/modules/rtp_rtcp/source/rtp_rtcp_interface.h;l=169;drc=f667feb8a5c6f227b49328ce78a062acc4f81187;bpv=1;bpt=1). > The RTCRemoteOutboundRtpStreamStats dictionary represents the remote endpoint's measurement metrics for its outgoing RTP stream (corresponding to an outgoing RTP stream at the sending endpoint) sounds odd. The remote outbound stream is an incoming stream at the receiving endpoint, no? > The timestamp reported in the statistics object is the time at which the corresponding [RTCP SR](https://w3c.github.io/webrtc-stats/#dfn-sender-report) was received. This one sounds like this object is about receiving SRs. But a few lines below we have > This differs from timestamp, which represents the time at which the statistics were generated or received by the local endpoint. which contradicts Should the field be named reportsReceived (ugh)? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/806 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 April 2025 00:03:18 UTC