- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 29 Aug 2022 07:27:53 +0000
- To: public-webrtc-logs@w3.org
> Isn't 1A implemented? Or are the objects created by the receiver ahead of time? On second thought, yes 1.A is already implemented ([link](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/pc/rtc_stats_collector.cc;l=1924;drc=2330c1533e39e4f8c195b0a2a05802ea9dee9c85)). I revise my vote to 1.A to match implementation and to avoid headache on what to do when ssrc goes from unknown to known on the same stats object. > In 1B -- What does SSRC being optional mean? Is it because no packet is received on the mid and therefore the SSRC is unknown? What value would an empty inbound-RTP json have if no packet has been sent or received? Yeah in the event of not having received packets, the 1.B proposal would still create the inbound-rtp with undefined or zero values. It's a rather pointless object, it just lets you know which streams have been configured regardless if packets have been received yet. Not worth the additional complexity I guess. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/643#issuecomment-1229887132 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 August 2022 07:27:55 UTC