Issue 190: TCP a: setup attribute for transport from Bernard Aboba on 2015-05-01 (public-ortc@w3.org from May 2015)

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Fri, 1 May 2015 16:56:10 +0000
To: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <BLUPR03MB1496E23B57ACD50F940AAE9ECD50@BLUPR03MB149.namprd03.prod.outlook.com>

Issue submitted by Robin Raymond:
https://github.com/openpeer/ortc/issues/190

We do have a way to advertise "so", "active" and "passive" TCP candidates but we have no way to tell a transport to behave in "active", "passive" or "actpass" modes of operation.

Proposed fix:

Add the following to Section 3.11.3:
Browsers MUST gather active TCP candidates and only active TCP candidates. Servers and other endpoints MAY gather active, passive or so candidates.

Received on Friday, 1 May 2015 16:56:38 UTC