- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 Sep 2022 03:56:27 +0000
- To: public-webrtc-logs@w3.org
My opinion: The case of dropping a simulcast layer is exactly the same as the case of dropping one RTP stream on a transport: If the application sums over a set of RTP senders / receivers, and one of them is dropped, the sum will decrease. This is no different in the simulcast case, and once we've accepted that totals can decrease at all due to RTP objects going away, we should be consistent and do the same thing with the multiple RTP objects inside a simulcast stream. No special treatment just because they have the same MID. Add warnings in text, but don't do special things for simulcast. (A completely different question is if it's possible to remove simulcast layers, or whether the layers not currently accepted by the receiver are just deactivated. Not this bug.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/pull/672#issuecomment-1250539779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 September 2022 03:56:29 UTC