Re: [rtcweb] RTCWeb Terminology

"Cavigioli, Chris" <> Mon, 24 October 2011 04:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 20AD921F8C1B for <>; Sun, 23 Oct 2011 21:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2EJI4LvCD1qK for <>; Sun, 23 Oct 2011 21:10:18 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EB69921F8BAB for <>; Sun, 23 Oct 2011 21:10:17 -0700 (PDT)
Received: from ([]) by with ESMTP; 23 Oct 2011 21:10:12 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.69,396,1315206000"; d="scan'208";a="81011979"
Received: from ([]) by with ESMTP; 23 Oct 2011 21:10:12 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Sun, 23 Oct 2011 21:10:12 -0700
Received: from ([]) by ([]) with mapi; Sun, 23 Oct 2011 21:10:11 -0700
From: "Cavigioli, Chris" <>
To: Hadriel Kaplan <>, "" <>, "" <>
Date: Sun, 23 Oct 2011 21:10:00 -0700
Thread-Topic: RTCWeb Terminology
Thread-Index: AQHMkN3c87Lt2+tvdEyozCfd9rxlhZWK44gg
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rtcweb] RTCWeb Terminology
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: Mon, 24 Oct 2011 04:10:52 -0000

Very good question - been bugging me too.  -chris 

-----Original Message-----
From: [] On Behalf Of Hadriel Kaplan
Sent: Saturday, October 22, 2011 10:13 AM
Subject: RTCWeb Terminology

this may seem like a silly question, but what are the actual names and capitalization schemes for the overall architecture, mechanism/protocol, API and such?

I believe the Working Group names are "RTCWEB" in IETF and "WEBRTC" in W3C.  But in the W3C it appears the name of the API doc is "WebRTC".

Is the overall thing "RTCWEB", "RTCWeb", "RTCweb", or "rtcweb"?  I've seen all 4 uses in IETF drafts.  Meanwhile in W3C they call the overall architecture and protocol "WEBRTC" in the "WebRTC" document.  Which is it?

Is the Browser API itself an "RTCWeb API" or "WebRTC API" or what?

The draft-ietf-rtcweb-overview draft has a terminology section but does not cover this.

I know this is silly, but I've gotten the question several times from customers and marketing folks. (plus it would be nice to be consistent in both IETF and W3C docs)

I apologize if this question has already been asked and answered.  I googled but found conflicting terms and usage in those results as well.