Re: [rtcweb] State of the Forking discussion

I thought we were asked to answer Magnus's questions - not to argue each others answers :)

Regards,

Christer 

> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: 3. marraskuuta 2011 15:03
> To: Iñaki Baz Castillo
> Cc: rtcweb@ietf.org
> Subject: Re: [rtcweb] State of the Forking discussion
> 
> 
> On Nov 3, 2011, at 8:27 AM, Iñaki Baz Castillo wrote:
> 
> > Right. But note however that most of the SIP devices just choose a 
> > single media session and render that to the human (regardless there 
> > could be N sessions due to multiple 18X with different Totag and 
> > SDPs). So I don't consider this a very important limitation as the 
> > very same occurs in 99% of SIP phones.
> > 
> 
> Yes but what's cool is that browsers are a platform type that 
> could actually render two streams at the same time: per the 
> current requirements, the browser can mix incoming audio 
> streams and display separate videos, and send out the same 
> audio/video to multiple peers - so parallel forking could 
> actually really work well for in WebRTC as compared to SIP.  :)
> 
> But anyway as we keep saying, we don't need native forking 
> ability in the browser for WebRTC's sake, since it can all be 
> done with app code - the main benefit to having it is to 
> federate/interop with SIP more easily/sanely.
> 
> How hard is it to put in the browsers?  Has W3C given any 
> input on this?
> 
> -hadriel
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>