Re: Transport related API need

On 2013-08-08 19:31, Roman Shpount wrote:
> I should be able to specify which codecs are present and their codec
> preference order (I want H.264 if supported by the browser instead of
> VP8, if I know that remote party supports both but will need to
> transcode VP8).

In my ignorance, I thought SDP O/A did sort out which codec to use 
really well. Isn't this handled by the other endpoint, in a response, 
only says H.264, or puts H.264 before VP8 (if both were offered)?

> This should also include ability to specify the same
> codec multiple times with different parameters (for instance iLBC with
> two different payloads for mode=20 and mode=30).

What parameters do you have in mind? And what use case are solved? And I 
assume that you can only have one set of parameters for one 
MediaStreamTrack (to be sent).

>
> I should be able to control ptime and maxptime (including getting rid of
> ptime all together) per m-line.

Could this (from an application point of view) be expressed in terms 
like "low delay"?

> _____________
> Roman Shpount
>
>
> On Thu, Aug 8, 2013 at 9:54 AM, Stefan Håkansson LK
> <stefan.lk.hakansson@ericsson.com
> <mailto:stefan.lk.hakansson@ericsson.com>> wrote:
>
>     Hi,
>
>     some time back we issued a call for input on things there is a desire to
>     be able to control (without SDP mangling) [1]. We asked for input on
>     "why", "what" and "how".
>
>     I just went through the "what" part of the responses, and compiled the
>     list at [2]. Is there anything I missed?
>
>     (Note, there were also input saying that this can't be discussed until
>     the SDP is defined, and other input saying SDP should go away - but I
>     think having this list is valuable anyway)
>
>     Stefan
>
>
>
>     [1] http://lists.w3.org/Archives/Public/public-webrtc/2013Jul/0176.html
>     [2] http://www.w3.org/2011/04/webrtc/wiki/Transport_Control
>
>

Received on Saturday, 10 August 2013 12:38:32 UTC