Re: [maitai] Roles of Sender and Receiver

Peter Musgrave <peter.musgrave@magorcorp.com> Thu, 02 December 2010 18:59 UTC

Return-Path: <peter.musgrave@magorcorp.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 8A57828C112 for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.27
X-Spam-Level:
X-Spam-Status: No, score=-103.27 tagged_above=-999 required=5 tests=[AWL=0.329, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 ycSDksE3Jzfb for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 10:59:12 -0800 (PST)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id B215828C12A for <maitai@ietf.org>; Thu, 2 Dec 2010 10:59:12 -0800 (PST)
Received: by gwj17 with SMTP id 17so4818776gwj.31 for <maitai@ietf.org>; Thu, 02 Dec 2010 11:00:28 -0800 (PST)
Received: by 10.151.6.15 with SMTP id j15mr1975364ybi.391.1291316428487; Thu, 02 Dec 2010 11:00:28 -0800 (PST)
Received: from petermac.magor.local ([72.1.217.106]) by mx.google.com with ESMTPS id u10sm2630722yba.1.2010.12.02.11.00.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Dec 2010 11:00:27 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.com>
Date: Thu, 02 Dec 2010 14:00:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <62F4714D-7819-4BBE-A588-9BE3FADBC001@magorcorp.com>
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <C4064AF1C9EC1F40868C033DB94958C703474808@XMB-RCD-111.cisco.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C02BD7CFC@xmb-sjc-234.amer.cisco.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
X-Mailer: Apple Mail (2.1082)
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 18:59:13 -0000

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?

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