Re: [MMUSIC] Fwd: New Version Notification for draft-uberti-mmusic-nombis-00.txt

[Justin Uberti <[e-mail]>]

On Sun, Mar 22, 2015 at 4:56 PM, Christer Holmberg <
[e-mail]> wrote:

> Hi,
>
> > [BA] As noted in Section 3.3:
> >
> >   the controlling endpoint MUST have some way to indicate to the
> >   controlled side that specific candidates are to be kept alive.
> >
> > To achieve this goal, is it necessary to send Binding Requests for each
> candidate pair
> > to be kept alive? This could consume quite a bit of energy, particularly
> if there are multiple
> > candidates on both sides.
>

Sending a few STUN packets doesn't cost appreciable energy, although
powering up the radio does. For most devices, you won't want to maintain
multiple active radios unless you think one might suddenly drop out.


> Don't you need to do that anyway, if you use continuous consent?
>
> Section 4.1 of draft-ietf-rtcweb-stun-consent-freshness-11 says:
>
>         "After a successful ICE connectivity check on a particular
> transport address,
>         consent MUST be maintained following the procedure described in
> this
>         document."
>
> I assume that applies to every valid candidate pair. Or?
>
>
Right, any pair that you might want to switch to will need to maintain
consent.