This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25533 - WebRTC spec should explicitly specify the state transition for cancelled offers.
Summary: WebRTC spec should explicitly specify the state transition for cancelled offers.
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: ekr
QA Contact:
URL:
Whiteboard:
Keywords:
: 26364 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-05-02 08:44 UTC by Kiran
Modified: 2014-12-15 10:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Kiran 2014-05-02 08:44:18 UTC 
Considering the following use-case

An offerer creates and offer, set it in browser through setLocalDescription. The signaling state transits from stable to have-local-offer. Now application cancels this offer before receiving the answer from remote peer.

In this scenario, spec should specify that the browser state should be rolled-back to previous stable state.
Comment 1 Harald Alvestrand 2014-10-31 16:47:18 UTC 
Rollback is speciified in JSEP, needs to be added to API.
Comment 2 Harald Alvestrand 2014-10-31 18:25:07 UTC 
*** Bug 26364 has been marked as a duplicate of this bug. ***
Comment 3 Dominique Hazael-Massieux 2014-12-15 10:39:23 UTC 
WebRTC API bugs have been moved to github issues: https://github.com/w3c/webrtc-pc/issues

Please subscribe to the issues you want to keep watching.