Re: [splices] SIP INVOKE method - implicit registrations

Adam Roach <adam@nostrum.com> Tue, 17 May 2011 13:34 UTC

Return-Path: <adam@nostrum.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 9DDECE06A2 for <splices@ietfa.amsl.com>; Tue, 17 May 2011 06:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 f-ve6w61SzRU for <splices@ietfa.amsl.com>; Tue, 17 May 2011 06:34:56 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 156B8E06A1 for <splices@ietf.org>; Tue, 17 May 2011 06:34:53 -0700 (PDT)
Received: from hydra-3.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p4HDYmrI050620 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 17 May 2011 08:34:49 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4DD27978.6060200@nostrum.com>
Date: Tue, 17 May 2011 08:34:48 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <7F2072F1E0DE894DA4B517B93C6A0585194E1859C2@ESESSCMS0356.eemea.ericsson.se>
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A0585194E1859C2@ESESSCMS0356.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: "splices@ietf.org" <splices@ietf.org>
Subject: Re: [splices] SIP INVOKE method - implicit registrations
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 13:34:57 -0000

And, to be clear, experience has shown that this kind of dual action (do 
the invoke thing *and* create a subscription) ends up being a really bad 
idea. I haven't read the draft yet, so I don't have an opinion on the 
INVOKE mechanism itself, but the way we would do something like REFER 
with the tools we have today would involve explicit subscriptions to a 
GRUU associated with the UAS if (and only if) the UA sending the REFER 
has an interest in the outcome.

/a

On 5/17/11 08:26, May 17, Christer Holmberg wrote:
> Hi,
>
> Section 3 says:
>
> "An INVOKE request implicitly establishes a subscription to the 'invoke' event."
>
> However, section 4.2.1 of the 3265bis draft (latest version has expired, but I assume it's still intended to be moved forward) has removed implicit registrations, saying that only SUBSCRIBE can be used to create subscriptions.
>
> Regards,
>
> Christer
>
>
>
> ________________________________
>
> 	From: splices-bounces@ietf.org [mailto:splices-bounces@ietf.org] On Behalf Of Shekh-Yusef, Rifaat (Rifaat)
> 	Sent: 17. toukokuuta 2011 16:15
> 	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
>
> 	
>
> 	
>
> 	
>
> 	
>
> 	
>
> 	
>
> _______________________________________________
> splices mailing list
> splices@ietf.org
> https://www.ietf.org/mailman/listinfo/splices