Re: [rtcweb] RTCWeb Terminology

Cullen Jennings <> Mon, 24 October 2011 15:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0F1B421F851F for <>; Mon, 24 Oct 2011 08:03:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -106.292
X-Spam-Status: No, score=-106.292 tagged_above=-999 required=5 tests=[AWL=0.307, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Qs2tdOMKQKnJ for <>; Mon, 24 Oct 2011 08:03:54 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4718D21F8CDE for <>; Mon, 24 Oct 2011 08:03:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1577; q=dns/txt; s=iport; t=1319468630; x=1320678230; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=D6sn77WrLdXNcFb2NhbvmiFkZ/e0JQghqhgy6MO7TQI=; b=G0HamTaRFx95t8jJf81Fup9E4zYAzaNgRrHZUnEVdweA0DRxurOWgTqt g3XaqS64//o6hbw7XHOk5ynP35AZPyOVQEOt3vCzl31uIwvJWtQKzQf3q kcdCFl+hrtwB21ul/gtzDMDFdtVcR851Dm58IRD9BOF0/bcjzy1FPQGgs I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.69,398,1315180800"; d="scan'208";a="9866599"
Received: from ([]) by with ESMTP; 24 Oct 2011 15:03:39 +0000
Received: from [] ( []) by (8.14.3/8.14.3) with ESMTP id p9OF3cAF030994; Mon, 24 Oct 2011 15:03:38 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <>
In-Reply-To: <>
Date: Mon, 24 Oct 2011 09:03:38 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: Hadriel Kaplan <>
X-Mailer: Apple Mail (2.1084)
Cc: "" <>, "" <>
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 15:03:55 -0000

I don't think there is an answer to this yet so I guess we need to figure it out.  I'm ore concerned about the long term explanation to people outside W3C or IETF. Hadriel, with you marketing hat on, you have any suggestions of what we should call the whole thing?

On Oct 22, 2011, at 11:13 AM, Hadriel Kaplan wrote:

> Howdy,
> 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.
> -hadriel
> _______________________________________________
> rtcweb mailing list