Extensible Messaging and Presence Protocol (XMPP): Core
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 30
- Abstract
- This memo defines the core features of the Extensible Messaging and Presence Protocol (XMPP), a protocol for streaming Extensible Markup Language (XML) elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779. [STANDARDS-TRACK]
- Publication Date
- 2004-10-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3920- Link
- https://doi.org/10.17487/RFC3920
- Author(s)
- Peter Saint-Andre
- Keyword(s)
- Instant Messaging, XML, Jabber
Latest version of IETF RFC 3920
Document Versions — IETF RFC 3920
-
▶ IETF RFC 3920 (2004-10-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Amended by:
- RFC6122 — XMPP-ADDR EXTERNAL
Normative Reference(s)
- ISO 10646-1 [Withdrawn]
- IETF RFC 793 [Superseded*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 1750 [Superseded*]
- IETF RFC 2119 [Active*]
- IETF RFC 2222 [Superseded*]
- IETF RFC 2234 [Superseded*]
- IETF RFC 2246 [Superseded*]
- IETF RFC 2277 [Active*]
- IETF RFC 2743 [Active*]
- IETF RFC 2782 [Active*]
- IETF RFC 2818 [Superseded*]
- IETF RFC 2831 [Superseded*]
- IETF RFC 3066 [Superseded*]
- IETF RFC 3280 [Superseded*]
- IETF RFC 3454 [Superseded*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 3491 [Superseded*]
- IETF RFC 3513 [Superseded*]
- IETF RFC 3548 [Superseded*]
- IETF RFC 3629 [Active*]
- W3C XML 1 [Active]
- W3C XML Namespaces 1.0 [Active]
Bibliographic Reference(s)
- Norris, R. and P. Saint-Andre, "Error Condition Mappings", JSF JEP 0086, February 2004. EXTERNAL
- Jabber Software Foundation, "Jabber Software Foundation", < http://www.jabber.org/ >. EXTERNAL
- Saint-Andre, P., "Non-SASL Authentication", JSF JEP 0078, July 2004. EXTERNAL
- Kaes, C., "Definition of Jabber Identifiers (JIDs)", JSF JEP 0029, October 2003. EXTERNAL
- SIMPLE Working Group, "SIMPLE WG", < http://www.ietf.org/html.charters/simple-charter.html >. EXTERNAL
- IETF RFC 1459 [Active*]
- IETF RFC 1939 [Active*]
- IETF RFC 2244 [Active*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2535 [Superseded*]
- IETF RFC 2595 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2779 [Active*]
- IETF RFC 2821 [Superseded*]
- IETF RFC 3501 [Superseded*]
- IETF RFC 3688 [Active*]
- IETF RFC 3921 [Superseded*]
- T-REC-X.208.1988 — CCITT/ISO88d EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3920.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3920, Extensible Messaging and Presence Protocol (XMPP): Core. Available at https://doi.org/10.17487/RFC3920
Snippet:
IETF RFC 3920, Extensible Messaging and Presence Protocol (XMPP): Core. Available at https://doi.org/10.17487/RFC3920
HTML (ISO 690 compliant)
Preview:
IETF RFC 3920, Extensible Messaging and Presence Protocol (XMPP): Core. Available at https://doi.org/10.17487/RFC3920
Snippet:
<span class="citation"><cite>IETF RFC 3920</cite>, Extensible Messaging and Presence Protocol (XMPP): Core. Available at <a href="https://doi.org/10.17487/RFC3920" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3920</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3920, Extensible Messaging and Presence Protocol (XMPP): Core
doi: 10.17487/RFC3920
url: https://doi.org/10.17487/RFC3920
doi: 10.17487/RFC3920
url: https://doi.org/10.17487/RFC3920
Snippet:
<li> <cite id="bib-rfc3920">IETF RFC 3920</cite>, Extensible Messaging and Presence Protocol (XMPP): Core <span class="doi">10.17487/RFC3920</span> </li>
Referenced By
- IETF RFC 3921 [Superseded*]
- IETF RFC 3922 [Active*]
- IETF RFC 3923 [Active*]
- IETF RFC 4854 [Active*]
- IETF RFC 5122 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6885 [Active*]
- IETF RFC 8996 [Active*]