Re: [rtcweb] New Draft - WebRTC JS Object API Model

Silvia Pfeiffer <silviapfeiffer1@gmail.com> Sat, 06 July 2013 11:00 UTC

Return-Path: <silviapfeiffer1@gmail.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 4F22821F8B33 for <rtcweb@ietfa.amsl.com>; Sat, 6 Jul 2013 04:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 Uj5iAT8oW0ua for <rtcweb@ietfa.amsl.com>; Sat, 6 Jul 2013 04:00:09 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id BAC6821F8A85 for <rtcweb@ietf.org>; Sat, 6 Jul 2013 04:00:09 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id m1so4396280oag.20 for <rtcweb@ietf.org>; Sat, 06 Jul 2013 04:00:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kLQaObYiaumQ1khfnpnbGh53cauk97Ir/kReU8Sw+rU=; b=BW42HfsdbUBj5e1zpQjpL21CeDZ0y9im5ZOXDQiAb+FzZ8CKjAHYusU0kmPO8kTUzL a9s/r4lTgLAboJgbbbqJcatcuq1gLIWBRRlv27S8689GYNsF4UqQAGm1SDDDhqS3Gw0W 3klSG1KgoYGeeKopymINcB4/uvt9swy4fK5+29rl8qwqKRfG/mvVJyk6ke8k2YRfw2vR 0MJHc47uhTa9rxVZFuxIZQSJq6F71B1nkE32BA6fcwDAy+Az2ca+uHNasPdJO0BBeYZf /IZV4NnzkmxbTmtf482ty1IMP399opiHOOrqNtm/k9oQ7DnFtNkt1kRM1eXVqG2YojZD 9fkw==
X-Received: by 10.182.118.129 with SMTP id km1mr15014578obb.15.1373108409308; Sat, 06 Jul 2013 04:00:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.173.106 with HTTP; Sat, 6 Jul 2013 03:59:49 -0700 (PDT)
In-Reply-To: <51CA6FEE.6030702@hookflash.com>
References: <51CA6FEE.6030702@hookflash.com>
From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 6 Jul 2013 20:59:49 +1000
Message-ID: <CAHp8n2=gz8Rk11otigNb=BcZxNQcdptmiJ_pr-rjvqwMbv_5yQ@mail.gmail.com>
To: Robin Raymond <robin@hookflash.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] New Draft - WebRTC JS Object API Model
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, 06 Jul 2013 11:00:10 -0000

An interesting read. It makes me wonder if there is a full description
available of the SDP that browsers (Chrome, Firefox) currently
support.

Looking forward to your proposal (I assume it will be on the W3C list?).

Cheers,
Silvia.

On Wed, Jun 26, 2013 at 2:37 PM, Robin Raymond <robin@hookflash.com> wrote:
>
> According to many, real adoption of WebRTC will not happen if we continue to
> force everyone to use this SDP Offer/Answer methodology.  It is clearly
> blocking our way forward and the amount of specification documentation
> remaining needed for the browser vendors to produce a compatible SDP based
> WebRTC engine in a browser is much more daunting than most are willing to
> admit.
>
>
> The draft rationale behind a JavaScript Object API model:
>
> http://www.ietf.org/internet-drafts/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00.txt
>
> Whereas:
>
> The WebRTC JavaScript Object API & Shim document will be along shortly.
>
>
> We wanted to get this initial rationale draft informational document out
> right away. Everyone that has any interest should review the reasons and
> concepts and comment before we get too far along on the details of an actual
> API, the initial API will follow in the coming days.
>
>
> Best regards,
>
> Robin Raymond
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>