flushing ICE candidates #53

robin-raymond opened this Issue Apr 12, 2014 · 3 comments


None yet
3 participants

robin-raymond commented Apr 12, 2014

Scenario: a network interfaces goes down and all associated candidates are no longer valid or server reflexive address changes.

There's no way to flush candidates that are no longer value. "onlocalcandidate" fires new candidates but does not inform of dead candidates. Likewise, there's no way to tell the remote party that candidates are gone/flushed. Over time, this can cause a build up of dead candidates that are not valid, especially as server reflexive network interfaces come and go.

juberti commented Apr 17, 2014

Assuming you are doing ICE restart to pick up new candidates, that will cause the old candidates to be flushed.

The impact of dead candidates is fairly minimal, so I'm not sure we need any specific handling other than ICE restart.

@robin-raymond robin-raymond added the 1.2 label Apr 29, 2014


aboba commented Jul 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment