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

Robin Raymond <robin@hookflash.com> Thu, 27 June 2013 05:17 UTC

Return-Path: <robin@hookflash.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 8B97D21F9BE9 for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.848
X-Spam-Level:
X-Spam-Status: No, score=-3.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 4aDrjrtgCt2V for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:17:03 -0700 (PDT)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id F22B421F9446 for <rtcweb@ietf.org>; Wed, 26 Jun 2013 22:17:02 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id a13so708567iee.34 for <rtcweb@ietf.org>; Wed, 26 Jun 2013 22:17:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:x-gm-message-state; bh=1xL1YeOYGBW8vuLJvXNF16QRbDENz4WxNtJEDUAMcF4=; b=CsD5qaNCWYcsS1u4ZKwAU2v4rlN0i5S28XT52niT5JNvJaM0jEKPa+SsWdgM/jF+2N JPnyYSPPtKQzghzASDazgsp1NVcdxG8yPoUSplThfZ/wes3B3ytFPBno5LkMjmgxN0+Z KAvYNmRWkklMlO2FBft+BwCAe5O24PNWDXs4TGfuTF0McbqIaNWN3Ke6N79TawQhElxS eXXXJF61sEW1yQjPcmtSlJxn21FOJ6EDrIF4ec2BKqzoHoA3w0JuaBb2QUuBeyOtp7OZ abcfKuJGJ0OEf8a0Gv5ZKAdCLwomzV7JriKx5wdKFWfTPKmJjMENivVJlpXvky7PnJ+5 F6Kw==
X-Received: by 10.50.117.72 with SMTP id kc8mr11918842igb.44.1372310221491; Wed, 26 Jun 2013 22:17:01 -0700 (PDT)
Received: from Robins-MacBook-Pro.local (CPE602ad08742f7-CM602ad08742f4.cpe.net.cable.rogers.com. [99.224.116.224]) by mx.google.com with ESMTPSA id ri10sm11628115igc.1.2013.06.26.22.16.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Jun 2013 22:17:00 -0700 (PDT)
Message-ID: <51CBCAC8.7070107@hookflash.com>
Date: Thu, 27 Jun 2013 01:16:56 -0400
From: Robin Raymond <robin@hookflash.com>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: Peter Thatcher <pthatcher@google.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CABkgnnUmRpanfpwryyiCUsOdMLzrd74n-4LXaj_AK3aLe0yQ8Q@mail.gmail.com> <51BF5F00.90705@jitsi.org> <CABkgnnWTvJYG1_HQWz3pZw633rgadeKzx472MTzzFMuq073RgQ@mail.gmail.com> <CALiegfkZcXrNR3CXY--d4ObZMV2z7NEpgdyVHtVtROVtDQsT6A@mail.gmail.com> <CAD5OKxs95gAmYoCr-EB6LaDFW7vaFfpF7=9fu_aCfV=LjwsVpg@mail.gmail.com> <BLU169-W13367E5FDE396829D364D62938C0@phx.gbl> <CAJrXDUEO-prozZPYAm2snfgUXhS5nKRN-ZXWdU1VGfXGnOTAfg@mail.gmail.com> <BLU403-EAS148552B821ED225C03D441D93750@phx.gbl> <CAJrXDUEbD7PuKkwF-oDOZJ-7gWr=GR0sft39t_0_5vDHs9YWOQ@mail.gmail.com>
In-Reply-To: <CAJrXDUEbD7PuKkwF-oDOZJ-7gWr=GR0sft39t_0_5vDHs9YWOQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090008060204030808050901"
X-Gm-Message-State: ALoCoQmEDUpjZSUaQkoh39Flw4DXPHwo8FaOjhkPMhLOGn3p8jDX8XFVbywY/0wwT78AMzxtRYY/
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: Thu, 27 Jun 2013 05:17:07 -0000

True, node.js doesn't have to use the same code in their implementation 
and they are free to deviate from the WebRTC path. But it would be 
highly desirable if they could use the same API as it would ensure a 
greater level of compatibility between client and servers where common 
JS libraries can be used. Plus node JS can be used to produce not just 
server apps but HTML5 based applications, so having a compatible library 
for those kind of applications is valuable too.

-Robin

> Peter Thatcher <mailto:pthatcher@google.com>
> 27 June, 2013 1:01 AM
> If Node.js wants a cleaner API, it's can certainly create one.  It's 
> not at all constrained by what goes in the browser or what the WGs 
> decide.  In fact, that would be an interesting way to explore a 
> cleaner API to see how well it works.
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> Bernard Aboba <mailto:bernard_aboba@hotmail.com>
> 26 June, 2013 8:19 PM
> I do think No Plan represents progress toward containing the SDP 
> monster in WebRTC 1.0, particularly for video scenarios. However, I 
> also agree with Robin's arguments against SDP and O/ A, particularly 
> for a server-side API (e.g. Node.js modules) where the current API 
> makes no sense at all. So my perspective is to contain the monster in 
> 1.0, then go with 2.0 first on server, then on the browser.
>
> On Jun 17, 2013, at 10:34 PM, "Peter Thatcher" <pthatcher@google.com 
> <mailto:pthatcher@google.com>> wrote: