Removing IceTransportsType::kNone and kNoHost.

248 views
Skip to first unread message

hb...@webrtc.org

unread,
Apr 18, 2017, 7:46:37 AM4/18/17
to discuss-webrtc

But we have:

It seems we should remove kNone and kNoHost and rename it to IceTransportPolicy. I filed this bug.

- Objections? Are any native applications still depending on these? Why/how?

Siddharth Toshniwal

unread,
Aug 20, 2018, 3:36:06 PM8/20/18
to discuss-webrtc
Hi all,

From what I see in the code this change is not implemented yet, hence dropping a note to respond to the request for inputs.

We are implementing a native WebRTC application that would get deployed on a server behind a static NAT. The server always has private IP addresses and these are not reachable from the public internet (WAN). However, the "server reflexive" address discovered by the native WebRTC code should be reachable from any host. To speed up the ICE discovery, we want to communicate only the reflexive candidates to the WebRTC peer. We achieve this by passing "kNoHost" as the IceTransportPolicy value.

I understand that we can also achieve the equivalent by passing "kAll" and then examining each discovered candidate to filter out any of those that are of the type "host" within our code. However, since the WebRTC code is giving this functionality already, we do use the same.

Thanks and Regards,
Siddharth
Reply all
Reply to author
Forward
0 new messages