Skip to content

Jabber/XMPP Protocol Branding Proposal

Author: Peter Saint-Andre
Version: 1.0
Date: 2006-09-20
Status: Approved


Since Jeremie Miller invented the Jabber technologies in 1998, the term “Jabber” has been used to describe a number of different things, including a server, a protocol, a communications network, a developer community, a set of technologies, even a company. Over time, we have worked to disambiguate the term “Jabber”. For example, Jeremie renamed the original Jabber server “jabberd”. Another example is that when we submitted our core XML streaming protocols to the IETF, we did so under the name Extensible Messaging and Presence Protocol (XMPP). But we still use the term “Jabber” with regard to the protocols published through the Jabber Software Foundation’s JEP series (where JEP stands for “Jabber Enhancement Proposal”). Unfortunately, this usage causes confusion — is “XMPP” only what is defined in RFCs 3920 and 3921, whereas all the various extensions to XMPP are to be called “Jabber”? In the opinion of the author of this proposal, it is time to reduce the confusion by calling the protocols published by the JSF what in fact they are: XMPP extensions. Therefore, in accordance with Section 3.12 of the JSF Bylaws, the author formally makes the following proposal for consideration at the 2006 Annual Meeting of the JSF.


The Jabber Software Foundation shall:

  1. Rename “Jabber Enhancement Proposal” to “XMPP Extension Protocol” (and JEP to XEP).
  2. Rename “Jabber Council” to “XMPP Council” (including appropriate modifications to Section 8.1 of the JSF Bylaws).
  3. Rename “Jabber Registrar” to “XMPP Registrar”.
  4. Move the JEP, Council, and Registrar web pages from to