[rtcweb] RTCWeb Terminology

Hadriel Kaplan <HKaplan@acmepacket.com> Sat, 22 October 2011 17:13 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 6064C21F85B9 for <rtcweb@ietfa.amsl.com>; Sat, 22 Oct 2011 10:13:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[AWL=0.181, BAYES_00=-2.599]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Q0PKNw2sWDyq for <rtcweb@ietfa.amsl.com>; Sat, 22 Oct 2011 10:13:09 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com []) by ietfa.amsl.com (Postfix) with ESMTP id AEC2121F85B8 for <rtcweb@ietf.org>; Sat, 22 Oct 2011 10:13:09 -0700 (PDT)
Received: from MAIL2.acmepacket.com ( by etmail.acmepacket.com ( with Microsoft SMTP Server (TLS) id; Sat, 22 Oct 2011 13:13:04 -0400
Received: from MAIL1.acmepacket.com ([]) by Mail2.acmepacket.com ([]) with mapi id 14.01.0270.001; Sat, 22 Oct 2011 13:13:04 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Thread-Topic: RTCWeb Terminology
Thread-Index: AQHMkN3c87Lt2+tvdEyozCfd9rxlhQ==
Date: Sat, 22 Oct 2011 17:13:04 +0000
Message-ID: <AAB480AA-8F03-4C25-8A7C-55B88D057C24@acmepacket.com>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CF24D89CA7A08C4B967FE78B262EB10A@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Subject: [rtcweb] RTCWeb Terminology
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: Sat, 22 Oct 2011 17:13:10 -0000

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.