RE: Issue 188: Priority calculation not possible without component

Since the IceGatherer gathers upon construction, it would seem that the component also needs to be known upon construction so that the priority can be calculated.

One way to do this would be for a constructed IceGatheret object to have a component of RTP by default, and add a .createAssociatedGatherer() method to the IceGatherer, which would return an IceGatherer object with a component attribute of RTCP.
________________________________
From: Bernard Aboba<mailto:Bernard.Aboba@microsoft.com>
Sent: ‎4/‎11/‎2015 2:40 PM
To: public-ortc@w3.org<mailto:public-ortc@w3.org>
Subject: Issue 188: Priority calculation not possible without component





>From Robin Raymond:

https://tools.ietf.org/html/rfc5245#section-4.1.2.1

   priority = (2^24)*(type preference) +
              (2^8)*(local preference) +
              (2^0)*(256 - component ID)


The trouble is that the gatherer will start gathering on construction and reporting candidates. The trouble is the priority cannot be calculated as per recommendation because the component ID is not known upon construction. Associated RTCP based gatherers are passed into the start method for a transport created by "createAssociatedTransport()" but the gatherer is not specifically an RTCP based gatherer.

—
Reply to this email directly or view it on GitHub<https://github.com/openpeer/ortc/issues/188>.