- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Feb 2019 13:26:18 +0000
- To: public-webrtc-logs@w3.org
> So is the following a (viable? better?) solution? Yes, I think so. I'm working on a blog post about this, how *rollback*, when used properly, should be able to tackle arbitrary remote changes, much like *negotiationneeded* (once Chrome fixes it) tackles arbitrary local changes, for *"perfect negotiation"*. That is: fully abstract away the negotiation process, handling all glare. I just need to prove to myself that it works in all instances, or at least the common ones. If we assume the other peer is sane, then `"have-local-offer"` should be all we need to support rollback of—e.g. if we receive an offer in `"have-remote-pranswer"` then the other side is messing with us, and we just ignore it. An edge-case may be receiving an offer in `have-remote-offer`. Do we take the new one or finish the old one? It would be up to the app how to handle this. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2095#issuecomment-461417758 using your GitHub account
Received on Thursday, 7 February 2019 13:26:20 UTC