- From: docfaraday via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Oct 2022 18:53:21 +0000
- To: public-webrtc-logs@w3.org
> > Then again, this is one of those situations that a reasonable implementation should not care about. > > It would seem that Chrome, Chromium, or libWebRTC(not sure which at the moment) does care, based on the observed behaviour in Chrome. I'll try and see if I can reproduce this in other Chromium browsers and raise a bug. > > Given the observed behaviour in Chrome, the de-facto correct implementation becomes MUST, at least until Chrome's behaviour is changed. The information in this report only indicates that Chrome keeps the a=ssrc in its own SDP; there's no mention so far of failure to interop with a remote endpoint that removes a=ssrc when a=inactive. Is there an interop problem here with Chrome and Firefox, for example? -- GitHub Notification of comment by docfaraday Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2783#issuecomment-1297527039 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 October 2022 18:53:22 UTC