[rtcweb] Using PAUSED to trigger API event
Magnus Westerlund <magnus.westerlund@ericsson.com> Thu, 26 July 2012 13:12 UTC
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C55E21F8760 for <rtcweb@ietfa.amsl.com>; Thu, 26 Jul 2012 06:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.194
X-Spam-Level:
X-Spam-Status: No, score=-106.194 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5ECiVLIDyyf for <rtcweb@ietfa.amsl.com>; Thu, 26 Jul 2012 06:12:39 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 31D6F21F875E for <rtcweb@ietf.org>; Thu, 26 Jul 2012 06:12:39 -0700 (PDT)
X-AuditID: c1b4fb25-b7fb66d000003bb6-65-501142450118
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 75.20.15286.54241105; Thu, 26 Jul 2012 15:12:37 +0200 (CEST)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0256.eemea.ericsson.se (153.88.115.97) with Microsoft SMTP Server id 8.3.264.0; Thu, 26 Jul 2012 15:12:37 +0200
Message-ID: <50114244.8070600@ericsson.com>
Date: Thu, 26 Jul 2012 15:12:36 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "public-webrtc@w3.org" <public-webrtc@w3.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBJMWRmVeSWpSXmKPExsUyM+Jvra6rk2CAQe9/dYvej0sYLdb+a2d3 YPJYsuQnk8fReftZA5iiuGxSUnMyy1KL9O0SuDKm3T7HVNAuXDH70GLWBsbr/F2MnBwSAiYS N2Z1MkLYYhIX7q1n62Lk4hASOMUosbu3nR3CWc4osW7lWlaQKl4BbYnJ//8yg9gsAqoSOxtv s4DYbAIWEjd/NLKB2KICgRLfth6HqheUODnzCViNiECkRMfC/2C9wgJaEouuLgWq5wDaLClx +0AKSJhZQE9iytUWRghbXqJ562ywciGgtQ1NHawTGPlnIZk6C0nLLCQtCxiZVzEK5yZm5qSX G+mlFmUmFxfn5+kVp25iBIbewS2/VXcw3jkncohRmoNFSZzXeusefyGB9MSS1OzU1ILUovii 0pzU4kOMTBycUg2MfqZfr3ypW/n7RBjf76y8GL31p5ewxyZ738o2W+v+PT8jw6Hp4USBxc8U 72eqT/ofoKrlsLDBxj4qk+PhVvOuTZvrw/vnbuEoS1ohuuxYhKbb3QvnVh960u+olhOyw2DL qwl3Myr3lN5suHrbgOHSzZY1p8VfHY7c753/ULnP6aisVefGWdPjlFiKMxINtZiLihMBFj4P XQsCAAA=
Subject: [rtcweb] Using PAUSED to trigger API event
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jul 2012 13:12:40 -0000
Hi, (as individual) Bo and I have a proposal in AVTEXT for an RTCP based mechanism for RTP Media stream pause and resume. https://datatracker.ietf.org/doc/draft-westerlund-avtext-rtp-stream-pause/ This will be discussed in the AVTEXT session on Thursday 17.30 in Regency E. The reason I am bring this up for WebRTC is that we think it can actually resolve one potential issue between the media transport protocol and the API. A media sender in RTP can stop sending a media stream at any point in time. This may be the result of a sender side Disable on the media stream track using the API. In the case of centralized media servers it could be that server that stops distributing that media stream based on lack of input or adaptation control. What I believe to be a potential issue is that the media receiving browser will not get any explicit indication that the discontinued transmission happened at the source and was intentional. The reason a receiver isn't receiving a media stream could be that the packets get lost en-route. Thus a question arise in how the receiving browser knows when to trigger the event indicating that mediaStream track has stopped. It can clearly be timer-based but that timer needs to be sufficiently robust to rarely misclassifying transport interruptions from an actual intentional media delivery stop. Thus I propose that this could be improved significantly by having media senders use the PAUSED indication from draft-westerlund-avtext-rtp-stream-pause to indicate to the media receiver that yes, this was an intentional halt in media delivery. Thus enabling a triggering of the event immediately when the last media is being processed/displayed rather than later after some timeout has occurred. Thus greatly improving the applications possibility to remove blank video displays, reconfigure the GUI etc based on the current availability of media streams. Comments and views? Cheers Magnus Westerlund ---------------------------------------------------------------------- Multimedia Technologies, Ericsson Research EAB/TVM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com ----------------------------------------------------------------------
- [rtcweb] Using PAUSED to trigger API event Magnus Westerlund