Re: [webrtc-pc] Updates to RTCPeerConnection.connectionState should happen when new RTCDtlsTransports/RTCIceTransports are created and destroyed due to negotiation (#2817)

So, the more I think about this, the more it seems appropriate to defer the updates to RTCPeerConnection.connectionState/iceConnectionState until the answer is set. A local offer that creates a new transport does not mean a whole lot; the transport could be negotiated away (due to bundle or an m-section rejection), rolled back, or maybe the answer never comes. It only matters once the answer is set.

Now, I _can_ see updating the gathering state; after sLD(offer) we expect to see trickle candidates, so I would also expect to see gathering state changes.

-- 
GitHub Notification of comment by docfaraday
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2817#issuecomment-1689950435 using your GitHub account


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

Received on Wednesday, 23 August 2023 13:18:00 UTC