RFC 4826: Extensible Markup Language (XML) Formats for Representing Resource Lists
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC4826
- Published
- May 2007
- Authors
- J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 6914SIMPLE Made Simple: An Overview of the IETF Specifications for Instant Messaging and Presence Using the Session Initiation Protocol (SIP)Current
April 2013
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
- RFC 4479A Data Model for PresenceCurrent
July 2006
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 3903Session Initiation Protocol (SIP) Extension for Event State PublicationUpdated
November 2004
- RFC 4590RADIUS Extension for Digest AuthenticationObsoleted
July 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?