- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Aug 2020 13:53:03 +0000
- To: public-webrtc@w3.org
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc: == Make the set of transports for a PC obvious == It seems kind of obvious that the set of transports that are considered for IceGatheringState computation is the set of transports referenced by visible transceivers + the transport referenced by the SctpTransport (if non-null). Thus, a transport attached only to a transceiver will disappear from the set when the transceiver transits to "stopped" after a negotiation, but it doesn't go away simply because "stop" is called. However, I don't think that's said explicitly anywhere. Should it be? Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2563 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 August 2020 13:53:06 UTC