Re: [Sip] New Liaison Statement, "OMA LS 178 on XCAP diff-event"

[Dean Willis <[e-mail]>]

Antti and Thanos, either or both of you care to take a shot at this?

--
Dean


On Mar 5, 2007, at 3:20 PM, 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?
>
> 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.
>
> Dean Willis (OMA) wrote:
>> Title: OMA LS 178  on XCAP diff-event
>> Submission Date: 2007-03-01
>> URL of the IETF Web page: https://datatracker.ietf.org/public/ 
>> liaison_detail.cgi?detail_id=303 Please reply by 2007-03-23
>> From: Dean Willis(OMA) <[e-mail]>
>> To: IETF SIP WG([e-mail])
>> Cc: [e-mail]
>> [e-mail]
>> [e-mail]
>> Reponse Contact: Pavel Dostal <[e-mail]>
>> Antti Laurila <[e-mail]>
>> Technical Contact: Pavel Dostal <[e-mail]>
>> Antti Laurila <[e-mail]>
>> Purpose: For comment Body: 1	Overview
>> This liaison seeks IETF SIP WG for the opinion on the XCAP Diff  
>> Event Package as drafted in draft-urpalainen-sip-xcap-diff-event-00.
>> 2	Proposal
>> OMA PAG WG deals with a requirement to enable subscription for
>> notification of changes in XCAP resource not only to single  
>> document but also to single XCAP component (XML element or  
>> attribute). This can not be achieved using draft-ietf-sip-xcap- 
>> config because the subscription in this case is allowed only to  
>> single document or folder.
>> A new SIP event package “xcap-diff” is defined in
>> draft-urpalainen-sip-xcap-diff-event-00. This event package allows  
>> subscription to a set of XCAP resources where resources can be  
>> either folder or document or component identified by node  
>> selector. As this functionality fits to current requirements, OMA  
>> PAG WG is considering adopting draft-urpalainen-sip-xcap-diff- 
>> event-00 as the solution for XCAP clients to receive partial  
>> changes of the XCAP resources.
>> 3	Requested Action(s)
>> OMA PAG WG kindly requests IETF SIP WG on the opinion on the XCAP  
>> Diff Event Package as drafted in draft-urpalainen-sip-xcap-diff- 
>> event-00 and its expected progress.
>> 4	Conclusion
>> OMA PAG WG would like to thank IETF SIP WG for their kind  
>> consideration and response to this liaison request and look  
>> forward to future opportunities to work together.
>> Attachment(s):
>>      OMA LS 178 on XCAP Diff Event (https://datatracker.ietf.org/ 
>> documents/LIAISON/file404.pdf)
>> _______________________________________________
>> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use [e-mail] for questions on current sip
>> Use [e-mail] for new developments on the application of sip
>
> -- 
> Jonathan D. Rosenberg, Ph.D.                   600 Lanidex Plaza
> Cisco Fellow                                   Parsippany, NJ  
> 07054-2711
> Cisco Systems
> [e-mail]                              FAX:   [phone]
> http://www.jdrosen.net                         PHONE: [phone]
> http://www.cisco.com
>


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [e-mail] for questions on current sip
Use [e-mail] for new developments on the application of sip