25360 2014-04-16 04:15:25 +0000 MediaStreamTrack should not be considered as ended just because remote peer stopped sending data. 2014-05-08 08:09:58 +0000 1 1 1 Unclassified WebRTC Working Group Media Capture and Streams unspecified All All RESOLVED FIXED P2 normal --- 1 kiran.guduru public-media-capture adam.bergkvist public-media-capture stefan.lk.hakansson oldest_to_newest 103933 0 kiran.guduru 2014-04-16 04:15:25 +0000 In section 10. Event Summary [1], non-normative section, it was specified for ended event that, ended event can be fired "because the remote peer stopped sending data". But there are chances for remote peer to temporarily stop sending data as below. When the user put remote peer on HOLD, the SDP will be negotiated with sendonly and recvonly in offer and answer respectively [2, 3]. In this scenario, remote peer will temporarily stop sending data until the time it is put to UNHOLD (offer, answer with sendrecv). So MediaStreamTrack should not be considered as ended just because remote peer stopped sending data. [1] http://www.w3.org/TR/mediacapture-streams/#event-summary [2] http://tools.ietf.org/html/draft-nandakumar-rtcweb-sdp-04#page-19 [3] http://tools.ietf.org/html/rfc3264#page-17 103941 1 adam.bergkvist 2014-04-16 08:04:43 +0000 If the other peer temporarily stops sending data then the track should be considered muted. That means that the source isn't producing any data at the moment. 103943 2 kiran.guduru 2014-04-16 08:16:31 +0000 (In reply to Adam Bergkvist from comment #1) > If the other peer temporarily stops sending data then the track should be > considered muted. That means that the source isn't producing any data at the > moment. It seems, perhaps, this comment should be apt for Bug 25360. 103944 3 kiran.guduru 2014-04-16 08:17:24 +0000 (In reply to Kiran from comment #2) > (In reply to Adam Bergkvist from comment #1) > > If the other peer temporarily stops sending data then the track should be > > considered muted. That means that the source isn't producing any data at the > > moment. > > It seems, perhaps, this comment should be apt for Bug 25360. Sorry for the typo, it should be Bug 25361. 103946 4 kiran.guduru 2014-04-16 08:21:40 +0000 This can be solved by modifying the prhase from "because the remote peer stopped sending data" to "because the remote peer permanently stopped sending data". (addition of "permanently" can remove other consequences like hold / unhold etc). 103957 5 adam.bergkvist 2014-04-16 09:34:31 +0000 Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/3d2d504a7b3be24593749555dd251b5256b9da0c 105407 6 stefan.lk.hakansson 2014-05-08 08:09:58 +0000 Fixed in http://dev.w3.org/2011/webrtc/editor/archives/20140507/getusermedia.html