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

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Tue, 07 June 2011 02:02 UTC

Return-Path: <rifatyu@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 ADFF821F85D3 for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 19:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_18=0.6, 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 hWEvDP6XaLrp for <splices@ietfa.amsl.com>; Mon, 6 Jun 2011 19:02:57 -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 733C421F85D2 for <splices@ietf.org>; Mon, 6 Jun 2011 19:02:55 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgBAIOF7U2HCzI1/2dsb2JhbABTly+DR4sid64rAptUhiEElWyEFoZf
X-IronPort-AV: E=Sophos;i="4.65,329,1304308800"; d="scan'208";a="250073537"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jun 2011 22:02:54 -0400
X-IronPort-AV: E=Sophos;i="4.65,329,1304308800"; d="scan'208";a="660131788"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 06 Jun 2011 22:02:53 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 6 Jun 2011 22:02:53 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Mon, 6 Jun 2011 22:02:52 -0400
Thread-Topic: [splices] Using Two Separate Devices to Start a Conversation proposal
Thread-Index: Acwko+APei7hPso6SoSQ3NW3OJy6FwAEUttc
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CC7FB9A8@DC-US1MBEX4.global.avaya.com>
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>
In-Reply-To: <4DED66AD.6080701@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: Tue, 07 Jun 2011 02:02:57 -0000

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