There are use-cases where I am not interested in the local candidates such as when talking to an SFU. In that case, the SFU will discover the candidates as peer-reflexive.
Would ICE be faster in this case if the local agent did not have to create pairs and do checks? I think that is marginal at best.
So the nohost option would only be useful if the user agent would place more privacy restrictions on gathering candidates such as a prompt asking for permission. I haven't seen that yet and the "only default route" gathering policy (mode 3 from https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-03) seems to work well enough.
ORTC has an
RTCIceGatherPolicy
of "nohost" while WebRTC 1.0 does not define anRTCIceTransportPolicy
of "nohost":https://rawgit.com/w3c/webrtc-pc/master/webrtc.html#rtcicetransportpolicy-enum
Related WebRTC 1.0 PR: w3c/webrtc-pc#1176 (RTCIceTransportPolicy enum descriptions)
The text was updated successfully, but these errors were encountered: