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 20809 - Stream rejection not possible
Summary: Stream rejection not possible
Status: RESOLVED LATER
Alias: None
Product: WebRTC Working Group
Classification: Unclassified
Component: WebRTC API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Adam Bergkvist
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-29 18:10 UTC by Matthew Kaufman
Modified: 2014-12-15 10:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Matthew Kaufman 2013-01-29 18:10:13 UTC 
At the face-to-face meeting in 2012-11, there was a lengthy discussion on how an application might programmatically reject a subset of the RTP streams (i.e. MediaStreamTracks) that arrive on a given RTP session.  There seemed to be consensus that a solution to this problem would be necessary.  There is no specification of this API, nor are there any normative references to documents that describe this API in the current draft.
Comment 1 Harald Alvestrand 2014-10-31 16:00:40 UTC 
The API that is to be used for rejection is MediaStreamTrack.stop() called between ontrack event and CreateAnswer() (according to discussion at TPAC a year ago).

There needs to be an example in the document showing this.
Comment 2 Dominique Hazael-Massieux 2014-12-15 10:39:36 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.