Skip to content
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
This repository was archived by the owner on Feb 25, 2026. It is now read-only.

Priority calculation not possible without knowing component #188

Closed

Description

@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.

Activity

  1. aboba commented on Apr 12, 2015

    @aboba
    Contributor

    One way to fix this would be to add a .createAssociatedGatherer() method to the IceGatherer, which would return an IceGatherer object with a component attribute of RTCP.

    partial interface RTCIceGatherer {
        readonly    attribute RTCIceComponent component;
        RTCIceGatherer createAssociatedGatherer ();
    };
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions