Re: [Ice] ICE PAC: When to start the timer waiting for possible peer reflexive candidates?

[Nils Ohlmeier <[e-mail]>]

> On Apr 25, 2019, at 15:26, Roman Shpount <[e-mail]> wrote:
> 
> On Thu, Apr 25, 2019 at 3:45 PM Nils Ohlmeier <[e-mail] <mailto:[e-mail]>> wrote:
> 
> I see ICE pac only as a not perfect workaround to cover for some corner cases. While solving this via an extra signaling message might be the better solution I think such a proposal should be done via a separate draft if desired/needed.
> 
> I understand the desire to limit the scope of this draft. From what I can see there are 3 options:
> 
> 1. Start timer when local ICE candidates collection was complete and at least one ICE candidates was received from the remote via signaling message or STUN bind request (timer starts when both conditions must be satisfied). The problem with this is timer might never start and agent will wait indefinitely.
> 
> 2. Start timer when ICE candidates collection was complete or an ICE candidates was received from the remote via signaling message or STUN bind request (timer starts when either condition is satisfied). The problem here is that if signaling messages are delivered too slowly, ICE nomination will fail even when working candidate pair is potentially present.

Option 2 is basically what was implemented in Firefox for quite some time. But we got too many failure reports from the field. So we switched to something similar to Option 1. Thus I would advice against trying option 2.

Option 1 appears to be the reasonable although not perfect solution.

Best
  Nils Ohlmeier

> 3. Add some sort of extra signaling to indicate when ICE checks were complete. In case of WebRTC this option can be implemented via option 1 and some sort of application specific communications which will stop the indefinite wait.
> 
> Based on this I would prefer going with option 1.
> _____________
> Roman Shpount