Re: [splices] SIP INVOKE method
"Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com> Tue, 17 May 2011 18:21 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 F1F62E073C for <splices@ietfa.amsl.com>; Tue, 17 May 2011 11:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level:
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.251, 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 jLTc2wfYE0cS for <splices@ietfa.amsl.com>; Tue, 17 May 2011 11:21:01 -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 0EBB3E06DE for <splices@ietf.org>; Tue, 17 May 2011 11:20:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYBACm80k3GmAcF/2dsb2JhbACXUINBiw13iHCiegKbYIYZBJRdg3+GRg
X-IronPort-AV: E=Sophos;i="4.65,226,1304308800"; d="scan'208";a="246907221"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 May 2011 14:20:47 -0400
X-IronPort-AV: E=Sophos;i="4.65,226,1304308800"; d="scan'208";a="622921260"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 May 2011 14:20:46 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.201]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 17 May 2011 14:20:46 -0400
From: "Shekh-Yusef, Rifaat (Rifaat)" <rifatyu@avaya.com>
To: Peter Musgrave <musgravepj@gmail.com>
Date: Tue, 17 May 2011 14:20:45 -0400
Thread-Topic: [splices] SIP INVOKE method
Thread-Index: AcwUqGmWp13eUW/uR4utewPD9pKxiQAELGQQ
Message-ID: <6369CB70BFD88942B9705AC1E639A33822CBDA9548@DC-US1MBEX4.global.avaya.com>
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <BANLkTinLjrS3DocT=_MbnDrHdoTLs7RuhQ@mail.gmail.com>
In-Reply-To: <BANLkTinLjrS3DocT=_MbnDrHdoTLs7RuhQ@mail.gmail.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
Cc: "splices@ietf.org" <splices@ietf.org>
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: Tue, 17 May 2011 18:21:02 -0000
Inline... > -----Original Message----- > From: Peter Musgrave [mailto:musgravepj@gmail.com] > Sent: Tuesday, May 17, 2011 11:38 AM > To: Shekh-Yusef, Rifaat (Rifaat) > Cc: splices@ietf.org > Subject: Re: [splices] SIP INVOKE method > > Hi Rifaat, > > Overall this is clearly described and I can see the utility. > > I agree with other comments that explicit subscriptions are evil. > > If find the method name INVOKE very unfortunate - since my brain when parsing > the example actually skipped the INVOKE message thinking it was an INVITE. > Semantically this method is somewhat like HTTP POST - but I think overloading > that term might not be viewed favourably. Maybe ACTION? > I am not sure that the fact that INVOKE is close to INVITE is an enough justification to change the name. Anybody else has an opinion on this? > Do you foresee having actions which accept parameters? For example there is a > special case of an action 'sendvm' that could be generalized to something like > 'redirect vm'. I could also see a case where terminate might wish to specify > the error code to be used to reject the call. > Yes, and I have the following open question about these parameters: Should a separate header be defined for action parameters? > Will the gory details of what a UA must do for each action be something which > is added to the document? > Yes, these details will come. I just wanted to get something out there to start a discussion on the idea of a new SIP method for invoking actions. > Regards, > > Peter Musgrave > > > On Tue, May 17, 2011 at 9:15 AM, Shekh-Yusef, Rifaat (Rifaat) > <rifatyu@avaya.com> wrote: > 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 > > > > > > > > _______________________________________________ > splices mailing list > splices@ietf.org > https://www.ietf.org/mailman/listinfo/splices
- 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