- From: ketsebum via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Oct 2022 15:31:36 +0000
- To: public-webrtc@w3.org
ketsebum has just created a new issue for https://github.com/w3c/webrtc-pc: == Continuous ICE Gathering - Feature Request == ## Background The feature request is to change how browsers complete their ICE Gathering. Currently, after a short period after establishing the call, we stop gathering new candidates and move to a completed state. However, due to an event that changes network conditions for the worse, the client may disconnect from the call prematurely. While, ICE Restart solves this problem it is a slower response than preferred, and could be solved if we continued to gather new ICE candidates throughout the call. The "walk-out-the-door" problem explains the issue that continuous ICE gathering would solve, described by these slides: https://www.ietf.org/proceedings/94/slides/slides-94-ice-6.pdf ## Other Implementations Chromium has this implemented for their native implementations, and they use a flag to enable this: https://chromium.googlesource.com/external/webrtc/+/b6760f9e4442410f2bcb6090b3b89bf709e2fce2/webrtc/api/android/java/src/org/webrtc/PeerConnection.java#126 ## Request The request here is to be able to turn on continuous ICE gathering through a similar config flag during the creation of the peer connection. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2791 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 October 2022 15:31:38 UTC