- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2023 03:27:39 +0000
- To: public-webrtc-logs@w3.org
The WPT may predate our stopping hack. [Section 5.2.1](https://datatracker.ietf.org/doc/html/rfc8829#section-5.2.1) says _"The next step is to generate "m=" sections, as specified in [[RFC4566](https://datatracker.ietf.org/doc/html/rfc4566)], [Section 5.14](https://www.rfc-editor.org/rfc/rfc4566#section-5.14). An "m=" section is generated for each RtpTransceiver that has been added to the PeerConnection, excluding any stopped RtpTransceivers"_. This seems to have supported the green WPT before the stopping hack, so it would perhaps be nice to preserve that JSEP logic, and I see no need to break it. If we added another _"MUST treat a [stopping](https://w3c.github.io/webrtc-pc/#dfn-stopping-0) transceiver as [stopped](https://w3c.github.io/webrtc-pc/#dfn-stopped)"_ JSEP hack here as well, then that might support the green WPT. But with Proposal A we wouldn't even need that hack, I think, which seems promising. @docfaraday WDYT? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2838#issuecomment-1471240402 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 March 2023 03:27:41 UTC