
Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Parameters
- per [RFC4825]

(last updated 2007-05-24)

XCAP Application Unique IDs
Registration Rules: standards track RFC publication

Application Unique
    ID (AUID)          Description                             Reference
--------------------   --------------------------------------  ---------
xcap-caps              Capabilities of an XCAP server          [RFC4825]
pidf-manipulation      Pidf-manipulation application           [RFC4827]
                       usage defines how XCAP is used
                       to manipulate the contents of 
                       PIDF based presence documents.
resource-lists         A resource lists application is         [RFC4826]
                       any application that needs access 
                       to a list of resources, identified 
                       by a URI, to which operations, 
                       such as subscriptions, can be applied.

rls-services           An Resource List Server (RLS)           [RFC4826]
                       services application is Session 
                       Initiation Protocol (SIP) application 
                       whereby a server receives SIP 
                       SUBSCRIBE requests for resource, and 
                       generates subscriptions towards the 
                       a resource list.
                              
REFERENCES
----------
[RFC4825]  J. Rosenberg, "The Extensible Markup Language (XML) 
           Configuration Access Protocol (XCAP)", RFC 4825, May 2007.

[RFC4827]  M. Isomaki and E. Leppanen, "An Extensible Markup Language 
           (XML) Configuration Access Protocol (XCAP) Usage for 
           Manipulating Presence Document Contents", RFC 4827, May 2007.

[RFC4826]  J. Rosenberg, "Extensible Markup Language (XML) Formats for 
           Representing Resource Lists", RFC 4826, May 2007
             
(registry created 27 July 2005)

[]
