Re: [webrtc-pc] No way to observe DataChannel-only transport events in initial negotiation (#2899)

In the TPAC meeting Henrik mentioned a variant of proposal B - adding a member to the pc.oniceconnectionstatechange data that is the iceTransport that it relates to - this seems cleaner and simpler than adding an (array of) iceTransports properties to the Peer connection.

I don't like surfacing a (potentially ghost) sctpTransport who's values are wrong or non-existent just to get an iceTransport.


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


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

Received on Tuesday, 12 September 2023 12:49:58 UTC