- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2023 03:04:06 +0000
- To: public-webrtc-logs@w3.org
> The same file also tests that [transceivers stopped prior to being negotiated never show up in the SDP](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/webrtc/RTCRtpTransceiver-stop.html;l=22;drc=232359e58644a36b534576ec7b65d070c4f75040) which is also good. - Proposal C: Implement the spec. There is no spec support for that green WPT test. The spec is quite clear: [stop()](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver-stop): _"Irreversibly marks the transceiver as [stopping](https://w3c.github.io/webrtc-pc/#dfn-stopping-0) ... cause[ing] future calls to [createOffer](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection-createoffer) to generate a zero port in the [media description](https://w3c.github.io/webrtc-pc/#dfn-media-description) for the corresponding transceiver, as defined in [[RFC8829](https://w3c.github.io/webrtc-pc/#bib-rfc8829)] ([section 4.2.1.](https://datatracker.ietf.org/doc/html/rfc8829#section-4.2.1)) (The user agent MUST treat a [stopping](https://w3c.github.io/webrtc-pc/#dfn-stopping-0) transceiver as [stopped](https://w3c.github.io/webrtc-pc/#dfn-stopped) for the purposes of RFC8829 only in this case)."_ -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2838#issuecomment-1471216013 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:04:09 UTC