- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Wed, 16 Jul 2014 00:27:58 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
Iņaki Baz Castillo said: "Now I've realized that I don't understand the question. The RTCIceTransportController class has no events or "state" attributes. ICE state are per RTCIceTransport instance. May be the difficult point to get here is that we can attach multiple RTCIceTransports into a single RTCIceTransportController but still must call gather() or start() in each RTCIceTransport." [BA] Yes, this is an important distinction between ORTC API and WebRTC 1.0. The closest equivalent of the WebRTC 1.0 "ICE Agent" is the "RTCIceTransportController" in ORTC but the analogy isn't very good since the individual ICE Transports have their own RTCIceRole, RTCIceTransportState and RTCIceGatheringState. Normally, RTCIceTransportController.addTransport would be called before start() or gather() is called on any of the RTCIceTransports (that is what is shown in Section 4.4 Example 5), but the question is what happens if it is called after some RTCIceTransports have been started and gather has been called. A scenario in which this is useful does not come to mind, but it still seems worthwhile to define what should happen.
Received on Wednesday, 16 July 2014 00:28:41 UTC