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

ICE candidate gathering policy #47

aboba opened this issue Apr 10, 2014 · 0 comments

ICE candidate gathering policy #47

aboba opened this issue Apr 10, 2014 · 0 comments


Copy link

aboba commented Apr 10, 2014

ORTC API has no equivalent of WebRTC 1.0's RTCIceTransports attribute that indicates what kind of local candidates are gathered (see Section 4.2.3).

Proposed fix:

partial interface RTCIceTransport {
attribute RTCIceGatherPolicy gatherPolicy;

enum RTCIceGatherPolicy {

"all": Gather all ICE candidate types.
"nohost": Gather all ICE candidate types except for host candidates.
"relayonly": Only gather media relay candidates such as candidates passing through a TURN server. This can be used to reduce leakage of IP addresses in certain use cases.

robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Apr 12, 2014

Support for control of quality, resolution, framerate and layering added, as described in
RTCRtpListener object added and figure in Section 1 updated, as described in w3c#32
More complete support for RTP and Codec Parameters added, as described in w3c#33
Data Channel transport problem fixed, as described in w3c#34
Various NITs fixed, as described in w3c#37
Section 2.2 and 2.3 issues fixed, as described in w3c#38
Default values of some dictionary attributes added, to partially address the issue described in w3c#39
Support for ICE TCP added, as described in w3c#41
Fixed issue with sequences as attributes, as described in w3c#43
Fix for issues with onlocalcandidate, as described in w3c#44
Initial stab at a Stats API, as requested in w3c#46
Added support for ICE gather policy, as described in w3c#47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

2 participants