[WIP] TCP ICE #89
Draft
[WIP] TCP ICE #89
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation successfully gathers host and server-reflexive TCP candidates, and connects to the other side. Code related to relay candidates wasn't modified yet, so in this state we can expect everything to crash and burn whenever a TURN server is specified in
ice_servers.Note that not all STUN servers support TCP (e.g.
stun.l.google.com:19302does not).ref: elixir-webrtc/ex_webrtc#238
TODO:
TODOsfrom commentsRelevant RFCs: