RTCIceGatherPolicy harmonization with WebRTC

[stpeter]

ORTC has:

enum RTCIceGatherPolicy {
"all",
"nohost",
"relay"
};

WebRTC has:

enum RTCIceTransportPolicy {
"none",
"relay",
"all"
};

Consistency might be desirable with respect to "none" vs. "nohost".

[aboba]

In the current API, an RTCIceGatherer is constructed from the RTCIceGatherPolicy, but there is no method to change the RTCIceGatherPolicy after construction. As a result, an RTCIceGatherPolicy of "none" could not be changed to another value. Also, there is no way to change the iceServers once an RTCIceGatherer is constructed. So I think there is a bigger issue here.

[robin-raymond]

This RTCIceTransportPolicy is a transport policy not a gather policy. This is not a gather policy. If we were to have RTCIceTransportPolicy it would be on the IceTransport not on the IceGatherer.

[aboba]

In WebRTC 1.0 there an open issue (see: w3c/webrtc-pc#384 ), relating to harmonizing RTCIceTransportPolicy.none with the values defined in draft-ietf-rtcweb-jsep Section 4.1.1, which does not include “none” but does include “public”, which is defined as follows:

“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.”

[aboba]

Since "none" has now been removed from WebRTC 1.0 RTCIceTransportPolicy, I would like to close this issue and open another one related to sync'ing the new "public" setting in RTCIceTransportPolicy.

[aboba]

The following WebRTC 1.0 PR will remove RTCIceTransportPolicy.public:
w3c/webrtc-pc#544

Note that "all" no longer includes addresses that have been filtered by the browser.