[rtcweb] Separating stream manipulation from the SDP loudness (Re: Proposed Plan for Usage of SDP and RTP)

[Harald Alvestrand <[e-mail]>]

As usual, I'm trying to use subject line change in order to achieve some 
separation of concerns...

On 03/07/2013 10:22 PM, Silvia Pfeiffer wrote:
> Agreed, but it's also not sufficient. SDP is not "programmer friendly" 
> enough because it has too many details that are protocol-details only 
> and it's too hard to see the semantic bits in SDP and ignore the rest.
>
> For example: the programmer wants to say - I want to get this video 
> resolution, this audio bitrate & channels, I want to use this camera 
> and this microphone for this call. Having to manipulate SDP directly 
> for this is a programmer's nightmare.

I think we've been over exactly those pieces, and our current proposed 
solution is called the Media Stream API and the constraints mechanism - 
and they have exactly nothing to do with SDP, or even with PeerConnection.

I don't think we've got it to be "unproblematic" yet, but also, I don't 
think SDP, JSON or even the offer-answer model is either the problem or 
the solution on this set of functionalities.

Or did I misunderstand something basic?

                Harald