Re: [rtcweb] Query regarding rtcweb use cases and requirements.

Harald Alvestrand <harald@alvestrand.no> Tue, 27 March 2012 10:36 UTC

Return-Path: <harald@alvestrand.no>
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 4F40021E8162 for <rtcweb@ietfa.amsl.com>; Tue, 27 Mar 2012 03:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 6lI+42-6ZuOe for <rtcweb@ietfa.amsl.com>; Tue, 27 Mar 2012 03:36:26 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 86C7121E8101 for <rtcweb@ietf.org>; Tue, 27 Mar 2012 03:36:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6E3F139E098; Tue, 27 Mar 2012 12:36:25 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0oJT8Zfu8n9; Tue, 27 Mar 2012 12:36:24 +0200 (CEST)
Received: from [130.129.67.10] (dhcp-430a.meeting.ietf.org [130.129.67.10]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 58B8039E03A; Tue, 27 Mar 2012 12:36:24 +0200 (CEST)
Message-ID: <4F71982B.4010208@alvestrand.no>
Date: Tue, 27 Mar 2012 12:36:27 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.28) Gecko/20120313 Thunderbird/3.1.20
MIME-Version: 1.0
To: ajrmeyn@gmail.com
References: <FA86515700364A16B4EDF69E88E3FA1A@devbox>
In-Reply-To: <FA86515700364A16B4EDF69E88E3FA1A@devbox>
Content-Type: multipart/alternative; boundary="------------040102050509010701030701"
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Query regarding rtcweb use cases and requirements.
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: Tue, 27 Mar 2012 10:36:28 -0000

On 03/27/2012 09:51 AM, ajrmeyn@gmail.com wrote:
> Hi,
>   
> This is with regards to the following document:
> Web Real-Time Communication Use-cases and Requirements
> draft-ietf-rtcweb-use-cases-and-requirements-06.txt
> http://datatracker.ietf.org/doc/draft-ietf-rtcweb-use-cases-and-requirements/?include_text=1
> I have noticed that the use cases with regards to Data API of web real 
> time communication, have not been addressed. For example: use cases 
> that are related to file sharing between browsers.
> is there any particular reason for the same?
Requirement F23 is a data-passing requirement.

For communications that did not need low latency, the WG felt that the 
RTCWEB requirements were not different from the requirements of any 
other application, so those could be fulfilled with other types of 
interfaces, including server-mediated file transfers.

The WG is suggesting data API/protocol solutions that can be used for 
other things than fulfiling the most narrow interpretation of the 
requirement listed, but did not feel a need to add a requirement 
covering those.

The purpose of the "use cases and requirements" is to find a minimum set 
of things that the protocol suite has to be able to do in order to be 
"good enough", not to delineate everything the protocol can be used for.

My interpretation....

                       Harald




> Regards,
> Antony Meyn
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb