Hello, Sorry if this message appears as a new thread, but I just joined the list for the purpose of this discussion. Indeed, I work with my colleague on using OpenXCAP with the Mercuro IMS client, and one of our questions raised the discussion.
Indeed, I understand the points raised by Anca, but OMA is more precise than IETF regarding the service URI scheme. As we digged in the OMA specs (which can be hard to find) I wanted to answer Laurent Etiemble's last message to point to other specifications. Regarding the service URI Scheme to be used to subscribe to modifications on a document stored in a RLS XDMS, it is given in a document called "Presence Application Characteristics file of Presence v1.1" which gives the service URI template as : <xui>;pres-list=<id> (see http://www.openmobilealliance.org/Technical/release_program/docs/PresenceSIMPLE/V1_1-20080627-A/OMA-SUP-AC_ap0002_presence-V1_0_2-20080627-A.txt) This would mean that the pres-list parameter is the only necessary parameter to use while requesting subscription to the presence event for a given list. Regarding the use of a 409 response to modify the URI on which the RLS XDMS is requested, this behaviour is described in Appendix B of the document "Resource List Server (RLS) XDM Specification". You can find it at : http://www.openmobilealliance.org/Technical/release_program/docs/PresenceSIMPLE/V1_1-20080627-A/OMA-TS-Presence_SIMPLE_RLS_XDM-V1_1-20080627-A.pdf Hope this helps, Antoine Fressancourt _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
