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

[Peter Thatcher <[e-mail]>]

As I mentioned in the previous email, I think O/A is use in two different
ways: transport and streams.  I believe it's mostly painful for adding
streams, and less painful for establishing the transport.  If we allowed
adding streams without O/A, we'd have relieved more than half the pain, or
at least more than half the pain I experience.   And that's just what I'm
proposing we allow with createLocalStream/createRemoteStream.


On Mon, Jun 17, 2013 at 9:01 PM, Martin Thomson <[e-mail]>wrote:

> On 17 June 2013 19:54, Robin Raymond <[e-mail]> wrote:
>
>>
>> On a side note, I agree that SDP should go (and quickly) but it's not the
>> format that's the problem. Granted, it is obtuse. But it's not just that;
>> it's a monolithic do-everything offer/answer model that offers very little
>> control and the API to control the browser's RTC is effectively via
>> manipulation of the SDP. Yuck! Even if it were fancier and prettier JSON,
>> it would still be an ugly do-everything monolithic object with a sketchy
>> offer/answer model that is brittle and offered very little real-scenario
>> controls for those whom need it. It's absolutely horrible and is in good
>> need of quick deprecation.
>
>
> I think that this sums up my views on the subject.  Offer/answer is at the
> heart of this.  SDP is just the ugly wrapper that attracts all the heat.
> SDP isn't so bad if you are doing SAP.  Of course, once you drop O/A, then
> you have to build something else.
>
> I made a start at that, but I caution, this approach was soundly rejected:
> http://lists.w3.org/Archives/Public/public-webrtc/2012Oct/att-0076/realtime-media.html
>
> No matter how right you are, the political reality is that it's not cool
> to raise comment 22.
>
> _______________________________________________
> rtcweb mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>