RFC 3923: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)
In plain English — editorial summary, not part of the RFC
This memo defines methods of end-to-end signing and object encryption for the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3923
- Published
- October 2004
- Authors
- P. Saint-Andre
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3922Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)Current
October 2004
- RFC 3921Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceObsoleted
October 2004
- RFC 3920Extensible Messaging and Presence Protocol (XMPP): CoreObsoleted
October 2004
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- 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
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?