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

Peter Thatcher <pthatcher@google.com> Mon, 08 July 2013 15:01 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 D343D21F9D58 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 08:01:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.803
X-Spam-Level:
X-Spam-Status: No, score=-1.803 tagged_above=-999 required=5 tests=[AWL=-0.132, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_URI_CONS7=0.306]
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 sd6teSC3+oN0 for <rtcweb@ietfa.amsl.com>; Mon, 8 Jul 2013 08:01:22 -0700 (PDT)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 4774C21F9C7C for <rtcweb@ietf.org>; Mon, 8 Jul 2013 08:01:22 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q10so4195687pdj.10 for <rtcweb@ietf.org>; Mon, 08 Jul 2013 08:01:22 -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=FvkQSM7UBeamAvyABVAnUrM1Pvjckq5i8vl3I77KcSk=; b=OQxE8UVeaJeZniUSZR8/NT2oIMO1NaYYMR4Lv51h5r7XS7MN4yEAk6M1ieoks7Mu4B qeswz0S67Fivp7HatfkRHbCW5pbJAfvhh0fNHI9ZUa1C3YwMTBeW7DyDToBzm2hdg1ga mCYBay3+aMU2fDqarzQeATGV+wsMLD0v9p7ZN29dGOwNzN5xPDWKRLNE6ZOrg0k7xfHX zE8JY3hwfT5hh5WCHUN5S0ywp5dEScVYPqTeJal1O0sr0spmbgqzE2/Ts09S2/S86A22 pEyom50V1pAS1+DTCCyRabLNz7Fbg4uTQoH94bInY31ISbD+5kV3SWq8d1l+5gFkIImB wb5A==
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=FvkQSM7UBeamAvyABVAnUrM1Pvjckq5i8vl3I77KcSk=; b=Pa9qFhX0XasmQrxG36JnvRDoiUcjFvnaSPuJpu0Q49/VKQkQwgMgFR7iBjFhzd0XYh e0zcErM2Vj+8YCMMjTE07auik8rl0Sy1FxxPM5zmJHHrp9sY2ljRzKI1wWiOQ0vNDGnM ib9eOYSF/LXv1GrE4kIeYoBm1ePNGT2MY0ZNAEkgheNk5GOlqOSd1csp46zbNp5Sdimm 67SLJPD/RDDJqsO6PCg8KCHZ39fBtfEKw32rhhFOFhXhNtcweZMf3jZL1ry74EreC5C+ HLJFN3bC0E8nPgeDF1OzVFFQwQ6VjwQor+nNeg+0WpZiewu7KMghINHhUhbib3rRTHTF r+Qw==
X-Received: by 10.68.29.2 with SMTP id f2mr21780269pbh.184.1373295681925; Mon, 08 Jul 2013 08:01:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.169 with HTTP; Mon, 8 Jul 2013 08:00:41 -0700 (PDT)
In-Reply-To: <CAHp8n2=gz8Rk11otigNb=BcZxNQcdptmiJ_pr-rjvqwMbv_5yQ@mail.gmail.com>
References: <51CA6FEE.6030702@hookflash.com> <CAHp8n2=gz8Rk11otigNb=BcZxNQcdptmiJ_pr-rjvqwMbv_5yQ@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Mon, 08 Jul 2013 08:00:41 -0700
Message-ID: <CAJrXDUFYKEDJK5d9ZbEdUa8+UuDBY7nxuj18J98j6rQdQEozCQ@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Content-Type: multipart/alternative; boundary="bcaec520f3b94b220204e1015139"
X-Gm-Message-State: ALoCoQlrTfipUdfPwmnMSDGJ2BD09zorQgEZ+22XgwpGCd7scYKXXGNwIsv6IWF+3qMsHfkL5vvdwDgv2t/HfrpcGfVhphbC/mAqm8Le0eouCYMkduE3AuQz0iL/Mhm0LV+HQmWahT1bGJBwRXrEibJBvIA7BaWlGWQJ+jE+S3FBSAhDYvtL9yyxEQmwAHgT47ONia+yXsXr
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: Mon, 08 Jul 2013 15:01:22 -0000

On Sat, Jul 6, 2013 at 3:59 AM, Silvia Pfeiffer
<silviapfeiffer1@gmail.com>wrote:

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

Here's the description for Chrome:

https://code.google.com/p/libjingle/source/browse/trunk/talk/app/webrtc/webrtcsdp.cc

:)


>
> 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
> >
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>