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

Server cannot be reached - Issues with IPv6 #542

Closed
aboba opened this issue Mar 10, 2016 · 1 comment
Closed

Server cannot be reached - Issues with IPv6 #542

aboba opened this issue Mar 10, 2016 · 1 comment
Assignees

Comments

@aboba
Copy link
Contributor

aboba commented Mar 10, 2016

In Section 4.9.3.2 it is stated:
If the server could not be reached, errorCode will be set to a TBD value in the 7XX range, as this does not conflict with the STUN error code range.

This will be a problem for IPv6 where the browser can have interfaces (such as tunnel interfaces) with routability problems.

From Robin Raymond:
"I'm not sure this particular error is wise. In any implementation (especial IPV6), it's very likely many host candidates will not be able to reach the TURN server or STUN server because they don't route appropriately. So you will warn/flag these as being failed but with other host candidates they actually succeed. The programmer will think things are going horribly wrong when this is probably normal.

Further, if you don't indicate that this URI is actually succeeding then the programmer is going to be somewhat in the dark as to what's going on.

I would only use the "cannot contact server" error if NONE of the host IPs could reach the server. (Although that could just indicate a general connectivity problem and not really a server problem)."

@fluffy
Copy link
Contributor

fluffy commented Mar 14, 2016

We need someway to debug which TURN serves could not be reach.

aboba added a commit that referenced this issue May 2, 2016
aboba added a commit to w3c/ortc that referenced this issue May 2, 2016
aboba added a commit to w3c/ortc that referenced this issue May 12, 2016
Grammatical improvement.  Related to Issue w3c/webrtc-pc#542 (from WebRTC 1.0).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants