Hi, I am a developer for a RLS server and I have encountered a problem with the interpretation of target list uri for a Subscription. I consider the list uri to be the u...@domain part from the R-URI of the initial Subscribe, but someone reported an inconsistency when the R-URI also contains a parameter. The sip client considered the list uri to contain also the parameter part and used this when constructing the list document that was uploaded on the XCAP server, so the RLS server could not fetch the list. My question is: Which interpretation is correct? Should parameters also be used to identify resource URI? This problem also exists with normal Subscribes.
I have looked through the RFC's and the RLS RFC says that: Section 3. Overview of Operation This resource list is represented by a SIP URI. To learn the resource state of the set of elements on the list, the user sends a single SUBSCRIBE request targeted to the URI of the list. In RFC 3265 (SIP-Specific Event Notification ) it is stated that: 3.1.2. Identification of Subscribed Events and Event Classes The Request URI of a SUBSCRIBE request, most importantly, contains enough information to route the request to the appropriate entity per the request routing procedures outlined in SIP [1]. It also contains enough information to identify the resource for which event notification is desired,, but not necessarily enough information to uniquely identify the nature of the event[..]. It is not clear from here what part of the R-URI identifies the target and whether parameters should also be used. If parameters would also be considered some complications will appear: - if a URI having a parameter 'transport=udp' should be matched to the URI without this parameter - the order of the parameters should not matter - so how do I know which is the right combination to use when searching the list? I hope someone can clarify this. Thanks and regards, Anca Vamanu _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
