Re: [Sip] New Liaison Statement, "OMA LS 178 on XCAP diff-event"
Jari Urpalainen <jari.urpalainen@nokia.com> Wed, 07 March 2007 09:12 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOsCa-0004q0-Oa; Wed, 07 Mar 2007 04:12:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOrBV-0004Md-Jz for sip@ietf.org; Wed, 07 Mar 2007 03:07:41 -0500
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOrBU-00012O-4Q for sip@ietf.org; Wed, 07 Mar 2007 03:07:41 -0500
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l2787GfR024509; Wed, 7 Mar 2007 10:07:31 +0200
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 10:07:14 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 10:07:14 +0200
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 10:07:14 +0200
Received: from kusti.research.nokia.com (mgw.research.nokia.com [172.21.56.13]) by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l27878MU030829; Wed, 7 Mar 2007 10:07:08 +0200
Received: from [172.21.43.170] (esdhcp043170.research.nokia.com [172.21.43.170]) by kusti.research.nokia.com (Postfix) with ESMTP id E6E4093B77; Wed, 7 Mar 2007 10:07:07 +0200 (EET)
Message-ID: <45EE7189.4000201@nokia.com>
Date: Wed, 07 Mar 2007 10:02:17 +0200
From: Jari Urpalainen <jari.urpalainen@nokia.com>
User-Agent: Thunderbird 1.5.0.10 (X11/20070302)
MIME-Version: 1.0
To: ext Jonathan Rosenberg <jdrosen@cisco.com>
Subject: Re: [Sip] New Liaison Statement, "OMA LS 178 on XCAP diff-event"
References: <E1HMrLq-0007Rc-2u@ietf.org> <45EC89B7.5070501@cisco.com>
In-Reply-To: <45EC89B7.5070501@cisco.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Mar 2007 08:07:14.0334 (UTC) FILETIME=[9D8F1BE0:01C7608F]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: fluffy@cisco.com, sip@ietf.org, OMA-PAG@MAIL.OPENMOBILEALLIANCE.ORG, "Drage, Keith (Keith)" <drage@alcatel-lucent.com>, OMA-LIAISON@MAIL.OPENMOBILEALLIANCE.ORG, dean.willis@softarmor.com, Antti Laurila <Antti.K.Laurila@nokia.com>
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org
ext Jonathan Rosenberg wrote: > My main question here is what are the use cases for subscribing to an > individual element, rather than the whole document? It would need to > be a case where a user cares about changes in one of their documents, > but not over certain parts of that document. For the cases of > resource-lists and rls-services, it was far from clear when that would > be desired. Wouldn't a user care about their entire buddy list and not > just some of it? Good point. I had a similar first impression as well. What made me eventually change my mind was the fact that we indeed have a similar feature in XCAP, i.e. a partial GET of components (and this is a similar feature using sip). For sure, in my reference XCAP implementation (general server/client for resource-lists+services AU) I had zero use for the partial retrievals of XML nodes of a document. But this is not to say that someone may still find it useful. Adding this sort of feature afterwards is definitely imo much more awkward. And as I see it, OMA wants to avoid in some cases an additional http retrieval, so it is an optimization case and as well may make the client implementation simpler. And speaking about the actual implementation, adding this feature to the server is pretty much trivial if you manage to get the XCAP baseline done and all this patching stuff, i.e. it doesn't cause much PITA. Another option would be that RFC3427 would be relaxed for sip event packages, i.e. FIFO model for event package names, so that e.g. OMA folks could do their own stuff based on their spec. > > If OMA could provide some specific example use cases and point out > problems with draft-ietf-sip-xcap-config for those cases, it would be > helpful in providing concrete feedback. > > Thanks, > Jonathan R. > there are some other differences: resource selection logic, "possible endless loop" issue, patch or not to patch, parameter stuff, initial subscription sync etc. And after glancing at the last config-framework I am still inclined to think that XCAP isn't the best fit there. br, jari _______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] New Liaison Statement, "OMA LS 178 on XCAP … Dean Willis (OMA)
- Re: [Sip] New Liaison Statement, "OMA LS 178 on X… Dean Willis
- Re: [Sip] New Liaison Statement, "OMA LS 178 on X… Jonathan Rosenberg
- Re: [Sip] New Liaison Statement, "OMA LS 178 on X… Jari Urpalainen
- RE: [Sip] New Liaison Statement, "OMA LS 178 on X… Dostal, Pavel
- Re: [Sip] New Liaison Statement, "OMA LS 178 on X… Dean Willis
- RE: [Sip] New Liaison Statement, "OMA LS 178 on X… Dostal, Pavel
- [Sip] RE: New Liaison Statement, "OMA LS 178 on X… Dostal, Pavel
- Re: [Sip] RE: New Liaison Statement, "OMA LS 178 … Dean Willis
- Re: [Sip] RE: New Liaison Statement, "OMA LS 178 … Jari Urpalainen
- Re: [Sip] RE: New Liaison Statement, "OMA LS 178 … Dean Willis
- Re: [Sip] RE: New Liaison Statement, "OMA LS 178 … Jari Urpalainen