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

Peter Thatcher <pthatcher@google.com> Wed, 19 June 2013 18:13 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 993E621F9E80 for <rtcweb@ietfa.amsl.com>; Wed, 19 Jun 2013 11:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.883
X-Spam-Level:
X-Spam-Status: No, score=-1.883 tagged_above=-999 required=5 tests=[AWL=0.094, 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 ifXxklSHTYX7 for <rtcweb@ietfa.amsl.com>; Wed, 19 Jun 2013 11:13:59 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E3BD121F9E6C for <rtcweb@ietf.org>; Wed, 19 Jun 2013 11:13:58 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc8so5341905pbc.18 for <rtcweb@ietf.org>; Wed, 19 Jun 2013 11:13:58 -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=ShZelHW2M/F4uP19Nn7+kykuI6tPQizkq8feLJFXCtQ=; b=G+7VwLtgPs2bMRTGXweejR10qRLXgnZ5WtZj+mv/GcwNh0IZJV+8rerOqO0uLyg5Gq nnSDwwcjJdW2gzUZF/l4W5khKbbhf3ACrxuIhD/mmnY0XT+mDxiJX/U8M1uZxPbHG1VA qmREiIuPGMb2b69gr1zIkRSiF9NlOf+hQP1uqBUiUIv/6YnD7iXLhPC5wd80D7C9rinc 2f3ZFJmFaXu/i9DPVxc369Ety4lthefTStq/704cxxSLXlyz7IvKqx1r1VxZHry65wyb 9aRZNKNWByNoDNjR+aDpeGKG8fUSuif/8MO7CmJdsNtuCnSof5wobZy23Qo5ew+5I8L5 Ku7Q==
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=ShZelHW2M/F4uP19Nn7+kykuI6tPQizkq8feLJFXCtQ=; b=WmFp0xV/BgL6GXktDQZlruxN8ddenFq5Fob9i/35LqZKlYo7SZhVQj5pgCPVs+pxUD PTPleAib6hU6w8YV7Rhgz6GPu/408XbjqaBcPLsb0q43AZBdhBEfw2u0FbW78RkRiGdP sgrynCO9orH4V3Dr6yiD/IGiKS5ous8goakUB+4AbrMCaiYjSnXda2Oo1vxBvQxKrE42 NvY0Gig9hAsWHX5Hag4Qojo/JNH9HGUiaW2KYrYJtY033jo9bgCmBPv8lAN8EeQ4RZAC P1pVgDU9tw4wCmYR+SOgz3DD91X8cFtSwDrNQdaflVDW2dIWXZVmNH0GzRIkChr5SSZM iesg==
X-Received: by 10.66.83.7 with SMTP id m7mr8001486pay.150.1371665638643; Wed, 19 Jun 2013 11:13:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.88.8 with HTTP; Wed, 19 Jun 2013 11:13:18 -0700 (PDT)
In-Reply-To: <CAD5OKxsN4+onxmj-sRMq0GedrnNNWzwkSz+V5y2vxOKSgMUuXw@mail.gmail.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CAHp8n2m4VwkpbdGE+q73qqij5RDCB4Vb-Ui1LmGSx1zmv8TX2g@mail.gmail.com> <CAJrXDUEfdsZJBgkcb=MJnxRmk9ZMTHw39DE=YWa+ngXxvfsQ0A@mail.gmail.com> <51C1D55D.6040905@hookflash.com> <CAJrXDUEcmWDhJ_3sq9W_VS=KvS3TxB1uPMBBm1W5GoPs=PrpMQ@mail.gmail.com> <CAD5OKxsN4+onxmj-sRMq0GedrnNNWzwkSz+V5y2vxOKSgMUuXw@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 19 Jun 2013 11:13:18 -0700
Message-ID: <CAJrXDUF-LmyPo=uoAeV5Cnik=ZwkU9Gck=fN0PHeL2ro2Xin4g@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Content-Type: multipart/alternative; boundary=f46d042ef48d24784504df85cb1a
X-Gm-Message-State: ALoCoQkrPO9g+4H69Mh3MdGtO096x/0JL06cNazvC/amplKGD9toFW3qBGtL3zOxbuUHUmFtcUDMiq7HnoGiVYn3Cy+HKLcKwrY/IFYVEzr5aF05qJclQ3A5OipqnkfpTFno072OqJDk1EP0YCDzY8Hi6qPXpVV2SSMeUbBuK1nsv++2Jb5xgug3g/vXViFMfjyBk52Jft5d
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: Wed, 19 Jun 2013 18:13:59 -0000

On Wed, Jun 19, 2013 at 10:17 AM, Roman Shpount <roman@telurix.com>; wrote:

>
> On Wed, Jun 19, 2013 at 1:01 PM, Peter Thatcher <pthatcher@google.com>wrote:
>
>> There are two separate things here: 1.  adding to the current API to
>> allow JS to avoid SDP.  2.  removing what is there that uses SDP.
>>
>> You're saying you want to add new things and remove olds things.  But I
>> think really you just want to add what you want, and it would matter if
>> what you didn't want to use were still there.  So I think it's better to
>> talk about what we can add to the API to make it easier to work with rather
>> than talk about starting from scratch.  Removing the existing pieces would
>> not be nearly as easy as you make it sound.
>>
>>
> Let me approach this from a different angle: Do you think it is possible
> to create an interoperable, re-implementable API based on SDP? Currently,
> SDP format changes with each release in a way that breaks both SDP mungling
> code and external connected end-points. What I want is an API that does not
> rely on a string blog to encapsulate every new feature. New features should
> be implemented via new methods. I need something standard enough that I can
> have a stable application implementation. As it stands right now WebRTC
> will not pass the W3C standard process, so we need either spend a lot more
> time tying down SDP or create the API that avoids it. I think you
>  underestimate the amount of effort needed to finalize SDP. At the current
> rate I see this  process taking another 2-3 years. It also creates a
> dependency on MMUSIC, which has its own priorities. So, if you want a
> realistic API standard, you need to look for a way around SDP.
>

I think an API that allows JS to not have to do SDP munging it much better.
 That's why I proposed a step in that direction.


>
> Also, using SDP just for transport is wasteful. All you need are 3 string
> parameters which can be passed individually without parsing/creating a
> string blog which carries another 5 things that carry no meaning for
> transport (version, origin, etc).
>

Agreed.  I'd rather not have it, but I'm trying to make incremental
improvements here.   I don't want to blow up everything and start from
scratch.


>  _____________
> Roman Shpount
>
>