Re: [splices] Using Two Separate Devices to Start a Conversation proposal

"Worley, Dale R (Dale)" <dworley@avaya.com> Mon, 06 June 2011 19:48 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA971F0C54 for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 12:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMeIUz3T+BQy for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 12:48:29 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id F2F4E1F0C44 for <splices@ietf.org>; Mon, 6 Jun 2011 12:48:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAGUu7U3GmAcF/2dsb2JhbABTph93rgcCm0KGIQSVXopx
X-IronPort-AV: E=Sophos;i="4.65,327,1304308800"; d="scan'208";a="250029826"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jun 2011 15:48:07 -0400
X-IronPort-AV: E=Sophos;i="4.65,327,1304308800"; d="scan'208";a="629947488"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jun 2011 15:48:06 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 6 Jun 2011 15:48:06 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Mon, 6 Jun 2011 15:45:49 -0400
Thread-Topic: [splices] Using Two Separate Devices to Start a Conversation proposal
Thread-Index: AcwkgRTdSiRNpBx1T0WA/78zzNInGQAAUD+I
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222907E9A7@DC-US1MBEX4.global.avaya.com>
References: <AcwcBjEKPHRsQSI9R9CEF7Om5nHptA==> <6369CB70BFD88942B9705AC1E639A33822CCE270F5@DC-US1MBEX4.global.avaya.com>, <BANLkTin+7fnDjmsfZVWKsmt631B7toRYVw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9A2@DC-US1MBEX4.global.avaya.com>, <4DED2C4C.50809@cisco.com>
In-Reply-To: <4DED2C4C.50809@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [splices] Using Two Separate Devices to Start a Conversation proposal
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 19:48:29 -0000

________________________________________
From: splices-bounces@ietf.org [splices-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@cisco.com]

IMO it is *undesirable* to require that there be a common point through
which all the media to/from that end must flow. Its especially
problematic if the "intelligent" device that would have the capability
to do this is bandwidth limited - as could be the case with mobile phones.
________________________________________

A good point -- We've been assuming that all of the aggregated UAs are near
each other in network terms.  But this use-case shows that to be false:  the controller
is my smartphone, but the video source/sink is my PC.

Of course we can accommodate this within a 3PCC environment by having the controller
shuffle SDP information to connect sources/sinks, rather than relaying RTP.

Dale