RFC 3858: An Extensible Markup Language (XML) Based Format for Watcher Information
In plain English — editorial summary, not part of the RFC
Watchers are defined as entities that request (i.e., subscribe to) information about a resource. There is fairly complex state associated with these subscriptions. The union of the state for all subscriptions to a particular resource is called the watcher information for that resource. This state is dynamic, changing as subscribers come and go. As a result, it is possible, and indeed useful, to subscribe to the watcher information for a particular resource. In order to enable this, a format is needed to describe the state of watchers on a resource. This specification describes an Extensible Markup Language (XML) document format for such state. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3858
- Published
- August 2004
- Authors
- J. Rosenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3994Indication of Message Composition for Instant MessagingCurrent
February 2005
- RFC 5025Presence Authorization RulesCurrent
December 2007
- RFC 5361A Document Format for Requesting ConsentCurrent
October 2008
- RFC 3870application/rdf+xml Media Type RegistrationCurrent
September 2004
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
- RFC 3923End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)Current
October 2004
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?