Extensible Markup Language Formats for Representing Resource Lists
RFC 4826, “Extensible Markup Language Formats for Representing Resource Lists”, is a Proposed Standard document published in May 2007 by J. Rosenberg. The canonical text is published by the RFC Editor.
Abstract
In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services that are associated with a group of users. One example is a resource list service. If a user sends a Session Initiation Protocol (SIP) SUBSCRIBE message to the URI representing the resource list service, the server will obtain the state of the users in the associated group, and provide it to the sender. To facilitate definition of these services, this specification defines two Extensible Markup Language (XML) documents. One document contains service URIs, along with their service definition and a reference to the associated group of users. The second document contains the user lists that are referenced from the first. This list of users can be utilized by other applications and services. Both documents can be created and managed with the XML Configuration Access Protocol (XCAP). [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4826 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4825 The Extensible Markup Language Configuration Access Protocol
- RFC 4827 An Extensible Markup Language Configuration Access Protocol Usage for Manipulating Presence Document Contents
- RFC 4824 The Transmission of IP Datagrams over the Semaphore Flag Signaling System
- RFC 4828 TCP Friendly Rate Control : The Small-Packet Variant
- RFC 4823 FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet
- RFC 4829 Label Switched Path Preemption Policies for MPLS Traffic Engineering
- RFC 4822 RIPv2 Cryptographic Authentication
- RFC 4830 Problem Statement for Network-Based Localized Mobility Management