Re: [maitai] Roles of Sender and Receiver

"Charles Eckel (eckelcu)" <eckelcu@cisco.com> Thu, 02 December 2010 20:58 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 76BCF3A69CF for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 12:58:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.419
X-Spam-Level:
X-Spam-Status: No, score=-10.419 tagged_above=-999 required=5 tests=[AWL=0.180, 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 4AepNYHG21mX for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 12:58:34 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id A01BE3A699D for <maitai@ietf.org>; Thu, 2 Dec 2010 12:58:34 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGOX90yrR7Hu/2dsb2JhbACjKnGoNpsahUcEhF6JIA
X-IronPort-AV: E=Sophos;i="4.59,289,1288569600"; d="scan'208";a="226727750"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 02 Dec 2010 20:59:50 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oB2Kxowu017671; Thu, 2 Dec 2010 20:59:50 GMT
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 2 Dec 2010 12:59:50 -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 12:59:48 -0800
Message-ID: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7F02@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <2D777804-734A-4561-B019-A735079B7D78@americafree.tv>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [maitai] Roles of Sender and Receiver
Thread-Index: AcuSXg4MCv9fPCcJRL2RPN1mHS/2TwABDYKw
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <C4064AF1C9EC1F40868C033DB94958C703474808@XMB-RCD-111.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.com> <62F4714D-7819-4BBE-A588-9BE3FADBC001@magorcorp.com> <2D777804-734A-4561-B019-A735079B7D78@americafree.tv>
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Marshall Eubanks <tme@americafree.tv>, Peter Musgrave <peter.musgrave@magorcorp.com>
X-OriginalArrivalTime: 02 Dec 2010 20:59:50.0812 (UTC) FILETIME=[DC72CDC0:01CB9263]
Cc: maitai@ietf.org
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 20:58:35 -0000

That is my thinking as well. You advertise what you have, which may or
may not include multiple representations of the same thing, then let the
other side decide what they want. The may want to receive a simplified
view of things, such a single composite image, or they may want
everything separate and then to do some composition or something else on
their end.

Cheers,
Charles

> -----Original Message-----
> From: Marshall Eubanks [mailto:tme@americafree.tv]
> Sent: Thursday, December 02, 2010 12:17 PM
> To: Peter Musgrave
> Cc: Charles Eckel (eckelcu); maitai@ietf.org
> Subject: Re: [maitai] Roles of Sender and Receiver
> 
> 
> On Dec 2, 2010, at 2:00 PM, Peter Musgrave wrote:
> 
> >
> > On 2010-12-02, at 11:10 AM, Charles Eckel (eckelcu) wrote:
> >
> >> 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
> >
> > Ok, I see what you're after.
> >
> > In the case where the receiver elects to get three separate streams,
then I have a refinement for my
> question.
> >
> > Who now decides how the streams from A map on to screens at B?
> 
> The MCU, of course. So, all 3 could be sent to the MCU, and it could
send a 3-tuple to some end
> points, switched to others, composited to
> still others, and even combinations to some.
> 
> The point is that there could be middleware that knows more about what
is going on than any of the
> endpoints, which only have partial knowledge.
> 
> 
> Regards
> Marshall
> 
> 
> 
> >
> > A could send streams targeted at specific screens at B (after
examining B's description of it's
> screens)
> >
> > -or-
> >
> > B could send A instructions on where to send each stream (based on
examining A's description of it's
> cameras)
> >
> > -or-
> >
> > We can find use-cases in which both techniques might be required.
> >
> > I am trying to decide how complete the information in a room
description really needs to be. While I
> like the idea of a reasonably complete physical description (since it
is very future proof) - I think
> it imposes a burden on each side which might not be warranted. The
other extreme (just label cameras
> left, center, right) seems to obviously limited. Where is the middle
ground?
> >
> > Peter Musgrave
> > _______________________________________________
> > maitai mailing list
> > maitai@ietf.org
> > https://www.ietf.org/mailman/listinfo/maitai
> >