Re: [splices] Initiate an A/V Call Using Two Separate Devices proposal

"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Sat, 18 June 2011 13:44 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 9C76421F8619 for <splices@ietfa.amsl.com>; Sat, 18 Jun 2011 06:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.247
X-Spam-Level:
X-Spam-Status: No, score=-3.247 tagged_above=-999 required=5 tests=[AWL=0.352, BAYES_00=-2.599, 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 ltRvSr3JHR7J for <splices@ietfa.amsl.com>; Sat, 18 Jun 2011 06:44:10 -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 E102321F8618 for <splices@ietf.org>; Sat, 18 Jun 2011 06:44:09 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAAFGq/E3GmAcF/2dsb2JhbABSl1WPCnesfQKaf4YqBJZbiyA
X-IronPort-AV: E=Sophos;i="4.65,385,1304308800"; d="scan'208";a="252037400"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Jun 2011 09:44:08 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jun 2011 09:43:56 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Sat, 18 Jun 2011 09:44:07 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "splices@ietf.org" <splices@ietf.org>
Date: Sat, 18 Jun 2011 09:44:07 -0400
Thread-Topic: [splices] Initiate an A/V Call Using Two Separate Devices proposal
Thread-Index: AcwcA9ICWlHJ0iFSQrC3DgLgYMzGCQJJsIlIAJJeOSABbigkLQAkFdAb
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CC7FB9B3@DC-US1MBEX4.global.avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CCE270ED@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222907E9AD@DC-US1MBEX4.global.avaya.com>, <6369CB70BFD88942B9705AC1E639A33822CD81336C@DC-US1MBEX4.global.avaya.com>, <CD5674C3CD99574EBA7432465FC13C1B222907EA01@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907EA01@DC-US1MBEX4.global.avaya.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] Initiate an A/V Call Using Two Separate Devices 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: Sat, 18 Jun 2011 13:44:10 -0000

Hi Dale,

Good point.
I am fine with your proposal of not specifying the media type in a URN.

Regards,
 Rifaat

________________________________________
From: Worley, Dale R (Dale)
Sent: Friday, June 17, 2011 4:34 PM
To: Shekh-Yusef, Rifaat (Rifaat); splices@ietf.org
Subject: RE: [splices] Initiate an A/V Call Using Two Separate Devices proposal

I like the general idea of this, but I'm not fond of the details.

urn:invoke:call:initiate;media=video;target=bob@whatever
seems to mean, "Initiate a call to bob@whatever, adding me as a 3rd-party origin for video".

But I don't see the need for the "media=video" part of the URN, as the controller
will have the opportunity to edit my SDP when it receives it before passing it on.

But the URN urn:invoke:call:initiate;target=bob@whatever would seem to tell
the UAS to initiate a call to bob@whatever, without including the UAC as a 3pcc participant.

urn:invoke:call:initiate;media=video
seems to mean, "Initiate a call to me, offering me your video resources."

But again, there seems to be no reason to specify which media are desired, as the UAC
can reject any offered streams that it doesn't like.

I think we want to avoid having to specify media types in the URNs whenever possible, as they
will be multiplying over time.  How would one specify, "Offer me your audio and text resources?"

Dale