Re: "mediadiscarded" and "unassignedmediaarriving" - action needed if we want them

I understand Martin's PR for mediadiscarded, which roughly parallels the RtpUnhandled event from ORTC. 

In both specs, the solution is to obtain an RtpReceiver to handle the discarded or unhandled stream. 

For 1.0, is the idea to have another way to create RtpReceivers, other than vending them?

> On Aug 20, 2015, at 22:01, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> wrote:
> 
> Hi all,
> 
> a long time ago a PR adding a "mediadiscarded" event was submitted [1]. 
> The purpose was to inform the application that (perhaps due to an SDP 
> offer or answer not having arrived) media that the UA can't associate 
> with an existing track (or RTPreceiver) is arriving (and being dropped 
> on the floor).
> 
> That PR was in line with what was discussed at the 2014 TPAC.
> 
> However, there were some later (private) discussion of adding another 
> event that allowed the app to instruct the UA to create a track (and 
> RTPreceiver) for the incoming media. I called that event 
> "unassignedmediaarriving" in the subject line. To my understanding 
> Firefox is even implementing something like this.
> 
> There is currently no PR that addresses "unassignedmediaarriving", or 
> how "mediadiscarded" and "unassignedmediaarriving" should relate. As 
> we've said that for a feature to be part of 1.0 a (relatively baked) PR 
> should exist before the Seattle f2f meeting we're asking people who want 
> this to start working on such a PR.
> 
> Stefan for the chairs
> 
> 
> [1] https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fw3c%2fwebrtc-pc%2fpull%2f29&data=01%7c01%7cBernard.Aboba%40microsoft.com%7cb04204aad59e43bfe46108d2a9e59bdc%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=jnKTgC2o4ozP618ohvpWTkoRxWWmRKp%2f22mF4Fg6bn8%3d
>

Received on Friday, 21 August 2015 05:39:20 UTC