Re: [MMUSIC] ICE-SIP-SDP: Question on ice-pacing attribute

[Roman Shpount <[e-mail]>]

On Wed, Jul 17, 2019 at 6:12 PM Christer Holmberg <
[e-mail]> wrote:

> >> Before I suggest text, my question is: do we allow modifying the pacing
> mid-session?
>
> >
>
> > We should allow modifying pacing attribute mid-session on ICE restart.
> Due to 3PCC, a new end point
>
> > might join the session without the prior knowledge of the negotiated
> pacing value. In order to support this,
>
> > changes in pacing attribute in combination with ICE-restart must be
> supported. Changes of pacing during ICE
>
> > nomination process (i.e. without ICE restart) are extremely hard to
> implement and should be prohibited.
>
>
>
> If there is a subsequent offer/answer while the ICE processing is ongoing,
> and if we do NOT allow modifying the value (without ICE restart), we need
> to say how/of the attribute is included in such offer/answers. Are endpoint
> mandated to include the previously negotiated value?
>

I would assume that the same values for pacing, ice-options, or ice-lite
should be included unless ICE restart was initiated.


> And, what happens if an agent tries to modify the value (again, without
> ICE restart)?
>

Ignoring the change would be the safer option.

Also, when reading Roman’s 3PCC use-case, I assume we need to specify the
> same for the ice-options attribute?
>

I think this should apply to ice-options and ice-lite attributes as well.
Changing these values mid ICE nomination is not well defined and, most
likely, unnecessary.

Best Regards,
_____________
Roman Shpount