Re: [rtcweb] I-D Action: draft-ietf-rtcweb-overview-13.txt

Harald Alvestrand <harald@alvestrand.no> Mon, 01 December 2014 08:55 UTC

Return-Path: <harald@alvestrand.no>
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 564E61A1A13 for <rtcweb@ietfa.amsl.com>; Mon, 1 Dec 2014 00:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 OTIxkYZ6HK5C for <rtcweb@ietfa.amsl.com>; Mon, 1 Dec 2014 00:55:24 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id 811181A0379 for <rtcweb@ietf.org>; Mon, 1 Dec 2014 00:55:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id E33597C3257 for <rtcweb@ietf.org>; Mon, 1 Dec 2014 09:55:21 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nY-eNfaR8Pfj for <rtcweb@ietf.org>; Mon, 1 Dec 2014 09:55:17 +0100 (CET)
Received: from hta-hippo.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:dda9:53b6:c5d9:2f80]) by mork.alvestrand.no (Postfix) with ESMTPSA id A51CE7C0C5E for <rtcweb@ietf.org>; Mon, 1 Dec 2014 09:55:17 +0100 (CET)
Message-ID: <547C2CF5.5000204@alvestrand.no>
Date: Mon, 01 Dec 2014 09:55:17 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <20141128131903.18180.87191.idtracker@ietfa.amsl.com> <E1FE4C082A89A246A11D7F32A95A17828E64262E@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17828E64262E@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/yNT-dkV35goZOwLBEPKsv_qLJx0
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: Mon, 01 Dec 2014 08:55:27 -0000

On 11/30/2014 08:44 PM, Makaraju, Maridi Raju (Raju) wrote:
>> A WebRTC browser (also called a WebRTC User Agent or WebRTC UA) is      >something 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
> browser (as most of the times they share same source code as a browser). Android KitKat provided WebView component, that supports WebRTC APIs+Javascript, is one example which is close to native than hybrid environment. To include these use cases, I suggest changing the above text to:
>
> "A WebRTC User Agent or WebRTC UA is something that conforms to both the protocol specification and the Javascript API defined above. WebRTC browser is one such WebRTC UA. However, other non-browser implementations may conform to WebRTC UA as well."

I find it simpler to call all these browsers.
The W3C has chosen to coin the term "interactive user agents", but I 
find that term clumsy in practice.
As written:

    o  A WebRTC browser is something that conforms to both the protocol
       specification and the Javascript API defined above.


    Browser:  Used synonymously with "Interactive User Agent" as defined
       in the HTML specification [W3C.WD-html5-20110525].


Android WebView in particular is actually Chrome with some of the user 
interface stripped away. I don't see a compelling reason to use a 
different term here.

>
> 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
>>
>>
>> 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.
>>
>>          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
>>
>> 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".
>>
>>     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.
>>
>>     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.
>>
>>     This document is a work item of the RTCWEB working group.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-rtcweb-overview/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-rtcweb-overview-13
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-rtcweb-overview-13
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> 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