Issue 223: Asymmetry between RTP and RTCP within the API

• From: Bernard Aboba <Bernard.Aboba@microsoft.com>
• Date: Tue, 30 Jun 2015 15:25:14 +0000
• To: "public-ortc@w3.org" <public-ortc@w3.org>
• Message-ID: <BLUPR03MB149E1F3E5A2D7B914CF9647ECA90@BLUPR03MB149.namprd03.prod.outlook.com>

In the current API, we have iceTransport.createAssociatedTransport() for creation of an RTCP IceTransport and iceGatherer.createAssociatedGatherer() for creation of an RTCP IceGatherer. However, the RTCP IceTransport and RTCP IceGatherer are not associated until rtcpIceTransport.start() is called.

In contrast, an RTP IceTransport is constructed with an RTP IceGatherer as an argument, so the association exists upon construction. As noted in other issues, this enables pruning of an RTP IceGatherer, as well as potentially enabling an RTP IceTransport to respond to incoming ICE connectivity checks. 

Why should this not be possible for an RTCP IceTransport or RTCP IceGatherer?  This does not seem right. 

Received on Tuesday, 30 June 2015 15:25:43 UTC