RE: ICE freezing and Bandwidth Estimation from Bernard Aboba on 2018-05-31 (public-webrtc@w3.org from May 2018)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Thu, 31 May 2018 19:16:24 +0000
To: Christer Holmberg <christer.holmberg@ericsson.com>, Peter Thatcher <pthatcher@google.com>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <DM5PR00MB032728F1AFF006C4727E7379EC630@DM5PR00MB0327.namprd00.prod.outlook.com>

Christer said: 

"With “almost no one”, are you referring to browser vendors, or ICE vendors in general?"

[BA] In ORTC we had a freezing API (IceTransportController).  There are 4 implementations, but I believe only one of them supported the freezing API (Ortc lib)

Without support for the freezing API, the Edge ICE implementation did not support freezing either in ORTC API, or WebRTC 1.0 via adapter.js shim. 

While there have been lots of ICE interop issues to work through in the Edge implementation, freezing was not one of them.

Received on Thursday, 31 May 2018 19:16:52 UTC