Re: [maitai] Roles of Sender and Receiver

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Thu, 02 December 2010 16:09 UTC

Return-Path: <eckelcu@cisco.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 8FBB628C14C for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 08:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.406
X-Spam-Level:
X-Spam-Status: No, score=-10.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 7Fn91tHkw9WV for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 08:09:33 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 8CA6D28C115 for <maitai@ietf.org>; Thu, 2 Dec 2010 08:09:32 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOJT90yrR7Ht/2dsb2JhbACjIXGnbpsYhUcEhF6JHw
X-IronPort-AV: E=Sophos;i="4.59,288,1288569600"; d="scan'208";a="296366083"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 02 Dec 2010 16:10:48 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oB2GAmoq022090; Thu, 2 Dec 2010 16:10:48 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 2 Dec 2010 08:10:48 -0800
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, 02 Dec 2010 08:10:46 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <C4064AF1C9EC1F40868C033DB94958C703474808@XMB-RCD-111.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [maitai] Roles of Sender and Receiver
Thread-Index: AcuSH+FPRbLe7wE3SMi2WTNf4O8qQAAFgccgAAEArrA=
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <C4064AF1C9EC1F40868C033DB94958C703474808@XMB-RCD-111.cisco.com>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "Mike Hammer (hmmr)" <hmmr@cisco.com>, Peter Musgrave <peter.musgrave@magorcorp.com>, maitai@ietf.org
X-OriginalArrivalTime: 02 Dec 2010 16:10:48.0124 (UTC) FILETIME=[7B669FC0:01CB923B]
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 16:09:35 -0000

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
> 
> 
> 
> 
> _______________________________________________
> maitai mailing list
> maitai@ietf.org
> https://www.ietf.org/mailman/listinfo/maitai
> _______________________________________________
> maitai mailing list
> maitai@ietf.org
> https://www.ietf.org/mailman/listinfo/maitai