rlsStandard-dep Resource lists server is a server which allows subscriptions to lists of users. Its behaviour is defined in [rls] and [sip rls]. As described there, it uses XCAP server for storing data about lists of users. These data can be manipulated in any way by user's client software. Resource lists server is a server which allows subscriptions to lists of users. Its behaviour is defined in [rls] and [sip rls]. As described there, it uses XCAP server for storing data about lists of users. These data can be manipulated in any way by user's client software. Modules
Libraries
Specification says that each time a SUBSCRIBE request to a RL-URI comes, RLS has to ask XCAP server for coresponding <service> in default rls-services document. The XCAP query in this case is for document like <xcap-root>/rls-services/global/index/~~/rls-services/service[@uri=%22<AOR>%22]. Returned <service> is processed according to specification then and the result of it is flat list of URIs to subscribe to. This processing has its weaknesses.
These reasons lead to separation of resource lists into "global lists" and "users lists". Global lists are not stored/modified by regular users; they are managed by administrators and they are handled according the draft. Example of such lists may be "technical support", "human resources", ... Resource lists for users are stored only in their resource-lists documents and the <service> element in global rls-services document is ommited (it is “implicit”). In this case RLS reads directly user's resource-lists document instead of trying to find it in global rls-services document. As said above, resources described in rls-services documents are global resources accessible by all users. No regular user should have acces rights to modify global rls-services document on XCAP server. The construction of rls-services document URI is described in [rls]. Only in short: the AOR from SIP SUBSCRIBE request is combined with XCAP root given in configuration like this: <xcap-root>/rls-services/global/index/~~/rls-services/service[@uri=%22<AOR>%22]. This URI doesn't not specify namespaces as mentioned in definition, but this is due to problems with XCAP server used for tests (problems querying parts of documents with namespaces). Example 1. rls-services uri example Let us assume
Resulting document describing the list will be get from URI: http://localhost/xcap-root/rls-services/global/index/~~/rls-services/service[@uri=%22<technical-support@someorg.org>%22], which means the service element with uri parameter value technical-support@someorg.org stored in rls-services document named index. Example 2. rls-services document There is example rls-services document describing resources “technical-support@test-domain.com”, “hr@test-domain.com” and “work@test-domain.com” which puts previous two into itself. This document should be stored on xcap server in file <xcap-root>/rls-services/global/index. <?xml version="1.0" encoding="UTF-8"?> <rls-services> <service uri="sip:technical-support@test-domain.com"> <list name="Our technical support"> <entry uri="sip:smith@test-domain.com"> <display-name>Smith</display-name> </entry> <entry uri="sip:joe@test-domain.com"> <display-name>Joe</display-name> </entry> <entry uri="sip:agatha@test-domain.com"> <display-name>Agatha</display-name> </entry> </list> <packages> <package>presence</package> </packages> </service> <service uri="sip:hr@test-domain.com"> <list name="Human resources"> <entry uri="sip:johny@test-domain.com"> <display-name>Johny V</display-name> </entry> <entry uri="sip:joe@test-domain.com"> <display-name>Joe</display-name> </entry> </list> <packages> <package>presence</package> </packages> </service> <service uri="sip:work@test-domain.com"> <list name="Employee resources"> <entry uri="sip:technical-support@test-domain.com"> <display-name>Technical support</display-name> </entry> <entry uri="sip:hr@test-domain.com"> <display-name>Human resources</display-name> </entry> </list> <packages> <package>presence</package> </packages> </service> </rls-services> Working with URIs presented in this section have one big disadvantage - it needs full XCAP server which is able to work with partial documents and able to process XPointer expressions in XCAP queries. Due to unavailability of free XCAP servers is there a possibility to use SERi's RLS server in mode of reduced XCAP server needs (see RLS module parameters). If operating in this mode, RLS requests full rls-service document from uri <xcap-root>/rls-services/global/index, inspects it and finds requested resource list according to URI and AOR by itself. (Only if possible! There can't be links to partial documents in rls-services document.) Opposite to global resource lists are resource lists of standalone users. As was told above, these lists are stored as resource-lists documents under user's directories. These resource-lists documents are accessed directly without searching for them in rls-services document - they behave like if they have implicit link there. Example 3. User's resource lists Let us assume
The document below for user Smith can be stored on XCAP server in http://localhost/xcap-root/resource-lists/users/smith/resource-lists.xml. It contains two resource lists: “default” and “contacts”. <?xml version="1.0" encoding="UTF-8"?>
<resource-lists
xmlns="urn:ietf:params:xml:ns:resource-lists"
>
<list name="default">
<display-name>Buddy List</display-name>
<entry uri="sip:joe@test-domain.com">
<display-name>Joe</display-name>
</entry>
<entry uri="sip:jan@test-domain.com">
<display-name>Jan</display-name>
</entry>
</list>
<list name="contacts">
<display-name>Contact List</display-name>
<entry uri="sip:alois@test-domain.com">
<display-name>Alois</display-name>
</entry>
</list>
</resource-lists>
NoteThere might be new versions of internet drafts and thus links to them my be obsolete. In such case try increment version in link or find the draft on IETF by name. XCAP[xcap] draft-ietf-simple-xcap-07.txt - XCAP specification. [xcap_diff] draft-ietf-simple-xcap-diff-01.txt - XCAP changes notifications format. [xcap_profiles] draft-ietf-sipping-config-framework-07.txt -XCAP user profiles. Presence[events] RFC 3265 - SIP Events. [presence] RFC 3856 - Presence Event package. [publish] RFC 3903 - Event state publication. [winfo_doc] RFC 3858 - Data Format for watcher info. [reg] RFC 3680 - SIP Reg Events. Authorization[common auth] draft-ietf-geopriv-common-policy-05.txt. [presence auth] draft-ietf-simple-presence-rules-03.txt - presence authorization XML based data format and usage with XCAP. Resource lists[rls] draft-ietf-simple-xcap-list-usage-05.txt - XML formats for representing resource lists. [sip rls] draft-ietf-simple-event-list-07.txt - Event Notification Extension for Resource Lists. |
Navigation |