- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 26 Feb 2024 17:58:56 +0000
- To: public-webrtc-logs@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-stats: == Should RTCRtptransceiver.stop() cause inbound-rtp stats to disappear? == This [language on RTP stats](https://w3c.github.io/webrtc-stats/#the-rtp-statistics-hierarchy) seems to go against https://github.com/w3c/webrtc-stats/issues/26: _"RTP monitored objects are deleted when the corresponding RTP sender or RTP receiver is reconfigured to remove the corresponding RTP stream. This happens for the old SSRC when the ssrc changes, a simulcast layer is dropped or the RTCRtpTransceiver's currentDirection becomes "stopped""_. The _"receiver is reconfigured"_ part seems fine, and probably describes intent, that things stick around until replaced. But this part: _"This happens ... when ...the RTCRtpTransceiver's currentDirection becomes `"stopped"`"_ ends up meaning stats are deleted on [pc.close](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-close) (which will [stop the RTCRtpTransceiver](https://w3c.github.io/webrtc-pc/#dfn-stop-the-rtcrtptransceiver)). Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/784 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 26 February 2024 17:58:58 UTC