Re: [webrtc-pc] Composed RTCPeerConnection.gatheringState seems wrong in some cases (#2914)

What's the model that forces you to assume two underlying transports?
https://datatracker.ietf.org/doc/html/rfc8445#section-9 doesn't seem to assume that the transport is changed - the RTCIceTransport represents "the ICE transport layer for the RTP or RTCP component of a transceiver or group of transceivers".

To my mind, an RTCIceTransport manages a group of candidate pairs, some of which have data flowing on them; an ICE restart throws out the old ones (except the one that is in use, until changed), and tries to create new ones.

None of this should be modeled as creating a new transport.


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


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

Received on Thursday, 14 December 2023 07:36:05 UTC