{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/187","labels_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/187/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/187/comments","events_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/187/events","html_url":"https://github.com/w3c/webrtc-pc/issues/187","id":59146445,"number":187,"title":"How to prevent tracks from being renegotiated after rejection","user":{"login":"martinthomson","id":67641,"avatar_url":"https://avatars.githubusercontent.com/u/67641?v=3","gravatar_id":"","url":"https://api.github.com/users/martinthomson","html_url":"https://github.com/martinthomson","followers_url":"https://api.github.com/users/martinthomson/followers","following_url":"https://api.github.com/users/martinthomson/following{/other_user}","gists_url":"https://api.github.com/users/martinthomson/gists{/gist_id}","starred_url":"https://api.github.com/users/martinthomson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/martinthomson/subscriptions","organizations_url":"https://api.github.com/users/martinthomson/orgs","repos_url":"https://api.github.com/users/martinthomson/repos","events_url":"https://api.github.com/users/martinthomson/events{/privacy}","received_events_url":"https://api.github.com/users/martinthomson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-02-26T21:27:38Z","updated_at":"2015-02-27T18:39:44Z","closed_at":null,"body":"Situation:\r\n\r\n1. A adds a track and sends an offer.\r\n2. B applies the offer, but rejects the track (calls .stop() on it).\r\n3. A receives the answer and doesn't send the track.\r\n4. A creates a second offer.\r\n\r\nAs currently specified, the second offer will include the rejected track.\r\n\r\n@juberti suggests that we mark the corresponding RtpSender (maybe it can have a `rejected` property).\r\n\r\nAlso to consider: what if A *wants* to include the track in the second offer?  Should it be forced to remove the dead track and re-add it?  Maybe the `rejected` property can be made mutable, so that it can be set back to false."},"comment":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/comments/76447743","html_url":"https://github.com/w3c/webrtc-pc/issues/187#issuecomment-76447743","issue_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/187","id":76447743,"user":{"login":"juberti","id":1821693,"avatar_url":"https://avatars.githubusercontent.com/u/1821693?v=3","gravatar_id":"","url":"https://api.github.com/users/juberti","html_url":"https://github.com/juberti","followers_url":"https://api.github.com/users/juberti/followers","following_url":"https://api.github.com/users/juberti/following{/other_user}","gists_url":"https://api.github.com/users/juberti/gists{/gist_id}","starred_url":"https://api.github.com/users/juberti/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/juberti/subscriptions","organizations_url":"https://api.github.com/users/juberti/orgs","repos_url":"https://api.github.com/users/juberti/repos","events_url":"https://api.github.com/users/juberti/events{/privacy}","received_events_url":"https://api.github.com/users/juberti/received_events","type":"User","site_admin":false},"created_at":"2015-02-27T18:39:44Z","updated_at":"2015-02-27T18:39:44Z","body":"Senders don't have any states at the moment, but this sounds similar to what Martin/I mentioned above.\r\nI prefer 'closed'/'ended' to 'rejected'. I also think readding makes more sense than making the closed state mutable."}}