Re: [maitai] Roles of Sender and Receiver

Peter Musgrave <peter.musgrave@magorcorp.com> Sat, 04 December 2010 22:15 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 A2ACA28C0E7 for <maitai@core3.amsl.com>; Sat, 4 Dec 2010 14:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.257
X-Spam-Level:
X-Spam-Status: No, score=-103.257 tagged_above=-999 required=5 tests=[AWL=0.342, 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 Lq3oqx2cZgs7 for <maitai@core3.amsl.com>; Sat, 4 Dec 2010 14:15:22 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id AE11628C0E5 for <maitai@ietf.org>; Sat, 4 Dec 2010 14:15:22 -0800 (PST)
Received: by iwn40 with SMTP id 40so13486133iwn.31 for <maitai@ietf.org>; Sat, 04 Dec 2010 14:16:42 -0800 (PST)
Received: by 10.231.182.131 with SMTP id cc3mr3765818ibb.36.1291501002711; Sat, 04 Dec 2010 14:16:42 -0800 (PST)
Received: from [192.168.1.105] ([204.237.32.134]) by mx.google.com with ESMTPS id i16sm3106453ibl.18.2010.12.04.14.16.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Dec 2010 14:16:41 -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: <4CFA8445.1090005@cisco.com>
Date: Sat, 04 Dec 2010 17:16:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0495AE5E-E524-4ADF-9004-8DB98975E9AD@magorcorp.com>
References: <928969B1-F60B-47B8-A526-676E86BA7061@magorcorp.com> <4CF9975D.4060903@cisco.com> <F7377176-D185-4FC6-B012-C776783D5871@magorcorp.com> <4CFA8445.1090005@cisco.com>
To: Paul Kyzivat <pkyzivat@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: Sat, 04 Dec 2010 22:15:23 -0000

> This depends a bit on how much you assume about the UAS. In the worst case, its just a generic sip UA that supports one audio, and maybe one video stream. If offered more than one of each, it will probably either reject the call or else just accept the first of each and refuse the rest.
> 
> For a caller with more than that to offer, it would make sense for *it* to put the audio and video stream that are most important *first*.
> 
This highlights a trap in my thinking. I had assumed that the calling party "expected" the receiver to be a TP system. As you point out - it is not reasonable to assume this. 

A TP could be calling a simple SIP UA (perhaps without even video) all the way up immersive room....

Apologies if I am stating the obvious. 

Peter