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

consider moving ICE address matching / time ordering logic into this draft #7

Closed
marten-seemann opened this issue Jul 29, 2023 · 0 comments · Fixed by #11
Closed

consider moving ICE address matching / time ordering logic into this draft #7

marten-seemann opened this issue Jul 29, 2023 · 0 comments · Fixed by #11

Comments

@marten-seemann
Copy link
Owner

Then we wouldn't need a dependency on ICE.

Apparently ICE was designed with the assumption that the application might have several connections to the same endpoint at the same time, e.g. to demultiplex audio and video. Obviously, this isn't needed when using a multiplexed transport, and might lead to some simplifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant