W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2018

RE: ICE freezing and Bandwidth Estimation

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Thu, 31 May 2018 15:00:02 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Peter Thatcher <pthatcher@google.com>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <DM5PR00MB0327CB2876189D11EB7532B7EC630@DM5PR00MB0327.namprd00.prod.outlook.com>
Christer said: 

"Why would you need to do something in the API? Freezing is taken care of by the ICE stack, isnít it?

Or, is the idea to allow the user to override what is going on in the check lists?"

[BA]  The ORTC API contained an IceTransportController Interface: https://draft.ortc.org/#rtcicetransportcontroller*

The rationale for this related to freezing and bandwidth estimation, but implementation experience casts doubt on whether this makes sense.

Edge did not implement the IceTransportController for freezing and this does not appear to have caused any problems. 

When Edge considered the bandwidth estimation problem, the IceTransportController did not appear to be the right design, because it was not at the right layer and related to two distinct needs.

Ortc Lib did implement the IceTransportController for freezing, but not for bandwidth estimation. 
Received on Thursday, 31 May 2018 15:00:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:41 UTC