Re: [rtcweb] Use-case grouping

"Lu, Hui-Lan (Huilan)" <huilan.lu@alcatel-lucent.com> Wed, 22 June 2011 14:25 UTC

Return-Path: <huilan.lu@alcatel-lucent.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 EFD6011E8108 for <rtcweb@ietfa.amsl.com>; Wed, 22 Jun 2011 07:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 8GfTB0D6X7-8 for <rtcweb@ietfa.amsl.com>; Wed, 22 Jun 2011 07:25:38 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id F2AA711E80BA for <rtcweb@ietf.org>; Wed, 22 Jun 2011 07:25:37 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id p5MEPVNY022914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Jun 2011 09:25:32 -0500 (CDT)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id p5MEPVoI025069 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 22 Jun 2011 09:25:31 -0500
Received: from USNAVSXCHMBSB3.ndc.alcatel-lucent.com ([135.3.39.137]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Wed, 22 Jun 2011 09:25:31 -0500
From: "Lu, Hui-Lan (Huilan)" <huilan.lu@alcatel-lucent.com>
To: 'Christer Holmberg' <christer.holmberg@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Wed, 22 Jun 2011 09:25:30 -0500
Thread-Topic: [rtcweb] Use-case grouping
Thread-Index: AcwwKBkpm2xc+n+GQ1Gb7cU29D+/KgADg67bACwFU3A=
Message-ID: <0E96A74B7DFCF844A9BE2A0BBE2C425F058E625BB2@USNAVSXCHMBSB3.ndc.alcatel-lucent.com>
References: <7F2072F1E0DE894DA4B517B93C6A05851DB5336E53@ESESSCMS0356.eemea.ericsson.se>, <4E00B8F8.4050306@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A05851DB53FF29A@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05851DB53FF29A@ESESSCMS0356.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
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: Wed, 22 Jun 2011 14:25:39 -0000

"Point-to-point" seems more flexible. Such a group would allow us to address use cases invovling devices (such as IP phones or mobile phones) which don't have a browser.

Huilan 

> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Christer Holmberg
> Sent: Tuesday, June 21, 2011 1:11 PM
> To: Harald Alvestrand; rtcweb@ietf.org
> Subject: Re: [rtcweb] Use-case grouping
> 
> Hi Harald,
> 
> We could add a "Point-to-point", or "Browser-to-browser", 
> use-case group.
> 
> Regards,
> 
> Christer
> 
> ________________________________
> From: rtcweb-bounces@ietf.org [rtcweb-bounces@ietf.org] On 
> Behalf Of Harald Alvestrand [harald@alvestrand.no]
> Sent: Tuesday, June 21, 2011 6:30 PM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] Use-case grouping
> 
> 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<mailto:rtcweb@ietf.org>
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>