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

Iñaki Baz Castillo <ibc@aliax.net> Sat, 29 June 2013 06:23 UTC

Return-Path: <ibc@aliax.net>
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 C594921F9983 for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 23:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level:
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 RECqn4yWzC3a for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 23:23:29 -0700 (PDT)
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) by ietfa.amsl.com (Postfix) with ESMTP id 201D721F9957 for <rtcweb@ietf.org>; Fri, 28 Jun 2013 23:23:22 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id g10so1067170qah.12 for <rtcweb@ietf.org>; Fri, 28 Jun 2013 23:23:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=JikkJU+TCMy8Vs232rdPiFXcpYrkrTmGTyHT4U4G8Js=; b=KGyaX+et+1uOC4Y/+wi08XO9M/1I6QV2KBBW2nrSr6ll6miUODliy9VNvsw7L5hjq1 Dkx/YfvCNA7R1C6qDA557wTb+PqQVouIgZa5ktZOD6R3kSEwJM4RKtUb2s4VF+E8wHJd NoS029bA/e8BMPttIjknyXbsBhHxubEDuSOK32ESxAAOfZwq7c8jAhd4+1BmjnueckZQ GBxi+VWR+nJe8oPM9XitSlb50NFrNd5o9t5cPSlbBpIve4lj5oLuM4F0+8suCzMtBGU4 B3a0d8h+qWLUTvsEp9IJFV0V/fo3h0kib0/rAyceM0l96iAw7j4H+cLNe2wjndWamnbf zh2g==
MIME-Version: 1.0
X-Received: by 10.49.61.167 with SMTP id q7mr20750437qer.80.1372487001602; Fri, 28 Jun 2013 23:23:21 -0700 (PDT)
Received: by 10.49.72.132 with HTTP; Fri, 28 Jun 2013 23:23:21 -0700 (PDT)
Received: by 10.49.72.132 with HTTP; Fri, 28 Jun 2013 23:23:21 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1135B686C@xmb-aln-x02.cisco.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CAHp8n2m4VwkpbdGE+q73qqij5RDCB4Vb-Ui1LmGSx1zmv8TX2g@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1135B686C@xmb-aln-x02.cisco.com>
Date: Sat, 29 Jun 2013 08:23:21 +0200
Message-ID: <CALiegf=YjQoAen+u-7wZbxK-r=0ChqdtQCJo58aJJvoBPQ5ZXQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Cullen Jennings <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bdc9fba30928304e04508d2
X-Gm-Message-State: ALoCoQmz1QNbxNqb257U0i8CBC00o8PUtytuAugminoDKBc5r8dLirLdFbiB9sleyAKz2Q3JoFN9
Cc: 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: Sat, 29 Jun 2013 06:23:33 -0000

Cullen, do you think that W3C would ever design a JS API that forces the
developer to deal with an unmanageable blob string? Can somebody point me
to an existing similar "API" in HTML5?

The problem is that telcos are much more used to IETF processes than Web
people and hence this WG is dominated by telcos proposing their first API
for the W3C, an API to satisfy their existing business model (the webphone).

It is time to leave Web experts to design a really useful API for WebRTC.

--
Iñaki Baz Castillo
<ibc@aliax.net>;
El 29/06/2013 00:29, "Cullen Jennings (fluffy)" <fluffy@cisco.com>; escribió:

>
> On Jun 17, 2013, at 6:00 PM, Silvia Pfeiffer <silviapfeiffer1@gmail.com>;
> wrote:
>
> > Having hit my
> > head hard against the limitations of the current WebRTC API and being
> > forced to learn SDP to achieve some of the less common use cases, I'm
> > feeling the pain.
>
> Could you let us know the use cases of what it is you need an easy way to
> do ?
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>