Re: [maitai] Roles of Sender and Receiver

"Duckworth, Mark" <Mark.Duckworth@polycom.com> Thu, 02 December 2010 14:34 UTC

Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: maitai@core3.amsl.com
Delivered-To: maitai@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DA5128C103 for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 06:34:16 -0800 (PST)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m5GswdWI5HJ1 for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 06:34:13 -0800 (PST)
Received: from Crpehubprd01.polycom.com (crpehubprd01.polycom.com [140.242.64.158]) by core3.amsl.com (Postfix) with ESMTP id 6BB3328C125 for <maitai@ietf.org>; Thu, 2 Dec 2010 06:33:53 -0800 (PST)
Received: from Crpmboxprd01.polycom.com ([fe80::e001:c7b0:91a1:9443]) by Crpehubprd01.polycom.com ([fe80::27:216a:613a:350c%13]) with mapi; Thu, 2 Dec 2010 06:35:08 -0800
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "maitai@ietf.org" <maitai@ietf.org>
Date: Thu, 02 Dec 2010 06:35:04 -0800
Thread-Topic: [maitai] Roles of Sender and Receiver
Thread-Index: AcuSH+HOi/u1fDMETkiztPANcv0z1wAC/D1w
Message-ID: <44C6B6B2D0CF424AA90B6055548D7A61A7612FD9@CRPMBOXPRD01.polycom.com>
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com>
In-Reply-To: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com>
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
Subject: Re: [maitai] Roles of Sender and Receiver
X-BeenThere: maitai@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multi-stream Attributes for Improving Telepresence Application Interoperability <maitai.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/maitai>, <mailto:maitai-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/maitai>
List-Post: <mailto:maitai@ietf.org>
List-Help: <mailto:maitai-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/maitai>, <mailto:maitai-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Dec 2010 14:34:16 -0000

Peter,

That is a very good question.  I think we don't have an easy answer yet, it needs some discussion.  The issue gets a bit more complicated for multipoint, when there could be an MCU in the middle that is also part of the decision process.

>Consider a three display, 3 camera (3d3c) room A sending to a 1d1c room B.
>Does A offer all three streams to B and let B pick?

That is certainly a good possibility.  If B can choose dynamically, changing the choice during the session, it is similar to the current standard ability for B to select a video source from A using the H.281 SELECT VIDEO SOURCE message.  But the list of possible sources supported in H.281 isn't good enough for this application.

Maybe B wants to receive something like "current speaker stream" or "presenter stream", no matter which of A's three cameras it comes from.  I think of this as B making a higher level choice, and delegating the specific choice to A.

Maybe A is capable of sending a single stream that includes all the people in the room (perhaps by zooming out a camera, or combining three camera images into a single stream).  B might prefer to receive that type of stream.

I tend to agree an approach that gives B some control is more powerful and useful.  But I also think there are use cases where we want everything to be automatic, so we should not require a human user at site B to do anything in order to receive useful streams.

Mark Duckworth

-----Original Message-----
I have been pondering possible ways of representing a room configuration - but I think I need to back up and ask a question about basic interop architecture. 

In the selection of content on a stream, who is the active decision making entity, sender - or receiver - or both?

Consider a three display, 3 camera (3d3c) room A sending to a 1d1c room B. 

Does A offer all three streams to B and let B pick? (This leads in the direction of dynamic changes based on B, which is powerful but leads us into continuous control...)
Does A determine B has only one display and select which video B should get and send only one stream?

IHMO an approach which lets B have control over what it gets is more powerful. e.g. If I have heard the pitch from the speaker 100 times, I want to watch the customer and see if they are engaged, rather than watch the active speaker blather on....

Peter