Re: [rtcweb] JSEP-04: Some comments on Section 5.2.1. and 5.2.2 (19th september)

[Christer Holmberg <[e-mail]>]

Hi,

>>>> Section 5.2.2:
>>>> -----------------
>>>>
>>>>
>>>> Q_5:      Offer when in "local-offer"
>>>>
>>>> The text says:
>>>>
>>>> "If the initial offer was applied using setLocalDescription, but an
>>>>                answer from the remote side has not yet been applied, meaning the
>>>>                PeerConnection is still in the "local-offer" state, the steps for
>>>>                generating an initial offer should be followed,"
>>>>
>>>> I don't understand this. Why would you create a new Offer while you are waiting for an Answer to the previously sent Offer?
>>
>>

>>> Justin has asked for this in the case when the offer has not been sent to anyone else. This is not going to be useful for typical systems trying to have SIP or Jingle compatible flow but who knows ...
>>
>> Again, we have consensus to base JSEP on 3264. And, if we are going to deviate from 3264, I'd like to have some discussion and justification for that.
>
>

> We have been through this many times before.
>
> The state machine that has been in the JSEP document for a while clearly shows that local-offer->local-offer state transitions are permitted.

If we've been through this many times, I must have missed, or forgotten, each time :) Well, that can happen, so feel free to send me a link to a discussion/decission on this.

But, still, whatever deviations we agree to make to 3264, I would like to have it clearly documented - with justification.

In this case, I would also want to have it documented that the previous Offer is "cancelled", and that any associated pranswer/answer etc only applies to the latest offer.

Regards,

Christer