Re: [rtcweb] Relation of Mozilla WebAPI announced today to RTCWEB/WebRTC work?

"Timothy B. Terriberry" <tterriberry@mozilla.com> Tue, 23 August 2011 17:58 UTC

Return-Path: <prvs=20974d5c9=tterriberry@mozilla.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 9A65D21F8A7E for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 10:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
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 8vbl-ixsQdKO for <rtcweb@ietfa.amsl.com>; Tue, 23 Aug 2011 10:58:57 -0700 (PDT)
Received: from mxip0i.isis.unc.edu (mxip0i.isis.unc.edu [152.2.0.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA3221F8A71 for <rtcweb@ietf.org>; Tue, 23 Aug 2011 10:58:56 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAGrpU06sGgRS/2dsb2JhbABCp0KBV4FAAQEEATg6BgEFCwshFg8JAwIBAgFFEwEHAodtvRCCRIQEBIdhkDYPjA0
X-IronPort-AV: E=Sophos;i="4.67,416,1309752000"; d="scan'208";a="232402729"
Received: from mr1a.isis.unc.edu (HELO smtp.unc.edu) ([172.26.4.82]) by mxip0o.isis.unc.edu with ESMTP; 23 Aug 2011 14:00:01 -0400
X-UNC-Auth-As: tterribe
X-UNC-Auth-IP: 63.245.220.240
Received: from [10.250.5.61] (corp-240.mv.mozilla.com [63.245.220.240]) (authenticated bits=0) by smtp.unc.edu (8.14.4/8.14.3) with ESMTP id p7NHxxSQ026516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Aug 2011 14:00:01 -0400 (EDT)
Message-ID: <4E53EA9F.1080905@mozilla.com>
Date: Tue, 23 Aug 2011 10:59:59 -0700
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110604 Gentoo/2.0.14 SeaMonkey/2.0.14
MIME-Version: 1.0
References: <2C8C7F02-2175-43AA-B58C-65F944555F9D@voxeo.com>
In-Reply-To: <2C8C7F02-2175-43AA-B58C-65F944555F9D@voxeo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: rtcweb@ietf.org, public-webrtc@w3.org
Subject: Re: [rtcweb] Relation of Mozilla WebAPI announced today to RTCWEB/WebRTC work?
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: Tue, 23 Aug 2011 17:58:57 -0000

> Can anyone from Mozilla please comment on how the "WebAPI" announced
> today with the goal to " provide a basic HTML5 phone experience within 3
> to 6 months" relates to the work happening in RTCWEB/WebRTC?

This is more along the lines of getting access to the APIs needed to 
instruct a mobile phone to initiate a phone call, rather than to host 
that call inside the browser. Presumably also with some way to detect 
that your on a device that supports that capability at all.