Status

()

defect
P3
normal
Rank:
29
3 years ago
2 years ago

People

(Reporter: drno, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox51 affected)

Details

(URL)

(Reporter)

Description

3 years ago
Latest JSEP draft suggests (SHOULD) that we implement ICE candidate pools:
https://rtcweb-wg.github.io/jsep/#rfc.section.3.5.4

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.
(Reporter)

Updated

3 years ago
backlog: --- → webrtc/webaudio+
Rank: 29

Comment 1

3 years ago
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.
(Reporter)

Updated

3 years ago
Duplicate of this bug: 1296901
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.