Open Bug 1291894 Opened 8 years ago Updated 2 years ago

Implement ICE pool allocations


(Core :: WebRTC: Networking, defect, P3)




Tracking Status
firefox51 --- affected


(Reporter: drno, Unassigned)




Latest JSEP draft suggests (SHOULD) that we implement ICE candidate pools:

We can't do it easily on a global (Firefox) level, so before a PeerConnection gets created.
But creating a pool once a nICEr instances gets created, right after a PeerConnection got instantiated should be doable.
backlog: --- → webrtc/webaudio+
Rank: 29
I think doing it after the PC was created would be just as good as a global pool and would work out fine. Basic use case is when page is loaded, it creates a PC and a small pool of candidates. Then later when an call is made, it is all ready to go.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.