- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Dec 2023 09:33:47 +0000
- To: public-webrtc-logs@w3.org
The relevant spec link is https://w3c.github.io/webrtc-pc/#rtcicegatheringstate-enum Question: Why are there two transports? Given that https://w3c.github.io/webrtc-pc/#rtcicetransport says "An ICE restart for an existing [RTCRtpTransceiver](https://w3c.github.io/webrtc-pc/#dom-rtcrtptransceiver) will be represented by an existing [RTCIceTransport](https://w3c.github.io/webrtc-pc/#dom-rtcicetransport) object, whose [state](https://w3c.github.io/webrtc-pc/#dom-icetransport-state) will be updated accordingly, as opposed to being represented by a new object." In the unbundled case, both transports would transition to "new", I guess. So what's the case when this can happen? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2914#issuecomment-1851642417 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 December 2023 09:33:50 UTC