8.4. XCAP usage for resource lists
Section 8.3 (above) discusses resource lists and how to gain state information about them. This section discusses how these lists are created and maintained.
The list creation solution takes advantage of XCAP (see Chapter 25) as an application usage. [Draft-ietf-simple-xcap-list-usage] defines the XML schema along with its semantics. It also defines the following:
Application Usage ID (AUID) – "resource-lists".
Additional constraints – none.
Naming convention – none.
Resource interdependencies – the list is represented by a URI. If the client does not populate the XML element carrying the URI value, the XCAP server needs to do so.
Authorization policy – default.
The Ut interface in the Internet Protocol Multimedia Subsystem (IMS) architecture is used to manipulate resource lists.
As an example, Alice is using two terminals, one at home and one in the office. She creates her buddy list from her home terminal and adds Bob and Sarah as her buddies. Figure 8.3 illustrates the example. An XCAP request is created carrying the resource (buddy) list to be stored on the server.
The XCAP request may look like the following:
PUT http://xcap.example.com/services/resource-lists/users/
sip:alice@example.com/friends.xml HTTP/1.1 Content-Type:application/resource-lists+xml Host: xcap.example.com <?xml version="1.0" encoding="UTF-8"?> <resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"> <list name="friends"> <entry uri="sip:bob@example.com"> <display-name>Bob</display-name> ...Get The IMS: IP Multimedia Concepts And Services, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
