RFC 3921: Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6121.
Current version: RFC 6121 — Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
In plain English — editorial summary, not part of the RFC
This memo describes extensions to and applications of the core features of the Extensible Messaging and Presence Protocol (XMPP) that provide the basic instant messaging (IM) and presence functionality defined in RFC 2779. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3921
- Published
- October 2004
- Authors
- P. Saint-Andre
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 107
- Also known as
- —
- Obsoleted by:
- RFC 6121
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
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
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
- RFC 6122Extensible Messaging and Presence Protocol (XMPP): Address FormatObsoleted
March 2011
- RFC 3994Indication of Message Composition for Instant MessagingCurrent
February 2005
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 3505Electronic Commerce Modeling Language (ECML): Version 2 RequirementsCurrent
March 2003
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?