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

Peter Thatcher <pthatcher@google.com> Wed, 03 July 2013 19:34 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 5BC5B21F9D24 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 12:34:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[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 lxTWYc3vWCmj for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 12:34:44 -0700 (PDT)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 98FEE21F9B42 for <rtcweb@ietf.org>; Wed, 3 Jul 2013 12:34:44 -0700 (PDT)
Received: by mail-vc0-f174.google.com with SMTP id kw10so389391vcb.19 for <rtcweb@ietf.org>; Wed, 03 Jul 2013 12:34:43 -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=XCwtbpE4nr/MfYfnZ1t+7rLCJXCwJfhlZImMP7fGJ7s=; b=bAU2d3eEuMZdYxJVg9zMHBUGDsZcMvSrtqfdVsUOzsaDlG4SXjpb9l6U609byqoq+M ql7Xl4aOOcpTZ4c4nY7IHYrWRKfmDYi4lCV4WyhwFbbUbf+aLypbYJvwRTQKFptwe9UD rLfTbGAlxqsNjFx2izAbCMDVbSu4mg1X75P60Aybzf6/kh3Wo/j6QywVkFDJhN9W7hZ1 dONzu5upBPT0N9LzHgiRNmExysgChowbyCBrWkOkTOrMWiP7i+LJYe2sZYdYagi0kgKs MwsCsymNWc3QO9eSqjVzk5C2oCRb0jzk6E4RRxUHPmdlksJ4wnR4vvI9tJr5TSCGLJvk 9SEg==
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=XCwtbpE4nr/MfYfnZ1t+7rLCJXCwJfhlZImMP7fGJ7s=; b=k8RzvRNIZgqrGmj8Svz/x9NeSFiDG0+dYeijJgZdWEnex+04zIHqrKVYgrfLK7t9Cf VGmqG4ezNWPU0HV7aM51lx1NEtx1+LepXAvxN/8yEI6AZjBsVR3b7isuSQW5Gb2uGPRl oP+d67hkFo5i7aGnP+WEwKCxXNHV/Mf24aEvgnT8glXK0Wk9YYR4ITy32naUJsqmsae7 xm3O6BilWZqRF2VocLATJELVrSvO2hpTPXV8MksS1MlpT91OiTsBaSX6Z35SUljVF8pp /K5EBmbvuAGhElcZ+yDaolTUgRUYGCP+4Zq0HfgDW9FNf2gH2tpHzgY9e2ItJtslvWeB weHg==
X-Received: by 10.58.207.195 with SMTP id ly3mr709650vec.77.1372880083848; Wed, 03 Jul 2013 12:34:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.59.71 with HTTP; Wed, 3 Jul 2013 12:34:02 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1135C22D6@xmb-aln-x02.cisco.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CAHp8n2m4VwkpbdGE+q73qqij5RDCB4Vb-Ui1LmGSx1zmv8TX2g@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135B686C@xmb-aln-x02.cisco.com> <CALiegf=YjQoAen+u-7wZbxK-r=0ChqdtQCJo58aJJvoBPQ5ZXQ@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135B7AEE@xmb-aln-x02.cisco.com> <51CFA5D6.201@hookflash.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135C22D6@xmb-aln-x02.cisco.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 3 Jul 2013 12:34:02 -0700
Message-ID: <CAJrXDUFSrJ3-v5ZbXydr=TaMLqBbUZbv42A6F_OxHSnmdeTkyA@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b6d8d7cb7ac6a04e0a08d4d
X-Gm-Message-State: ALoCoQljBXUJmmPckphe5VruCrfpGC9ndIxD/7j2jGyooAdPeCfsstQABhOR8jUFPaA2Yey1rG0mH5AJUxLk7NhIbcC5cSfFS2v92B7Go9FMvea9Xas/ZxaYHX2Q1PHpUkhrTIT2HhKWmazLBTN1XjyMq0i3U4CxwxfqmfCKeXgkfWdvR2wOA0ySVg8HDK+t6jB5NZ8QAN7F
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, 03 Jul 2013 19:34:45 -0000

We already have some in the spreadsheet that I previously linked (
https://docs.google.com/spreadsheet/ccc?key=0AuaKXw3SkHMSdHlZdV9RN0xSWFhybVl4anJLRkVPV0E#gid=0
)

Wolfgang Beck: Muting a call
Lance Stout: Jingle signalling
Gustavo García: Set "inactive", control crypto, modifying codecs, modifying
bitrate,
Philipp Hancke: Jingle signalling
Alexandre Gouaillard: Knowing the codec list, the tranport details, the
bandwidth options, which ice candidates are used or failing
Roman Shpount: Interop between browser SDP and MCU SDP
Silvia : Not trying to mangle SDP yet, but would like to control bandwidth
requests/limitations; bitrate requests; codec settings
Iñaki Baz Castillo: Mangling it, but didn't say for what purpose.


And I could give a very long list of things, but I'll continue to keep
myself disqualified :).




On Wed, Jul 3, 2013 at 12:16 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote:

>
> On Jun 29, 2013, at 8:28 PM, Robin Raymond <robin@hookflash.com>; wrote:
>
> > Versus this SDP blob that many of us must parse/mangle/generate from our
> code if we want to go beyond a basic demo:
>
> My assertion has always been we should avoid any JS app needing to touch
> the SDP. Every example I have heard of why people are doing (with exception
> of one) it is ones that there has been discussion of providing an API to do
> that and/or to fix a bug in browsers. (Just as FYI, the one exception is
> Kaufrman's use of ICE to put things in what is usual done as a MPLS tunnel.
> There are probably other common ways to solve that problem).
>
> I like Peter's idea of trying to capture what are the reason people think
> they need to look at the SDP.
>
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>