[webrtc-pc] RTCPeerConnection.iceGatheringState is updated differently for datachannel than audio/video (#2898)

docfaraday has just created a new issue for https://github.com/w3c/webrtc-pc:

== RTCPeerConnection.iceGatheringState is updated differently for datachannel than audio/video ==
From https://w3c.github.io/webrtc-pc/#rtcicegatheringstate-enum

> The set of transports considered is the one presently referenced by the [RTCPeerConnection](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection)'s [set of transceivers](https://w3c.github.io/webrtc-pc/#transceivers-set) and the [RTCPeerConnection](https://w3c.github.io/webrtc-pc/#dom-rtcpeerconnection)'s [[[SctpTransport]]](https://w3c.github.io/webrtc-pc/#dfn-sctptransport) internal slot if not null.

[[SctpTransport]] is set when the answer is set:

https://w3c.github.io/webrtc-pc/#ref-for-dfn-sctptransport-4

Whereas transports are set on senders/receivers in sLD:

https://w3c.github.io/webrtc-pc/#ref-for-dfn-sendertransport-2
https://w3c.github.io/webrtc-pc/#ref-for-dfn-receivertransport-2

This means that we do not see icegatheringstatechange events/updates until we reach stable if we have a datachannel only, but we get those events/updates in have-local-offer if that datachannel is bundled with an audio or video msection!


Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2898 using your GitHub account


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

Received on Monday, 28 August 2023 15:34:37 UTC