RFC 7259: The Jabber-ID Header Field
In plain English — editorial summary, not part of the RFC
This document defines a header field that enables the author of an email or netnews message to include a Jabber ID in the message header block for the purpose of associating the author with a particular Extensible Messaging and Presence Protocol (XMPP) address.
Document record
- Document ID
- RFC7259
- Published
- May 2014
- Authors
- P. Saint-Andre
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- RFC 7248Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceObsoleted
May 2014
- RFC 7590Use of Transport Layer Security (TLS) in the Extensible Messaging and Presence Protocol (XMPP)Current
June 2015
- RFC 7622Extensible Messaging and Presence Protocol (XMPP): Address FormatUpdated
September 2015
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
- RFC 4854A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)Current
April 2007
- RFC 7572Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant MessagingCurrent
June 2015
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
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?