W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2022

[webrtc-provisional-stats] Sender/receiver stats needs to reference RTP stream stats or the other way around (#35)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 23 Jun 2022 14:22:27 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1282489161-1655994140-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-provisional-stats:

== Sender/receiver stats needs to reference RTP stream stats or the other way around ==
Either "sender" should have a list of "outboundRtpIds" or "outbound-rtp" should have a single "senderId". Due to simulcast there is a 1:N relationship here.
Similar for the receive side (except simulcast is not a thing there so the relationship would be 1:1).

No strong preference here but avoiding lists is nice so outbound-rtp.senderId might be nicer than sender.outboundRtpIds, on the other hand I'd like to wait and get the RTP streams lifetimes clarified (https://github.com/w3c/webrtc-stats/issues/643) before deciding what to do here.

If RTP streams have permanent life times, then sender.outboundRtpIds has the benefit of telling you which RTP streams are active as opposed to which ones are obsolete in the case of ssrc changing.

Please view or discuss this issue at https://github.com/w3c/webrtc-provisional-stats/issues/35 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 June 2022 14:22:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC