Re: [splices] SIP INVOKE method
"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Wed, 18 May 2011 11:37 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 8CE55E06BC for <splices@ietfa.amsl.com>; Wed, 18 May 2011 04:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level:
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125, 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 5rqbnjB95P-E for <splices@ietfa.amsl.com>; Wed, 18 May 2011 04:37:21 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id BBAF3E06B7 for <splices@ietf.org>; Wed, 18 May 2011 04:37:21 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiABAL2u002HCzI1/2dsb2JhbACXTI5Ld4hwo0UCm0+GGQSUXYpF
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="280527158"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 May 2011 07:37:21 -0400
X-IronPort-AV: E=Sophos;i="4.65,231,1304308800"; d="scan'208";a="653297414"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 May 2011 07:37:20 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Wed, 18 May 2011 07:37:20 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: "Parthasarathi R (partr)" <partr@cisco.com>, "splices@ietf.org" <splices@ietf.org>
Date: Wed, 18 May 2011 07:37:18 -0400
Thread-Topic: [splices] SIP INVOKE method
Thread-Index: AcwUlG21RcTDGyn+QBi7uyh9D1M1iwAIncUgAAH/MEAAJAxbgA==
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CBE5C341@DC-US1MBEX4.global.avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <6369CB70BFD88942B9705AC1E639A33822CBDA9433@DC-US1MBEX4.global.avaya.com> <A11921905DA1564D9BCF64A6430A6239054DE574@XMB-BGL-411.cisco.com>
In-Reply-To: <A11921905DA1564D9BCF64A6430A6239054DE574@XMB-BGL-411.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [splices] SIP INVOKE method
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: Wed, 18 May 2011 11:37:22 -0000
Inline... > -----Original Message----- > From: Parthasarathi R (partr) [mailto:partr@cisco.com] > Sent: Tuesday, May 17, 2011 2:57 PM > To: Shekh-Yusef, Rifaat (Rifaat); splices@ietf.org > Subject: RE: [splices] SIP INVOKE method > > Rifaat, > > I skimmed through your draft. I like the idea of controlling remote UA action > using new method (INVOKE). Few comments in the draft: > > 1) Sec 4.1: SUBSCRIBE with expire=0 is used to terminate INVOKE dialog by > INVOKE-Issuer. Whether it is ok to "INVOKE with expire=0" terminate INVOKE > dialog as it avoids the dependency on SUBSCRIBE message to terminate. > The new plan is to remove the implicit subscription. > 2) I foresee the complexity in creating explicit subscription because two > dialog creation methods (INVOKE & SUBSCRIBE) are used to make the single > action. It will be good in case INVOKE acts similar to INVITE (Dialog creation > & Action). INVITE has the implicit action like "ring the phone" or "auto- > answer" whereas INVOKE has explicitly mention the action to be done in INVOKE- > recipient. > I am not sure that I understand your comment, but with the new plan the INVOKE will NOT create a dialog. > 3) Do you foresee INVOKE dialog creation which change the action within INVOKE > dialog. For example: Following three actions using single INVOKE dialog > creation but updating the action based on the application information.. > > Action 1: Create the call > Action 2: Hold the call > Action 3: Terminate the call > In this case, I expect the INVOKE-Issuer to first create a subscription and then to send the INVOKE requests in the context of that dialog. > Thanks > Partha > > ________________________________________ > From: splices-bounces@ietf.org [mailto:splices-bounces@ietf.org] On Behalf Of > Shekh-Yusef, Rifaat (Rifaat) > Sent: Tuesday, May 17, 2011 10:57 PM > To: Shekh-Yusef, Rifaat (Rifaat); splices@ietf.org > Subject: Re: [splices] SIP INVOKE method > Thank you all for your quick review and feedback so far. > I will work on a new version of the draft that removes the implicit > subscription. > > Please, let me know if you have any other comments beside the implicit > subscription issue. > > Regards, > Rifaat > > > From: splices-bounces@ietf.org [mailto:splices-bounces@ietf.org] On Behalf Of > Shekh-Yusef, Rifaat (Rifaat) > Sent: Tuesday, May 17, 2011 9:15 AM > To: splices@ietf.org > Subject: [splices] SIP INVOKE method > > Hi, > > As discussed in the last SPLICES WG meeting in Prague, the REFER method is > overloaded and has limitations that prevents it from being the ideal method > for action invocation. > We have worked on the following new draft that defines a new SIP method to be > used for invoking actions: > https://datatracker.ietf.org/doc/draft-yusef-splices-invoke/ > > We would appreciate it if people review the document and provide us with their > feedback. > > Regards, > Rifaat > > > > >
- Re: [splices] SIP INVOKE method gao.yang2
- [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method - implicit regist… Christer Holmberg
- Re: [splices] SIP INVOKE method - implicit regist… Adam Roach
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Salvatore Loreto
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Christer Holmberg
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method R.Jesske
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Hutton, Andrew