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

Describe a match algorithm for two RTCIceCandidates #186

Closed
sam-vi opened this issue Nov 6, 2023 · 0 comments · Fixed by #192
Closed

Describe a match algorithm for two RTCIceCandidates #186

sam-vi opened this issue Nov 6, 2023 · 0 comments · Fixed by #192
Assignees

Comments

@sam-vi
Copy link
Contributor

sam-vi commented Nov 6, 2023

Matching of RTCIceCandidates is used by operations that take one or more RTCIceCandidatePair dictionaries as inputs, validate the input, and instruct the ICE agent to perform some action on the respective candidate pairs (eg. setSelectedCandidatePair).

There are two options for match RTCIceCandidates:

  1. An instance match
  2. A comparison of the candidate, sdpMid, sdpMLineIndex, and usernameFragment attributes of RTCIceCandidate

Option 2 may be preferable since the RTCIceCandidate is JSON-stringifiable with those 4 attributes.

sam-vi added a commit to sam-vi/webrtc-extensions that referenced this issue Dec 20, 2023
Fixes: w3c#186.

The algorithm matches the (non-derived) candidate, sdpMid,
sdpMLineIndex, and usernameFragment attributes of RTCIceCandidate.

The candidate match algorithm will be used in the candidate pair match
algorithm (w3c#187), which will, in turn, be used in validation steps for
RTCIceTransport methods (w3c#188).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant