Re: [rtcweb] WebRTC definition (Re: Consensus Call: RTCWeb Terminology)

Jim McEachern <jim.mceachern@genband.com> Thu, 27 October 2011 02:21 UTC

Return-Path: <jim.mceachern@genband.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCB021F85AA for <rtcweb@ietfa.amsl.com>; Wed, 26 Oct 2011 19:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.999
X-Spam-Level:
X-Spam-Status: No, score=-4.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_BACKHAIR_27=1, J_CHICKENPOX_66=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hvh1nN-uppWz for <rtcweb@ietfa.amsl.com>; Wed, 26 Oct 2011 19:21:29 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 9207F21F84B3 for <rtcweb@ietf.org>; Wed, 26 Oct 2011 19:21:22 -0700 (PDT)
Received: from mail.genband.com ([63.149.188.88]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP; Wed, 26 Oct 2011 19:21:25 PDT
Received: from owa.genband.com ([172.16.21.98]) by mail.genband.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Oct 2011 21:21:01 -0500
Received: from GBPLMAIL02.genband.com ([fe80::9455:4039:582f:aee8]) by gbex02.genband.com ([fe80::d038:d922:68b6:b18e%14]) with mapi id 14.01.0339.001; Wed, 26 Oct 2011 21:20:56 -0500
From: Jim McEachern <jim.mceachern@genband.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] WebRTC definition (Re: Consensus Call: RTCWeb Terminology)
Thread-Index: AQHMlC6/wB/LrtI+pkWxD+xy+BZUrZWPcxXw
Date: Thu, 27 Oct 2011 02:20:55 +0000
Message-ID: <8584590C8D7DD141AA96D01920FC6C698C8CBDB5@gbplmail02.genband.com>
References: <AAB480AA-8F03-4C25-8A7C-55B88D057C24@acmepacket.com> <42322A10-14A7-4600-820D-7612A1B12592@cisco.com> <3747C7CB-C039-4D15-A46C-8FDB9A47AF3A@acmepacket.com> <DD0E14D2-252F-442B-9AFC-8ECD6704794B@cisco.com> <4EA889CC.3090001@alvestrand.no>
In-Reply-To: <4EA889CC.3090001@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.35.81.184]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Oct 2011 02:21:01.0101 (UTC) FILETIME=[11ED8DD0:01CC944F]
X-TM-AS-Product-Ver: SMEX-8.0.0.4160-6.500.1024-18474.003
X-TM-AS-Result: No--24.502800-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Subject: Re: [rtcweb] WebRTC definition (Re: Consensus Call: 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: Thu, 27 Oct 2011 02:21:29 -0000

How about this?

WebRTC
      A collaborative standards effort between the IETF and W3C that specifies a JavaScript API and architectural context, to enable real-time peer to peer audio, video and data communication between browsers
     on the Internet.
     Components of WebRTC include a protocol profile, defined in the IETF, of which this document
     gives an overview, and an API, defined in the W3C, and specified in <reference>

Jim

> -----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
> Behalf Of Harald Alvestrand
> Sent: Wednesday, October 26, 2011 6:30 PM
> To: rtcweb@ietf.org
> Subject: [rtcweb] WebRTC definition (Re: Consensus Call: RTCWeb
> Terminology)
> 
> On 10/26/2011 10:17 AM, Cullen Jennings wrote:
> > With my chair hat on ...
> >
> > I'd like to declare we currently have consensus for Hadriel's proposal that
> the technology should be referred to as "WebRTC" and the API as the
> "WebRTC API". The IETF WG name is still RTCWeb, the mailing list is still
> rtcweb@ietf.org, the IETF drafts should still have "-rtcweb-" in them to
> indicate the WG name.
> 
> As -overview editor, I'm happy to include this definition.
> 
> Just because I have to write it in a terminology list, I wonder how I should
> define it.
> 
> Is it an effort? A technology? A project?
> 
> It should be something like:
> 
> WebRTC
>       A <something> that <someting> to enable peer to peer audio and video
> between browsers
>      on the Internet.
>      Components of WebRTC include a protocol profile, defined in the IETF, of
> which this document
>      gives an overview, and an API, defined in the W3C, and specified in
> <reference>
> 
> Suggestions for the <something>s (or alternate formulations) would be most
> welcome.
> 
>                   Harald
> 
> 
> 
> > Cullen<RTCWeb CoChair>
> >
> >
> > On Oct 24, 2011, at 10:56 AM, Hadriel Kaplan wrote:
> >
> >> For the API, the consensus was it would be confusing to people if we
> weren't consistent with W3C docs.
> >>
> >> So I propose the following:
> >>
> >> WebRTC: the whole shebang
> >> WebRTC API: the JS<->Browser API.
> >>
> >> -hadriel
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb