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

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
> 