IETF Logo Mail Archive

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

Peter Thatcher <pthatcher@google.com> Fri, 28 June 2013 23:30 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 77DDC21F9CBF for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 16:30:59 -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 gMyprXI5uLSa for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 16:30:59 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 07CAF21F9CBC for <rtcweb@ietf.org>; Fri, 28 Jun 2013 16:30:58 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so1313305pdi.41 for <rtcweb@ietf.org>; Fri, 28 Jun 2013 16:30: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=XVXD5sA1zilf0k15d/z4dOInRFZIe0cpsqtsfdLiWAU=; b=kmoanubWkeX3WlUYuFJhNV2FCL92ShKJnd1pHnVVQg2us48f5NuMApq4XSPeF6Rn2r CHfVFOiwsU33sQWroIdvYvXFu/IPWjgBsPQbDJjUOhnf718ouOFLIU4aQy+Z1+nkP02x J/6TnuG5ibkI4YJxCd+pODXJ8Lz1l1fI5H4+mXrIrKVlMKc+IpmPX8A0VJEDS/ENiaPd O48Sgu3IMOKtiEXSOhAaO4CdwCipZ6OMYFKNqArb6Rr/ZScZTgeqZhjUGbkIkO0bi8hK lvPpGKEuZOO/3P7ij7kP4jrOaU02WNc3ViKtmzf7fn1m6zbTkt6h64QVxmsWjrhYNPTK W0mQ==
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=XVXD5sA1zilf0k15d/z4dOInRFZIe0cpsqtsfdLiWAU=; b=QLqDJ3o/IzAsiUx127zyV171YTfb/25nYkV8AzyYRdQahbRLShlQfUAsoQR/ssnRF5 kVMLTeedCXVBUd7CYAZd2mniuQjx12R2osULL1Z+Xmh17ScGJw01ur7DF4AO9KdWWsxQ UMNB0LriCDC3anRJ2S2+U5xSwnkivnrha9cE8cz+IdmaGbbiZI3jLYSpQ2nOKlTqD2+L oJFaiW7IcWw3NLBdq5g0aeGclM1K7MUnnQ/14vg+UTqlfPUaa9qk/klpeeTWFNtjntxt lwxNDsJhudlRLsy8KM8n2JDoTmBc8GYR6000M56HwH207UJJIqCya1pSXAmYDcPIlX7r MnPw==
X-Received: by 10.66.162.102 with SMTP id xz6mr13867333pab.0.1372462258632; Fri, 28 Jun 2013 16:30:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.234.71 with HTTP; Fri, 28 Jun 2013 16:30:18 -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>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 28 Jun 2013 16:30:18 -0700
Message-ID: <CAJrXDUHPZwom_0GH0RU6oYYF3vTxzu8yMP+vCTv5Eg5hg1vhTQ@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary="047d7b86e55064dbb904e03f45bc"
X-Gm-Message-State: ALoCoQnx8S/iuzBnbVlMDXgGNMalvucS8pgImwe7LY30Wb8DBtyhvvFBL2tVaZPEbAD/lK+bXLbrEbC/P9siJCVxAMEppiZ34VBlORQX/1yQ4nXWUyVJxwjHnRp3VHclgtouzVoCrPmntMXjbokPFKLnuAk567z6zRhi/v/V2E7PQxKen2zstEz7386/iEkiVCid0mvO5ecz
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: Fri, 28 Jun 2013 23:30:59 -0000

FYI, you might find some in this doc:

https://docs.google.com/spreadsheet/ccc?key=0AuaKXw3SkHMSdHlZdV9RN0xSWFhybVl4anJLRkVPV0E#gid=0

About nine developers have listed what they are trying to do and what pain
they are running into, with SDP specifically.  Granted, it's only what can
fit in a single spreadsheet cell, but I'm sure you can ask for further
details if you are interested.  But at least one did mention how well SDP
is working for them, so there's input on both sides.




On Fri, Jun 28, 2013 at 3:28 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote:

>
> 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 ?
>
>

v2.23.0 | Report a Bug | By Email