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

Peter Thatcher <pthatcher@google.com> Fri, 12 July 2013 19: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 5148321F9CA2 for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 12:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.781
X-Spam-Level:
X-Spam-Status: No, score=-1.781 tagged_above=-999 required=5 tests=[AWL=-0.110, 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 iIrN8YtjtkYu for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 12:01:36 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 9E36B21F9E58 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 12:01:12 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un1so9373050pbc.1 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 12:01:12 -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=APudZcQi2N5ZkpCbvvjAPaq6Aivg98sSvep2E+jlCUk=; b=IChEhcc5CSFPtyFfyPuj3NMIMUZiUxiSD35GhJJ2gAVt0VXVXcAOuXwgArslKR3qMa XIlVZy9NMJbhlvo7oDHYBm159Wr7p3gftrI54JGjx48azdzV4f2WZfQprNOl4o0140OY jISEbhNiHwqkTl/0TcqAU3oyVZXi22tZ2AZ0LmkyxmQEKB/ehf/sCub9VJWKDYg9Q8a7 NrFEYkXUD5RYvJOw9ZAJ0SNMT4PxGZuzj/878GH79LO+o38UrDFnajdHL+jNIw2sq1hU U4V5Kc4yurz52wNSkh/UVduSNprXiFCkkPX/YZ7jkV4j+bMNhMsuMvoOwvPT1AqdkYli dveA==
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=APudZcQi2N5ZkpCbvvjAPaq6Aivg98sSvep2E+jlCUk=; b=YGf0UW9AVLYwCnZWkFZH84FUk8cZsizb0JuvAgfViizwEbVIdbpqP4NAsTxblRpILI nOppHwAYaVh4QWcs/gzOmOEU9EcJvt/S4tgH8/WHBX43pxcZeetcbCN3sqUIcgQalHud 1v8hbE9ISwgHhTi1uGRUPj99eVKcjvuABkuy0n6jwImQ6yiBBxmEGXWrQUtdI3Ka7Znh nutcfmX2W0LYrZYSMLx+kQSqv9eIsU+I5GeJOit2uFeV4H3L6S3mxYoXHOiOiJ0/mT5Y +RYsYaxm82P6eATBBFs5O4RCUN6pXScM9T6cE4JV3cNtBlRiIYkFuU3lBQjNY8OOoeP/ Ds4Q==
X-Received: by 10.66.243.5 with SMTP id wu5mr39503754pac.44.1373655672330; Fri, 12 Jul 2013 12:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.169 with HTTP; Fri, 12 Jul 2013 12:00:32 -0700 (PDT)
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A4841A308833@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <51CA6FEE.6030702@hookflash.com> <CAHp8n2=gz8Rk11otigNb=BcZxNQcdptmiJ_pr-rjvqwMbv_5yQ@mail.gmail.com> <CAJrXDUFYKEDJK5d9ZbEdUa8+UuDBY7nxuj18J98j6rQdQEozCQ@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A4841A308833@tk5ex14mbxc272.redmond.corp.microsoft.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 12 Jul 2013 12:00:32 -0700
Message-ID: <CAJrXDUHcYYot4F2OQkMQLBftJ18ooj29fQ+5ryUo8N9RqR=GDg@mail.gmail.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary=047d7b111f5f64ab3104e15522fe
X-Gm-Message-State: ALoCoQnEfSTRCd+rP2rIU3RG85tsIitUpqCu3pR7zsaNYa0o61etIvHEnpAGoqQN0RdPZ8j4SUmuH5w0RJWbV/MwfjyuPU/ljeqOYHGdsRGE6+AgJVtqg2H2shVwwD61xgr37ChWxUdvJ6qLYBoKbG/hTk0PdOHW5Ts90GNWa3V8MDA9+rvoYwEsv5rjf57UKgpPLPH7rYIU
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: Fri, 12 Jul 2013 19:01:38 -0000

I wasn't aware of that.  Thanks for letting me know.


On Mon, Jul 8, 2013 at 9:02 AM, Matthew Kaufman (SKYPE) <
matthew.kaufman@skype.net> wrote:

>  Some of us work for browser vendors who cannot follow that link, you
> know.****
>
> ** **
>
> Matthew Kaufman****
>
> ** **
>
> *From:* rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] *On
> Behalf Of *Peter Thatcher
> *Sent:* Monday, July 8, 2013 8:01 AM
> *To:* Silvia Pfeiffer
> *Cc:* rtcweb@ietf.org
> *Subject:* Re: [rtcweb] New Draft - WebRTC JS Object API Model****
>
> ** **
>
> ** **
>
> ** **
>
> 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****
>
>  ** **
>