- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 08:12:40 +0000
- To: public-webrtc-logs@w3.org
https://www.rfc-editor.org/rfc/rfc3550.html#section-6.3.5 has rules for "timing out a participant" even if there is no bye. I wouldn't rely on that being implemented as specified though. The problem you are trying to solve is a large multiparty call (run over a single RTCPeerConnection) where participants (and each of them gets 2+ unique ssrcs) join and leave all the time. This leads to > RTP monitored objects are not [deleted](https://w3c.github.io/webrtc-stats/#dfn-deleted). describing a lot of participants that are no longer there which is quite a problem. Binding the lifetime to the lifetime of the transceiver (i.e. stopping it removing the associated stats) seems sensible -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/668#issuecomment-1239058357 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 08:12:42 UTC