You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
public: Candidates with private IP addresses [RFC1918] will be filtered out. This prevents exposure of internal network details, at the cost of requiring relay usage even for intranet calls, if the NAT does not allow hairpinning as described in [RFC4787], section 6.
While this is now supported into the WebRTC 1.0 API's RTCIceTransportPolicy, there is no equivalent in ORTC RTCIceGatherPolicy.
JSEP Section 4.1.1 (see: https://tools.ietf.org/html/draft-ietf-rtcweb-jsep) defines the meaning of "public" in WebRTC 1.0 RTCIceTransportPolicy:
This patch adds "public" to ORTC RTCIceGatherPolicy, addressing Issue #305
JSEP Section 4.1.1 (see: https://tools.ietf.org/html/draft-ietf-rtcweb-jsep) defines the meaning of "public" in WebRTC 1.0 RTCIceTransportPolicy:
public: Candidates with private IP addresses [RFC1918] will be filtered out. This prevents exposure of internal network details, at the cost of requiring relay usage even for intranet calls, if the NAT does not allow hairpinning as described in [RFC4787], section 6.
While this is now supported into the WebRTC 1.0 API's RTCIceTransportPolicy, there is no equivalent in ORTC RTCIceGatherPolicy.
WebRTC 1.0 Issues:
w3c/webrtc-pc#384
w3c/webrtc-pc#8
WebRTC 1.0 PR: w3c/webrtc-pc#432
The text was updated successfully, but these errors were encountered: