Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

[Roman Shpount <[e-mail]>]

On Mon, Jun 17, 2013 at 5:56 PM, Iñaki Baz Castillo <[e-mail]> wrote:

>
> What is the aim of NoPlan? The draft says "This document does not
> question the use of SDP and the Offer/Answer model". Why? It should
> question it since it treats SDP as if it was a silly and unmanageable
> binary blob. It is like "we must live with SDP because it is
> mandatory, but let's try to ignore it as much as possible". If so, why
> don't ignore SDP entirely?
>
> However NoPlan is the best we have if, finally, SDP is mandated in WebRTC.
>
> I think it is time to write two lists:
>
> 1) Advantages of using SDP in WebRTC.


Somebody wrote a bunch of code based on JSEP.


> 2) Dissadvantages of using SPD in WebRTC.


An unmanageable monster was created which currently stays in the way of
developing new functionality (bundle), building applications (does not
provide obvious ways to implement obvious tasks, like adding an extra
stream without re-negotiating all the existing ones) and even interop with
existing SIP endpoints (which was the original but now is complicated since
it would require a non trivial set of constraints and subsequent SDP
manipulation).
_____________
Roman Shpount