Re: [rtcweb] New use case: Large multiparty session

Arno Bakker <arno@cs.vu.nl> Wed, 03 August 2011 13:37 UTC

Return-Path: <a.bakker@vu.nl>
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 05E5D21F8B2E for <rtcweb@ietfa.amsl.com>; Wed, 3 Aug 2011 06:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.127
X-Spam-Level:
X-Spam-Status: No, score=-4.127 tagged_above=-999 required=5 tests=[AWL=0.377, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, 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 3BGF3VBUECE1 for <rtcweb@ietfa.amsl.com>; Wed, 3 Aug 2011 06:37:24 -0700 (PDT)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.16]) by ietfa.amsl.com (Postfix) with ESMTP id 3F14B21F854D for <rtcweb@ietf.org>; Wed, 3 Aug 2011 06:37:23 -0700 (PDT)
Received: from PEXHB011B.vu.local (130.37.236.65) by mailin.vu.nl (130.37.164.16) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 3 Aug 2011 15:34:59 +0200
Received: from [130.161.211.249] (130.37.238.20) by mails.vu.nl (130.37.236.65) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 3 Aug 2011 15:34:46 +0200
Message-ID: <4E394E76.2030302@cs.vu.nl>
Date: Wed, 3 Aug 2011 15:34:46 +0200
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: <rtcweb@ietf.org>
References: <4E390884.5050909@cs.vu.nl> <4E394434.3040802@jesup.org>
In-Reply-To: <4E394434.3040802@jesup.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Subject: Re: [rtcweb] New use case: Large multiparty session
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
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 13:37:25 -0000

On 03/08/2011 14:51, Randell Jesup wrote:
> On 8/3/2011 4:36 AM, Arno Bakker wrote:
 >>
>> 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.
>


Yes. Although your wording suggests a single relay node (central or 
member) is used. Please leave the option of true peer-to-peer 
distribution (or IP multicast) of the signal open.

CU,
      Arno