- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 May 2017 18:41:26 +0000
- To: public-webrtc-logs@w3.org
I agree that the expectations/recommendations for what candidates a browser gathers should be described somewhere. > for example Chrome sets the port on the tcp candidates it emits to 9 This just means it's an "active" TCP candidate, and will only be used to make an outgoing connection if a "passive" remote candidate is added. Which *is* something that should be supported, so that the browser can make a TCP connection to an Internet-accessible server when that's the only option available. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1238#issuecomment-303814811 using your GitHub account
Received on Wednesday, 24 May 2017 18:41:32 UTC