Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

flushing ICE candidates #53

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

flushing ICE candidates #53

robin-raymond opened this issue Apr 12, 2014 · 3 comments
Labels
1.2

Comments

@robin-raymond
Copy link
Contributor

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.
@robin-raymond
Copy link
Contributor Author

http://lists.w3.org/Archives/Public/public-ortc/2014Apr/0026.html

@juberti
Copy link

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.

@aboba
Copy link
Contributor

aboba commented Jul 21, 2016

Peter's candidate removal draft:
https://tools.ietf.org/html/draft-thatcher-ice-remove-candidate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
1.2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aboba @juberti @robin-raymond