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

[Roman Shpount <[e-mail]>]

On Thu, Apr 25, 2019 at 2:17 PM Christer Holmberg <
[e-mail]> wrote:

> >The timer should start when the connectivity checks start by the remote
> ICE agent. The timer is needed to make sure local candidate addresses
> continue
>
> >to accept STUN binding requests for at least some minimal time, so
> technically timer should start from the time remote ICE agent was informed
> about
>
> >candidate addresses and started connectivity checks. There is some
> signaling delay involved here, so it needs to accounted by the timer value.
>
>
>
> An agent doesn’t know when the peer agent will start - especially not the
> offerer. If it sends an INVITE with its candidates, it may take a while
> before the INVITE even reaches the peer agent, due to network services,
> call forwarding etc etc etc.
>
>
>
This was actually one of the issues raised related to the timer start. The
offerer can start the timer when it got the first remote candidate or end
of candidates notification. Answerer is trickier, since there is no
signaling indication when offerer actually got the answer. This is why I
was thinking that an extra signaling message (
https://github.com/cdh4u/draft-ice-pac/issues/11), indicating end of
sending candidate checks might work better then a timer.
_____________
Roman Shpount