Return-Path: <Raju.Makaraju@alcatel-lucent.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id AFF221A1A7B
 for <rtcweb@ietfa.amsl.com>; Sun, 30 Nov 2014 11:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level: 
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01]
 autolearn=ham
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id kDHIFK0FSsXj for <rtcweb@ietfa.amsl.com>;
 Sun, 30 Nov 2014 11:44:07 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com
 [135.245.210.21])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id AC55B1A1A7A
 for <rtcweb@ietf.org>; Sun, 30 Nov 2014 11:44:07 -0800 (PST)
Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65])
 by Websense Email Security Gateway with ESMTPS id B09838A0A3629
 for <rtcweb@ietf.org>; Sun, 30 Nov 2014 19:44:00 +0000 (GMT)
Received: from US70TWXCHHUB03.zam.alcatel-lucent.com
 (us70twxchhub03.zam.alcatel-lucent.com [135.5.2.35])
 by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id sAUJi1n5031050
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL)
 for <rtcweb@ietf.org>; Sun, 30 Nov 2014 14:44:03 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.56]) by
 US70TWXCHHUB03.zam.alcatel-lucent.com ([135.5.2.35]) with mapi id
 14.03.0195.001; Sun, 30 Nov 2014 14:44:01 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-13.txt
Thread-Index: AQHQCw3w2ia/yona0k6xAQgNHvOCYJx5bwHQ
Date: Sun, 30 Nov 2014 19:44:01 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17828E64262E@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <20141128131903.18180.87191.idtracker@ietfa.amsl.com>
In-Reply-To: <20141128131903.18180.87191.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/6yoRcta8CIwXfNatBQ6OEGblkak
Subject: Re: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-13.txt
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 30 Nov 2014 19:44:09 -0000


>A WebRTC browser (also called a WebRTC User Agent or WebRTC UA) is      >s=
omething that conforms to both the protocol specification and the
>Javascript API defined above.

Thanks for adding updates to the terminology, which now captures most
of it.
I have a comment on the above text in 2.2.

This seem to focus more on WebRTC **browser**. But, there are hybrid
environments, such as Apache Cordova, which are not browsers but can
conform to protocol specification and Javascript API just like a=20
browser (as most of the times they share same source code as a browser). An=
droid KitKat provided WebView component, that supports WebRTC APIs+Javascri=
pt, is one example which is close to native than hybrid environment. To inc=
lude these use cases, I suggest changing the above text to:

"A WebRTC User Agent or WebRTC UA is something that conforms to both the pr=
otocol specification and the Javascript API defined above. WebRTC browser i=
s one such WebRTC UA. However, other non-browser implementations may confor=
m to WebRTC UA as well."

BR
Raju

> -----Original Message-----
> From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Friday, November 28, 2014 7:19 AM
> To: i-d-announce@ietf.org
> Cc: rtcweb@ietf.org
> Subject: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-13.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Real-Time Communication in WEB-browsers
> Working Group of the IETF.
>=20
>         Title           : Overview: Real Time Protocols for Browser-based
> Applications
>         Author          : Harald T. Alvestrand
> 	Filename        : draft-ietf-rtcweb-overview-13.txt
> 	Pages           : 22
> 	Date            : 2014-11-28
>=20
> Abstract:
>    This document gives an overview and context of a protocol suite
>    intended for use with real-time applications that can be deployed in
>    browsers - "real time communication on the Web".
>=20
>    It intends to serve as a starting and coordination point to make sure
>    all the parts that are needed to achieve this goal are findable, and
>    that the parts that belong in the Internet protocol suite are fully
>    specified and on the right publication track.
>=20
>    This document is an Applicability Statement - it does not itself
>    specify any protocol, but specifies which other specifications WebRTC
>    compliant implementations are supposed to follow.
>=20
>    This document is a work item of the RTCWEB working group.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-overview/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-rtcweb-overview-13
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-rtcweb-overview-13
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

