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

"Timothy B. Terriberry" <> Tue, 23 August 2011 18:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3D16321F86EA for <>; Tue, 23 Aug 2011 11:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=0.646, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id vpPXZ6adZ7Tm for <>; Tue, 23 Aug 2011 11:40:58 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id A6E7F21F86D0 for <>; Tue, 23 Aug 2011 11:40:58 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.67,416,1309752000"; d="scan'208";a="232482272"
Received: from (HELO ([]) by with ESMTP; 23 Aug 2011 14:42:01 -0400
X-UNC-Auth-As: tterribe
Received: from [] ( []) (authenticated bits=0) by (8.14.4/8.14.3) with ESMTP id p7NIfsVP011340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Aug 2011 14:41:59 -0400 (EDT)
Message-ID: <>
Date: Tue, 23 Aug 2011 11:41:53 -0700
From: "Timothy B. Terriberry" <>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110604 Gentoo/2.0.14 SeaMonkey/2.0.14
MIME-Version: 1.0
To: Harald Alvestrand <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Jonas Sicking <>,,
Subject: Re: [rtcweb] Relation of Mozilla WebAPI announced today to RTCWEB/WebRTC work?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 23 Aug 2011 18:40:59 -0000

Harald Alvestrand wrote:
> On 08/23/11 19:59, Timothy B. Terriberry wrote:
>>> 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.
> The blog post sounds like a virtual clone of the W3C Device API charter.
> Is that your planned venue for standardizing these APIs?

I'm not sure that's been worked out yet, but before I say too many 
incorrect things, let me CC Jonas so he can correct me.

> I can't say I'm overly happy with the amount of imagination spent on the
> name, but the effort seems to make sense!

Well, I didn't name the thing, but keep in mind that initiating phone 
calls is only one small part of the total effort.