W3C home > Mailing lists > Public > public-ortc@w3.org > December 2015

Issue 293: Remote peer ICE-lite implementation

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Fri, 4 Dec 2015 16:55:46 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <BY2PR03MB160603362B0D0A515FD5890EC0C0@BY2PR03MB160.namprd03.prod.outlook.com>
As noted in JSEP Section 5.1.2, "the remote endpoint may use a Lite implementation; implementations MUST properly handle remote endpoints which do ICE-Lite."

WebRTC 1.0 handles this by allowing an a=ice-lite line in a Remote Description. How is the equivalent functionality supported in ORTC API?

A potential approach:

partial dictionary RTCIceParameters {
boolean? iceLite;
};

iceLite of type boolean, nullable
Whether ICE lite is supported (true) or not (false). If unset, ICE lite is not supported. Since browsers support full ICE, getLocalParameters().iceLite must not be set. This attribute is only set in remote parameters signaled by a remote peer (such as a gateway) that only supports ICE lite.
Received on Friday, 4 December 2015 16:56:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:39:57 UTC