- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Tue, 31 Oct 2023 18:50:18 +0000
- To: public-webrtc@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-extensions:
== Clarify how icecandidatepairnominate and selectCandidatePair are to be used ==
I feel https://github.com/w3c/webrtc-extensions/pull/174 merged without an explainer or example of its intended use, side-effects, or how to use it responsibly.
I've gotten some questions internally about when this API would be useful, and I couldn't immediately answer. The only situation they could think of was one where the service is operating on a particular network that it controls? Is that true? An explainer or intro or example to point at would be good.
A [slide](https://lists.w3.org/Archives/Public/www-archive/2023Sep/att-0010/WEBRTCWG-2023-09-12.pdf#page=65) presented at TPAC says what the app can do:
> Application can defer nomination of a candidate pair picked by the controlling ICE agent ...
> Application can select any valid candidate pair to send data ...
> Both controlling and controlled side can select a candidate pair to send data ...
But it doesn't say why or what problem is solved. The [only use UDP port 3478](https://lists.w3.org/Archives/Public/www-archive/2023Sep/att-0010/WEBRTCWG-2023-09-12.pdf#page=67) example given seems like it could be solved with `{`[`iceTransportPolicy`](https://www.w3.org/TR/webrtc/#dom-rtcconfiguration-icetransportpolicy)`: "relay"}`, or by filtering [`icecandidate`](https://www.w3.org/TR/webrtc/#event-icecandidate) events, or am I missing something?
> Application now has the responsibility & flexibility to synchronize send/receive ...
Can we lay out these responsibilities in an explainer with examples showing what's minimally needed to use the API correctly?
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/184 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 31 October 2023 18:50:20 UTC