Re: [webrtc-pc] Should the remote track mute in response to replaceTrack(null)? (#3077)

> Note about the SSRC being removed due to timeout:
>
> It's defined in https://datatracker.ietf.org/doc/html/rfc3550#section-6.3.5 as 2 RTCP reporting intervals (as computed in section 6.3.1). But the whole set of calculations here is designed based on multicast media sharing, which is not what we're doing, so it's somewhat unlikely that this calculation is followed exactly.

2 RTCP reporting intervals is, what, maybe 10 seconds? 20 seconds tops?

This is demonstrably not implemented and would make `replaceTrack(null)` a complete foot-gun. Can we remove this part from the spec?

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/3077#issuecomment-3351161754 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 30 September 2025 10:19:41 UTC