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

Peter Thatcher <pthatcher@google.com> Tue, 18 June 2013 05:31 UTC

Return-Path: <pthatcher@google.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 797C621F9C12 for <rtcweb@ietfa.amsl.com>; Mon, 17 Jun 2013 22:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nf3iwDoN0bDm for <rtcweb@ietfa.amsl.com>; Mon, 17 Jun 2013 22:31:26 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id DDE2721F880F for <rtcweb@ietf.org>; Mon, 17 Jun 2013 22:31:26 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so3528567pbb.14 for <rtcweb@ietf.org>; Mon, 17 Jun 2013 22:31:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FL/thb/4yoiTVKyPcgsX8d4TM0lpvK5VAYTJTsHem74=; b=n+z+ltlxZPy5HcOKdBP9qzdkzeTrkX/dAGQK7IGP9qOmd+43SmOnbI4zjra5m8mA9p IFZtwda/j8TzuP1s9cIFcrSuQYgPNOPNgU7tdssJFs8LVcpbmUz2lzNn1XYuhb3KbIZx /WJnKlHDxNiDgPqXu/NGuqJN4QvZnJed3F8DJPPs5oIK1b4opLXjaAxFsI54ijzT0vJo Lz3ci0Q98doF5MB93P/FFH9BgDn3QhHHiEI59FbdLF7yAV3+TTOINN/j5rWGpiAEx5Ml BIZWTRM/yIgaNGYt+j9t+ahVwx4K5v3a1kWH4ZmUMzLDpEbNAvfsLDO5dA5s8RK3Y0Gt ZtTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=FL/thb/4yoiTVKyPcgsX8d4TM0lpvK5VAYTJTsHem74=; b=PxF+797IQ62+ghZnSugHCKQmF/aJJfV9K7/nEHkoiSgW9dYfAPbsDLoc3S0otHf6iX JmLk7gTw86isL7maoA61kR09QqbT4sQyO9TFRzHp3Y3e0fqbRTDs7DHUtLi5TKBAFw8v tcKAVkzvqfeAcoDyuQ3AYFJbWILOXg8bk8t9KRgeqgM1zB3Y01zySutNprwzV9qmwbYD tb3jNSoNw2Ri+nDyG8RKADYZhwImqd9N07xont+DHkfcXrtZnSsuJogpARqPzKA0xNUJ Eisfrs4lhawSmwEPvpqTMfEH3cWPtskuOvykY0DN2C759Z6rWrBg6xTsRr/I0B8la5RW Vyqg==
X-Received: by 10.66.164.161 with SMTP id yr1mr706043pab.77.1371533486599; Mon, 17 Jun 2013 22:31:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.88.8 with HTTP; Mon, 17 Jun 2013 22:30:46 -0700 (PDT)
In-Reply-To: <CABkgnnUueg6A3RSixn4uUePa1rXqYRx5f5Ni1P1bC-mo4W=P=A@mail.gmail.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CAHp8n2m4VwkpbdGE+q73qqij5RDCB4Vb-Ui1LmGSx1zmv8TX2g@mail.gmail.com> <51BFCBE9.5070406@hookflash.com> <CABkgnnUueg6A3RSixn4uUePa1rXqYRx5f5Ni1P1bC-mo4W=P=A@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 17 Jun 2013 22:30:46 -0700
Message-ID: <CAJrXDUGBCi5X8Y1veD2CYOmUszvUwF4ULFhaTe7oi2conByWeA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacc03044500e04df670648
X-Gm-Message-State: ALoCoQkswJSSfZmTHRyLfA+pDmKHSFNR36onqMpvugZ7nnO+0a9o7cgAp29iVKVn0iRPXVZu6xph2aQDSuX8jlzd+nZnK5Mpx9DOBTBtPMaabN2HAJO9Qw8vsdsTTteCPyE0Lz/tvxhJ9QPo995aHCO3nQXTEUwqd+baMUEB2NcQPD40/gT+Fwz0FZSzM/rgSi3oXjB5he9R
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 05:31:27 -0000

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 <martin.thomson@gmail.com>wrote:

> On 17 June 2013 19:54, Robin Raymond <robin@hookflash.com>; 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
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>