Re: [rtcweb] Use-case grouping

Harald Alvestrand <harald@alvestrand.no> Tue, 21 June 2011 15:30 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 B766A11E825B for <rtcweb@ietfa.amsl.com>; Tue, 21 Jun 2011 08:30:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knZn70LLaPVy for <rtcweb@ietfa.amsl.com>; Tue, 21 Jun 2011 08:30:01 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id B653B11E8148 for <rtcweb@ietf.org>; Tue, 21 Jun 2011 08:30:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7EE4839E13B for <rtcweb@ietf.org>; Tue, 21 Jun 2011 17:29:01 +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 Hko3bjN2YYpT for <rtcweb@ietf.org>; Tue, 21 Jun 2011 17:29:00 +0200 (CEST)
Received: from [192.168.1.53] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 70C5F39E08B for <rtcweb@ietf.org>; Tue, 21 Jun 2011 17:29:00 +0200 (CEST)
Message-ID: <4E00B8F8.4050306@alvestrand.no>
Date: Tue, 21 Jun 2011 17:30:00 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <7F2072F1E0DE894DA4B517B93C6A05851DB5336E53@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05851DB5336E53@ESESSCMS0356.eemea.ericsson.se>
Content-Type: multipart/alternative; boundary="------------070201030908020204060002"
Subject: Re: [rtcweb] Use-case grouping
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, 21 Jun 2011 15:30:01 -0000

Seems to me sensible to have groupings.

The use case I don't see a place for at the moment is the single 
point-to-point call; the proposed use case I don't see mentioned below 
is my suggestion for "interoperable calling".

So this might require more tuning.

On 06/21/11 14:39, Christer Holmberg wrote:
> Hi,
> It's nice to see the amount of use-cases people have submitted :)
> Now, since many of the use-cases are related to each other, and in 
> order to get a better and easy-to-read structure of the document, I 
> would like to suggest to devide the use-cases into different "use-case 
> groups".
> Below is a proposed grouping, and examples of use-cases which would be 
> listed in each group. I have only used the existing use-cases, and the 
> ones suggested by Cullen, but I am aware that more use-cases have been 
> proposed :)
> Telephony use-cases:
>     - Telephony terminal use-case (draft)
>     - Call fedex use-case (Cullen)
> Video conferenceing use-cases:
>     - With central server (draft)
>     - Without central server (draft)
>     - Hockey (draft)
>     - Screen re-size (Cullen)
> Embedded voice communicatoin use-case:
>    - Multiparty on-line game with voice communication (draft)
> Bandwidth/QoS/mobility use-cases:
>    - NIC Change (Cullen)
>    - QoS Marking (Cullen)
> Later, we can of course modify/add/remove groups, but I think the 
> grouping above would be a good start, and I think all the use-cases so 
> far proposed would fit into one of those groups.
> Comments?
> Regards,
> Christer
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb