Re: [rtcweb] Review of draft-ietf-rtcweb-stun-consent-freshness-05

[Martin Thomson <[e-mail]>]

On 17 July 2014 18:59, Paul Kyzivat <[e-mail]> wrote:
>    WebRTC devices are required to support full ICE as specified in
>    section 3.4 of [I-D.ietf-rtcweb-transports].  However, when WebRTC
>    devices interwork with other endpoints that support only ICE-lite
>    (e.g. gateways) those endpoints will not generate consent checks, but
>    just respond to consent checks they receive.

Yes, this.

> Section 4.1:
>
>    ...  To prevent expiry of consent, a STUN binding
>    request is sent every N milliseconds, where N SHOULD be 5000
>    milliseconds and MUST be randomized at least 20% above and 20% below
>    that value (to prevent prevent network synchronization).  Using the
>    value 5000 milliseconds and that 20% randomization range, N would be
>    a value between 4000 and 6000.  ...

We've just discussed this particular point and concluded that the
randomization requirement isn't necessary, since there is no need for
any sort of lock step avoidance in a peer-to-peer system like this.