- From: jianjunz via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Oct 2017 07:16:33 +0000
- To: public-webrtc-logs@w3.org
jianjunz has just created a new issue for https://github.com/w3c/webrtc-pc: == Adding more values to RTCIceTransportPolicy Enum == [1] defines 4 specific modes for candidate collection. However, RTCIceTransportPolicy Enum only has 2 values. Currently, user agents choose which mode is going to be applied in certain circumstances. Should we add more values to RTCIceTransportPolicy Enum so applications have the chance to change UA's default behavior? UA may request permission from the end user before changes are made. Here is an example of different candidate collection behaviors between Chrome and Firefox: Run data channel sample [2] in a machine equipped with two network adapters. Chrome collects candidates on all network adapters. Firefox only collects candidates on default route and associated local addresses. [1] https://tools.ietf.org/html/draft-ietf-rtcweb-ip-handling-04 [2] https://webrtc.github.io/samples/src/content/datachannel/basic/ Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1644 using your GitHub account
Received on Wednesday, 25 October 2017 07:16:36 UTC