Re: [rtcweb] SDP Security Descriptions (RFC 4568) and RTCWeb

[Tim Panton <[e-mail]>]

On 26 Apr 2013, at 19:07, Cullen Jennings (fluffy) wrote:

> 
> On Apr 26, 2013, at 7:47 AM, Tim Panton <[e-mail]> wrote:
> 
>> If anyone still thinks that SDP is just a blob not an API surface, take a look at the 'reference implementation' of browser to browser interop.
>> https://code.google.com/p/webrtc-samples/source/browse/trunk/apprtc/index.html
>> 
>> I count around 100 lines of javascript munging the SDP.
> 
> Could you just summarize what the 100 lines do and which theses would be needed for browsers that implemented the drat standards? I'm trying to dig into what we need to fix. 


The bulk of it seems to be there to coerce the browsers to use the 'best' codec. 
I see code to remove CN and re-write the m= line to get opus as the first element.

I think this represents a class of problem where the web programmer will want to assert their 
preferences, and currently SDP munging is the only available API.

I personally doubt that any level of standardisation of the SDP will remove the need for such tweaks.

Tim.