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

[Silvia Pfeiffer <[e-mail]>]

What are the special scenarios?
(Noting that this is likely the wrong list for this topic...)
Silvia.

On Mon, Mar 11, 2013 at 9:59 AM, Suhas Nandakumar <[e-mail]>wrote:

> I agree .,. JS developer need not have to touch SDP unless it is required
> , which I feel might be needed for few special scenarios.
> Constraints, Medie Stream Apis, media capture Apis and Peer Connection
> Apis should be able to support majority of use cases without JS developer
> needing to manipulate SDP directly.
>
> 2 cents
>
> Cheers
> Suhas
>
>
> On Sunday, March 10, 2013, Silvia Pfeiffer wrote:
>
>> On Sun, Mar 10, 2013 at 3:04 AM, Harald Alvestrand <[e-mail]>wrote:
>>
>>> 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.
>>>
>>
>> TBH I just hadn't seen
>> https://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/proposals/SettingsAPI_proposal_v6.html. Is it implemented anywhere yet?
>>
>> Now that I've looked at it, I wonder how that interacts with the SDP
>> created through createOffer(). If indeed the JS programmer never has to
>> touch the SDP, I don't see a need to expose it in the API at all, i.e.
>> setLocalDescription() should not be necessary.
>>
>> Silvia.
>>
>>