-
Notifications
You must be signed in to change notification settings - Fork 115
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
RTCIceTransport selected candidate pair behavior when changing state #1981
Comments
Thoughts:
We should remove the "and null otherwise" from step 4 under "When the ICE Agent indicates that the selected candidate pair for an RTCIceTransport has changed". That way, there's no way to change [[SelectedCandidatePair]] from non-null to null, and also no way to fire the event with an empty candidate pair. (There's no definition for when the ICE Agent indicates that the selected candidate pair has changed; RFC 5245 section 11.1.1 (full implementations) says that the selected pair is empty only if there is no previous selected pair, so this is consistent with the above.) |
Harald's proposal sounds good to me. I can see the value in keeping the selected candidate pair set when transitioning to "failed". |
This issue was not resolved at TPAC. Short notes said "SelectedCandidatePair needs further work (do candidates go away?)" |
Proposal: When the |
I have some questions about the behavior of getSelectedCandidatePair() and the selectedcandidatepairevent in the following cases:
Also, when might the selectedcandidatepairevent fire with a newly-null selected candidate pair?
The text was updated successfully, but these errors were encountered: