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

Peter Musgrave <musgravepj@gmail.com> Tue, 07 June 2011 10:18 UTC

Return-Path: <musgravepj@gmail.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 3D3DB11E80E5 for <splices@ietfa.amsl.com>; Tue, 7 Jun 2011 03:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.603
X-Spam-Level:
X-Spam-Status: No, score=-1.603 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_18=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 hVzSTJPWHz+7 for <splices@ietfa.amsl.com>; Tue, 7 Jun 2011 03:17:59 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB7011E80D0 for <splices@ietf.org>; Tue, 7 Jun 2011 03:17:59 -0700 (PDT)
Received: by iwn39 with SMTP id 39so5720585iwn.31 for <splices@ietf.org>; Tue, 07 Jun 2011 03:17:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=bzBAcX2IFlzQGQxgct/0uBv87Tz2c5TXd6V+euPfD84=; b=M7jPGjx5fRjDfe9x/5AA9R7dBKSoDArkyjFSYM9rjEzZtzJHyXoHZBzdwubXt/Bnb4 mrgvgMQmjy250AYOC+2nI9T5vpBmptwm9kS8YsT7zd6DOkS63I5zXW2RrFo2U4xMUuE8 o85dEDfXJImf3r6TOT65PL6jBSMK7gw9t3Q4c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; b=tN8lDjDXdFIx4Rnq45boX/o5gkCjKSOknDs5rG36taFiuQVpFiwrbEFM6HHjqQ2ReY lMDiFRUmFV21TTzjUX4ygItQkkSI0jiPn7os8u+l6FGQDT7fwmBRBGo/0c/vOIzuqTlO aWMdb/aVYzFm0/fjuHdbEzUiAXpcfDAQnZPm8=
Received: by 10.42.83.194 with SMTP id i2mr10392239icl.305.1307441877237; Tue, 07 Jun 2011 03:17:57 -0700 (PDT)
Received: from [192.168.1.101] ([204.237.32.134]) by mx.google.com with ESMTPS id gb8sm2087816ibb.60.2011.06.07.03.17.55 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 07 Jun 2011 03:17:56 -0700 (PDT)
References: <6369CB70BFD88942B9705AC1E639A33822CCE270F5@DC-US1MBEX4.global.avaya.com> <BANLkTin+7fnDjmsfZVWKsmt631B7toRYVw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9A1@DC-US1MBEX4.global.avaya.com> <1C6C5AB3-6085-4CCA-9F1D-8BA5D98ED651@gmail.com> <4DED2EFA.20004@cisco.com> <BANLkTimfP2EaJZtPcjOp6s4v+Gk87vetGw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9AB@DC-US1MBEX4.global.avaya.com> <BANLkTinazZHd8zn-DibcHrEDp5B+iEztVg@mail.gmail.com> <BANLkTikW_WezCEyeZ5-i+6QmUw0XjXjxsg@mail.gmail.com> <4DED66AD.6080701@cisco.com> <6369CB70BFD88942B9705AC1E639A33822CC7FB9A8@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <6369CB70BFD88942B9705AC1E639A33822CC7FB9A8@DC-US1MBEX4.global.avaya.com>
Mime-Version: 1.0 (iPad Mail 8J3)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <4484FAFB-D1FA-4BD4-94DB-529B9D83F74C@gmail.com>
X-Mailer: iPad Mail (8J3)
From: Peter Musgrave <musgravepj@gmail.com>
Date: Tue, 7 Jun 2011 06:19:10 -0400
To: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
Cc: "splices@ietf.org" <splices@ietf.org>
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: Tue, 07 Jun 2011 10:18:00 -0000

I agree this can be dropped.

Peter

Sent from my iPad

On 2011-06-06, at 10:02 PM, "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>; wrote:

> Hi All,
> 
> Very interesting discussion.
> 
> What I had in mind is what Peter described below, but you guys came up with very interesting new ideas that can be used to address this scenario.
> The scenario is technically an interesting and challenging one, but I tend to agree with Paul that it is not really a use case that will likely be used and maybe we should spend our time addressing other more likely to be used uses case.
> 
> Regards,
> Rifaat
> 
> 
> 
> ________________________________________
> From: splices-bounces@ietf.org [splices-bounces@ietf.org] On Behalf Of Paul Kyzivat [pkyzivat@cisco.com]
> Sent: Monday, June 06, 2011 7:45 PM
> To: splices@ietf.org
> Subject: Re: [splices] Using Two Separate Devices to Start a Conversation proposal
> 
> I suspect asymmetric rtp *won't* work a lot of the time, for many
> reasons, whether we think they are reasonable or not.
> 
> Maybe this is just an unreasonable use case. I can't really imagine
> wanting to do this. If I have a handset, or headset, with a mic, it
> probably has a "speaker" too, and it would seem weird using the mic and
> not its speaker too. And when they are separate there is likely to be
> problems with echos.
> 
>        Thanks,
>        Paul
> 
> On 6/6/2011 7:27 PM, Peter Musgrave wrote:
>> Hi all,
>> 
>> My assumptions were that:
>> - Alice's desk phone is doing the media aggregation and creating a
>> reINVITE for Bob with a=sendrecv and asymmetric media:
>>   * media is sent from Bob to Alice desk phone
>>   * media is sent from Alice Computer to Bob
>> 
>> As far as Bob knows this is a dialog only with Alice's deskphone. Bob
>> does not have to support SPLICES or do anything special.
>> 
>> Bob must handle asymmetric RTP from Alice.
>> 
>> Ok?
>> 
>> I agree that requiring media relay does become a bad idea when the
>> relaying element is e.g a cellphone.
>> 
>> Do we think that having asymmetric RTP will be ok? A lot of
>> implementation have worked toward symmetric RTP (and some will only play
>> RTP arriving from the place they are sending to! [1 implementation at
>> SIPIT28, 3 at SIPIT27 - so maybe not worth worrying about]). Are there
>> any issues with ZRTP or use of ICE? [I am not an ICE expert so I can't
>> recall if symmetric RTP was baked into ICE, umm "frozen in" to ICE maybe?]
>> 
>> Regards,
>> 
>> Peter
>> 
>> 
>> 
>> 
>> 
>> On Mon, Jun 6, 2011 at 5:45 PM, Alan Johnston <alan.b.johnston@gmail.com
>> <mailto:alan.b.johnston@gmail.com>> wrote:
>> 
>>    But isn't the INVITE Join received at Alice's Desk Phone?  If so, then
>>    a normal Join will result in Alice's Desk Phone performing mixing of
>>    audio streams from Alice's PC, Alice's Desk Phone, and Bob.  I thought
>>    what was desired (and shown by Rifaat's flow) was that Alice's Desk
>>    phone did not mix the media, but instead inserted/spliced the media
>>    from Alice's PC into the dialog with Bob, resulting in a re-INVITE to
>>    Bob with two m= lines.
>> 
>>    - Alan -
>> 
>>    On Mon, Jun 6, 2011 at 4:15 PM, Worley, Dale R (Dale)
>>    <dworley@avaya.com <mailto:dworley@avaya.com>> wrote:
>>> No, surely it is an ordinary join.  At the far UA, there are two
>>    incoming dialogs, each with one audio m= line.  The only oddity is
>>    that one dialog is recvonly (at the far UA), and so is never sent
>>    media.  The other dialog is sendonly (at the far UA) and so never
>>    provides audio to the mixing, but is only sent the result of the
>>    mixing.  The effect is that the far UA's input audio is sent only to
>>    the second dialog, and the far UA's output audio is driven only by
>>    the first dialog.
>>> 
>>> Dale
>>> 
>>    _______________________________________________
>>    splices mailing list
>>    splices@ietf.org <mailto:splices@ietf.org>
>>    https://www.ietf.org/mailman/listinfo/splices
>> 
>> 
>> 
>> 
>> _______________________________________________
>> splices mailing list
>> splices@ietf.org
>> https://www.ietf.org/mailman/listinfo/splices
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices