Re: [maitai] Roles of Sender and Receiver

Peter Musgrave <peter.musgrave@magorcorp.com> Thu, 02 December 2010 20:01 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 7DAF528C19F for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 12:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.312
X-Spam-Level:
X-Spam-Status: No, score=-103.312 tagged_above=-999 required=5 tests=[AWL=0.288, 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 DTnjlvQOpcXx for <maitai@core3.amsl.com>; Thu, 2 Dec 2010 12:01:10 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 1AC0D28C199 for <maitai@ietf.org>; Thu, 2 Dec 2010 12:01:00 -0800 (PST)
Received: by gxk28 with SMTP id 28so4279246gxk.31 for <maitai@ietf.org>; Thu, 02 Dec 2010 12:02:16 -0800 (PST)
Received: by 10.150.200.12 with SMTP id x12mr2157800ybf.134.1291320135731; Thu, 02 Dec 2010 12:02:15 -0800 (PST)
Received: from petermac.magor.local ([72.1.217.106]) by mx.google.com with ESMTPS id e20sm530638yhc.19.2010.12.02.12.02.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Dec 2010 12:02:15 -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: <C4064AF1C9EC1F40868C033DB94958C7034749BA@XMB-RCD-111.cisco.com>
Date: Thu, 02 Dec 2010 15:02:13 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC6CA193-F24F-4D32-BDEE-45125C2934BA@magorcorp.com>
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> <C4064AF1C9EC1F40868C033DB94958C7034749BA@XMB-RCD-111.cisco.com>
To: "Mike Hammer (hmmr)" <hmmr@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 20:01:11 -0000

I think this is actually a different, very interesting issue. This speaks to control DURING the call and the need for that to be dynamic. I completely agree - but as understand the charter it's out of scope...although I think it is inevitable that we will need to look at what exists (BFCP, conference event etc.) and determine if it can be used or start to define something new.

This might be subverted by sending all and letting the receiver take them on and off hold quickly...clunky but avoid protocol work. 

My specific question relates to the initial setup where I have two 3 display, 3 camera systems from different vendors. Who decides which stream goes where? Sender or receiver?

Peter

On 2010-12-02, at 2:47 PM, Mike Hammer (hmmr) wrote:

> Ummmm....
> 
> Part of the issue is that with multiple participants with multiple
> inputs and outputs, you can't send all inputs from all sites to all
> other sites.  You kill the network, so some judicious control of what is
> sent when and to whom is needed.  That means that some inputs
> (microphone or camera) are not transmitted at times.
> 
> So, do we allow legs to be asymmetric or not?
> 
> Interested in your view of the collective impact of these types of
> control decisions.
> 
> Mike
> 
> 
> -----Original Message-----
> From: Peter Musgrave [mailto:peter.musgrave@magorcorp.com] 
> Sent: Thursday, December 02, 2010 2:00 PM
> To: Charles Eckel (eckelcu)
> Cc: Mike Hammer (hmmr); maitai@ietf.org
> Subject: Re: [maitai] Roles of Sender and Receiver
> 
> 
> 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