Re: Summary of replace track status

On 22/05/15 16:15, Peter Thatcher wrote:
[...]
>
>     * Detection/reporting of that negotiation would be needed: as said
>     above, there seem to be consensus of that if the new track (provided by
>     replaceTrack) would require a re-negotiation, replaceTrack should fail.
>     How quickly can this be detected? How should it be reported back to the
>     application?
>
>
> ​I don't recall of the top of my head any situation in which
> replaceTrack could trigger a renegotiation.  Perhaps if we had some
> scenarios were we thought that might come up, we could know how long it
> would take to detect.  Does anyone have any concrete examples?

I agree, some concrete examples here would be helpful.