Re: [rtcweb] Low Level Javascript API Proposal avail on the webrtc list

[Saul Ibarra Corretge <[e-mail]>]

On Oct 7, 2011, at 12:11 AM, Colin Perkins wrote:

> On 5 Oct 2011, at 18:20, Roman Shpount wrote:
>> On Wed, Oct 5, 2011 at 7:00 AM, Neil Stratford <[e-mail]> wrote:
>> I'm not sure I understand why this is such a problem. XMPP/Jingle defines it's own mapping, which is a common VoIP protocol that is widely supported. I'd much rather that the JS API is as expressive as possible in codec specific matters - for example even to the point of providing callbacks to the JS on certain codec level events, such as decoding a DTMF digit.
>>  
>> What we need is some way to expose all possible codec parameter combinations to JavaScript API. MMUSIC/PAYLOAD specifications for codec typically define CODEC parameters and how they are encoded in SDP/MIME content type, but they fall short of defining a way to list all the capabilities.
> 
> I'm not convinced that exposing all possible codec parameter combinations is an appropriate goal. There is simply too much flexibility present with many of the codecs, especially in combination, for the signalling to be reasonable if all the flexibility is exposed. Better, I think, for the browser to expose a set of known-reasonable combinations, and parameter ranges, from which the most appropriate choice is picked.

Maybe capabilities could be expressed in terms of "codecs" and "profiles". A profile is a set of properties attached to a codec under a given name, lets say codec H264 with "HD" profile or "SD" profile. Having the ability to make a custom profile would be nice, for those who need/want to have a more fine grained control over it.

-- 
Saúl Ibarra Corretgé
AG Projects