Re: [maitai] Roles of Sender and Receiver

"Duckworth, Mark" <Mark.Duckworth@polycom.com> Thu, 02 December 2010 18:09 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 E403A28C136 for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:09:44 -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 yZtrO-JW8mHV for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:09:44 -0800 (PST)
Received: from Crpehubprd01.polycom.com (crpehubprd01.polycom.com [140.242.64.158]) by core3.amsl.com (Postfix) with ESMTP id 0D63928C130 for <maitai@ietf.org>; Thu, 2 Dec 2010 10:09:41 -0800 (PST)
Received: from crpehubprd02.polycom.com (10.236.0.154) by Crpehubprd01.polycom.com (10.236.0.158) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 2 Dec 2010 10:10:57 -0800
Received: from Crpmboxprd01.polycom.com ([fe80::e001:c7b0:91a1:9443]) by crpehubprd02.polycom.com ([fe80::1c3e:2e7c:4b4f:14fd%10]) with mapi; Thu, 2 Dec 2010 10:10:57 -0800
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: "maitai@ietf.org" <maitai@ietf.org>
Date: Thu, 02 Dec 2010 10:10:55 -0800
Thread-Topic: [maitai] Roles of Sender and Receiver
Thread-Index: AcuSH+FPRbLe7wE3SMi2WTNf4O8qQAAFgccgAAEArrAABGtHYA==
Message-ID: <44C6B6B2D0CF424AA90B6055548D7A61A76B3628@CRPMBOXPRD01.polycom.com>
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <C4064AF1C9EC1F40868C033DB94958C703474808@XMB-RCD-111.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.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 18:09:45 -0000

Charles,

That sounds consistent with the way I have been thinking about it too.  B might also want to ask for a particular stream at a particular time, as in Peter's example of wanting to see the customer even though the customer isn't speaking.

Mark

-----Original Message-----
From: maitai-bounces@ietf.org [mailto:maitai-bounces@ietf.org] On Behalf Of Charles Eckel (eckelcu)
Sent: Thursday, December 02, 2010 11:11 AM
To: Mike Hammer (hmmr); Peter Musgrave; maitai@ietf.org
Subject: Re: [maitai] Roles of Sender and Receiver

The way I have been thinking about it, A would advertise what cameras it
has and ways it can present them to B. B would then be able to select
the camera and/or representations it wants.
As a simplified example, A could advertise the following:

I have 3 cameras, left, center, and right.
I can provide these as:
- 3 separate streams
- 1 active speaker switched stream
- 1 stream composed of the three

Of course there would be audio and many other things to consider, but
hopefully that gets the general idea across. This allows B to have as
much of as little control over what it receives as it likes, and it
should be able to change mid call.

Cheers,
Charles

> -----Original Message-----
> From: maitai-bounces@ietf.org [mailto:maitai-bounces@ietf.org] On
Behalf Of Mike Hammer (hmmr)
> Sent: Thursday, December 02, 2010 7:34 AM
> To: Peter Musgrave; maitai@ietf.org
> Subject: Re: [maitai] Roles of Sender and Receiver
> 
> Peter,
> 
> Unless of course it is a company meeting and the speaker is your CEO!
> 
> Something has to decide what screen tunes into what camera, no matter
> what.
> 
> Question is what can be programmed automatic, and what is allowed to
be
> manual.
> And if manual, what information is available to make such a decision.
> 
> Mike
> 
> 
> -----Original Message-----
> From: maitai-bounces@ietf.org [mailto:maitai-bounces@ietf.org] On
Behalf
> Of Peter Musgrave
> Sent: Thursday, December 02, 2010 7:53 AM
> To: maitai@ietf.org
> Subject: [maitai] Roles of Sender and Receiver
> 
> Hi,
> 
> 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