[rtcweb] RTCWeb architecture text requirement [Was RE: New use case: Large multiparty session]

"Parthasarathi R (partr)" <partr@cisco.com> Wed, 03 August 2011 23:59 UTC

Return-Path: <partr@cisco.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 1808C11E80AD for <rtcweb@ietfa.amsl.com>; Wed, 3 Aug 2011 16:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.165
X-Spam-Level:
X-Spam-Status: No, score=-10.165 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UUeXEisqGHYY for <rtcweb@ietfa.amsl.com>; Wed, 3 Aug 2011 16:59:45 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2369521F86CA for <rtcweb@ietf.org>; Wed, 3 Aug 2011 16:59:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=partr@cisco.com; l=2653; q=dns/txt; s=iport; t=1312415998; x=1313625598; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=9w5l2apjfVNYCByPTqnJOaun203FVA+DSvXwIOEt4t4=; b=BeH7vzM8fg4p1ATHRKKac0VLDy5oBMdsGzuSVCJmi2omxpb1EM8PEB7T 0i4gWAIIdB9G3vsWEOacWov2ka1QUtqPA/llQZk1hllTqtrwUvUQOwxg6 P2rXPaEhhfcbjEolph8o75KVTs8HxumsiXKZ7f4U+wzuPyq4GYtUDaqgo c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4AAMHfOU5Io8UQ/2dsb2JhbABCmAePWneBQAEBAQEDAQEBDwEdCjQXBAIBGQEDAQEBCgYXAQYBJh8DBggBAQQBCggIGodOohcBnm2FY18Eh1iQM4tc
X-IronPort-AV: E=Sophos;i="4.67,313,1309737600"; d="scan'208";a="106639976"
Received: from bgl-core-1.cisco.com ([72.163.197.16]) by ams-iport-1.cisco.com with ESMTP; 03 Aug 2011 23:59:56 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p73NxuSv006300; Wed, 3 Aug 2011 23:59:56 GMT
Received: from xmb-bgl-411.cisco.com ([72.163.129.207]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 4 Aug 2011 05:29:56 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 4 Aug 2011 05:29:53 +0530
Message-ID: <A11921905DA1564D9BCF64A6430A62390608E5C1@XMB-BGL-411.cisco.com>
In-Reply-To: <4E39857E.3040407@alcatel-lucent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RTCWeb architecture text requirement [Was RE: [rtcweb] New use case: Large multiparty session]
Thread-Index: AcxSAu74TGtrbXRsRrGplxMMMgjXuwANQN7g
References: <4E390884.5050909@cs.vu.nl> <4E394434.3040802@jesup.org> <4E39857E.3040407@alcatel-lucent.com>
From: "Parthasarathi R (partr)" <partr@cisco.com>
To: <igor.faynberg@alcatel-lucent.com>, <rtcweb@ietf.org>
X-OriginalArrivalTime: 03 Aug 2011 23:59:56.0291 (UTC) FILETIME=[71CF0D30:01CC5239]
Subject: [rtcweb] RTCWeb architecture text requirement [Was RE: New use case: Large multiparty session]
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, 03 Aug 2011 23:59:46 -0000

Hi all,

<snip>
> 
> Perhaps one thing to watch for in the use case write-ups is 
> separation between a use case and architecture. These are two 
> different things because one architecture can fit many (and 
> maybe all) use cases.
> 
</snip>

As mentioned by Igor, I'm also looking for the architecture document
which provide the insight into RTCWeb deployment possibilities.

draft-rosenberg-rtcweb-framework-00 is one of the RTCWeb document which
is in the similar line.  I'm interested in hearing others opinion on
this. 

Thanks
Partha 


> -----Original Message-----
> From: rtcweb-bounces@ietf.org 
> [mailto:rtcweb-bounces@ietf.org] On Behalf Of Igor Faynberg
> Sent: Wednesday, August 03, 2011 11:00 PM
> To: rtcweb@ietf.org
> Subject: Re: [rtcweb] New use case: Large multiparty session
> 
> I strongly support the use case, but I was under the 
> impression that there has been a use case thar required a 
> similar architecture: a "central" server (of course, it can 
> be replicated) for accumulating input and distributing output.
> 
> For one thing, the music collaboration use case, I believe, 
> calls for this architecture.
> 
> Perhaps one thing to watch for in the use case write-ups is 
> separation between a use case and architecture. These are two 
> different things because one architecture can fit many (and 
> maybe all) use cases.
> 
> Igor
> 
> On 8/3/2011 8:51 AM, Randell Jesup wrote:
> > On 8/3/2011 4:36 AM, Arno Bakker wrote:
> >> Hi
> >>
> >> as proposed in the July 26th meeting I'd like to put forward a new 
> >> use
> >> case: assume a client is involved in a large multiparty 
> session but 
> >> is unable (or unwilling) to upload his signals to all participants.
> >>
> >> This suggests forwarding support from the network is required, e.g.
> >> some relay server, multicast, or the future IETF peer-to-peer 
> >> streaming protocol (PPSP).
> >
> > So the use case is:
> >
> > User is part of a multiparty (3 or greater) session, but for one of 
> > several reasons (such as available upstream bandwidth)  cannot send 
> > media to all other participants ("mesh" conferencing).
> > This requires that another node, either a central network 
> node (such 
> > as a conferencing server) or another member in the session, 
> relay or 
> > mix the user's media to distribute to the rest of the 
> members of the 
> > session.
> >
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>