W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2014

Re: RTPSender/Receiver - The case for Constraints

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Sun, 18 May 2014 08:47:50 +0000
To: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>, Bernard Aboba <Bernard.Aboba@microsoft.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1CFFA21D@ESESSMB209.ericsson.se>
On 2014-05-17 00:27, Suhas Nandakumar (snandaku) wrote:

> At the same time, I see a need to apply constraints on
> RTPEncoding(RTPStream) level for the reasons mentioned below
> 1. New constrainable attributes that applies only to the RTP Stream
> such as bandwidth, QOS,  and goes along with the one defined at the
> track level (resolution, framerate).

To me, it would make most sense to focus on those new attributes that 
are tied more to sending a track over the network.

> 2. The cases where we want PC to act as a Media Source Transform so
> that any such transformations via constraints will not impact the
> originating media source and other associated sinks.

We already have the MediaStreamTrack API surface for that. You can 
create several MediaStreamTrack's that use the same source device, and 
apply different constraints to them.

Received on Sunday, 18 May 2014 08:48:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:40 UTC