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

Jonas Sicking <> Wed, 24 August 2011 00:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 86C8321F85A4 for <>; Tue, 23 Aug 2011 17:06:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yv5w1sGvzziz for <>; Tue, 23 Aug 2011 17:06:04 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id DA63321F8591 for <>; Tue, 23 Aug 2011 17:06:03 -0700 (PDT)
Received: by gxk19 with SMTP id 19so612773gxk.31 for <>; Tue, 23 Aug 2011 17:07:12 -0700 (PDT)
Received: by with SMTP id g44mr25923837yhe.43.1314144432700; Tue, 23 Aug 2011 17:07:12 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 23 Aug 2011 17:01:44 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <>
From: Jonas Sicking <>
Date: Tue, 23 Aug 2011 17:01:44 -0700
Message-ID: <>
To: "Timothy B. Terriberry" <>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 24 Aug 2011 08:13:52 -0700
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: Wed, 24 Aug 2011 00:06:04 -0000

On Tue, Aug 23, 2011 at 11:41 AM, Timothy B. Terriberry
<> wrote:
> 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'm working on a more detailed blog post which mentions our
standardization strategy. The short story is that we absolutely want
all of these APIs to be standardized. Our plan is to bring the APIs to
W3C once we've experimented enough with them to feel good about them.
Which group this ends up in depends on the API.

>> 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.

Indeed. I'm not a big fan of the name either. But the goal is indeed
to be much broader than just applications for phone and SMS.

/ Jonas