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 RTCIceCandidatePairs #187

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

Describe a match algorithm for two RTCIceCandidatePairs #187

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

Comments

@sam-vi
Copy link
Contributor

sam-vi commented Nov 6, 2023

Matching of RTCIceCandidatePairs is used by operations that take one or more candidate pairs as input, match them against previously known pairs, and perform some action on the respective pairs (eg. setSelectedCandidatePair).

The match algorithm should be based on matching the local and remote candidates respectively.

RTCIceCandidate matching is addressed by #186.

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).
sam-vi added a commit to sam-vi/webrtc-extensions that referenced this issue Dec 20, 2023
Fixes: w3c#187.

This PR depends on the candidate match algorithm described in w3c#192.

The candidate pair match algorithm will 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