Extensible Messaging and Presence Protocol (XMPP) is a communications protocol for message-oriented middleware based on XML (Extensible Markup Language). The protocol was originally named Jabber, and was developed by the Jabber open-source community in 1999 for near real-time, instant messaging (IM), presence information, and contact list maintenance. Designed to be extensible, the protocol has also been used for publish-subscribe systems, signalling for VoIP, video, file transfer, gaming, Internet of Things (IoT) applications such as the smart grid, and social networking services.
Unlike most instant messaging protocols, XMPP is defined in an open standard and uses an open systems approach of development and application, by which anyone may implement an XMPP service and interoperate with other organizations' implementations. Because XMPP is an open protocol, implementations can be developed using any software license; although many server, client, and library implementations are distributed as free and open-source software, numerous freeware and commercial software implementations also exist.
The Internet Engineering Task Force (IETF) formed an XMPP working group in 2002 to formalize the core protocols as an IETF instant messaging and presence technology. The XMPP Working group produced four specifications (RFC 3920, RFC 3921, RFC 3922, RFC 3923), which were approved as Proposed Standards in 2004. In 2011, RFC 3920 and RFC 3921 were superseded by RFC 6120 and RFC 6121 respectively, with RFC 6122 specifying the XMPP address format. In addition to these core protocols standardized at the IETF, the XMPP Standards Foundation (formerly the Jabber Software Foundation) is active in developing open XMPP extensions.
|Internet protocol suite|
- 1 History
- 2 Strengths
- 3 Weaknesses
- 4 Decentralization and addressing
- 5 XMPP as an extensible Message Oriented Middleware (xMOM) platform
- 6 XMPP via HTTP and WebSocket transports
- 7 Implementations
- 8 Deployments
- 9 Extensions
- 10 Competing standards
- 11 Connecting to other protocols
- 12 Development
- 13 See also
- 14 References
- 15 External links
Jeremie Miller began working on the Jabber technology in 1998 and released the first version of the jabberd server on January 4, 1999. The early Jabber community focused on open-source software, mainly the jabberd server (e.g., version 1.0 in May 2000, version 1.2 in October 2000, and version 1.4 in February 2001), but its major outcome proved to be the development of the XMPP protocol.
The early Jabber protocol, as developed in 1999 and 2000, formed the basis for XMPP as published in RFC 3920 and RFC 3921 (the primary changes during formalization by the IETF's XMPP Working Group were the addition of TLS for channel encryption and SASL for authentication). Note that RFC 3920 and RFC 3921 have been superseded by RFC 6120 and RFC 6121, published in 2011.
The first IM service based on XMPP was Jabber.org, which has operated continuously since 1999 and has offered free accounts to users of XMPP. From 1999 until February 2006, the service used jabberd as its server software, at which time it migrated to ejabberd (both of which are free software application servers). In January 2010, the service migrated to the proprietary M-Link server software produced by Isode Ltd.
In August 2005, Google introduced Google Talk, a combination VoIP and IM system that uses XMPP for instant messaging and as a base for a voice and file transfer signaling protocol called Jingle. (The initial launch did not include server-to-server communications; Google enabled that feature on January 17, 2006). Google has since added video functionality to Google Talk, also using the Jingle protocol for signaling. In May 2013, Google announced Jabber compatibility would be dropped from Google Talk for server-to-server federation, although it would retain client-to-server support. Google dropped XMPP support in Google Voice on May 15, 2014; this disrupted use of the service on XMPP-aware hardware such as the Obihai analog telephone adapters.
In January 2008, AOL introduced experimental XMPP support for its AOL Instant Messenger (AIM) service, allowing AIM users to communicate using the standardized, open-source XMPP. However, in March 2008, this service was discontinued. As of May 2011, AOL offers limited XMPP support.
In February 2010, the social-networking site Facebook opened up its chat feature to third-party applications via XMPP. The Facebook developers' site notes that Facebook Chat does not actually run an XMPP server internally, but merely presents an XMPP interface to clients; consequently, some server-side features like roster editing cannot be done via XMPP.
Similarly, in December 2011, Microsoft released an XMPP interface to its (now-defunct) Microsoft Messenger service. Skype, its de facto successor, also provides limited XMPP support. However, these are not native XMPP implementations.
- The architecture of the XMPP network is similar to email; anyone can run their own XMPP server and there is no central master server.
- Open standards
- The Internet Engineering Task Force has formalized XMPP as an approved instant messaging and presence technology under the name of XMPP (the latest specifications are RFC 6120 and RFC 6121). No royalties are required to implement support of these specifications and their development is not tied to a single vendor.
- XMPP technologies have been in use since 1999. Multiple implementations of the XMPP standards exist for clients, servers, components, and code libraries.
- XMPP servers can be isolated from the public XMPP network (e.g., on a company intranet), and strong security (via SASL and TLS) has been built into the core XMPP specifications.
- Custom functionality can be built on top of XMPP; to maintain interoperability, common extensions are managed by the XMPP Standards Foundation. XMPP applications beyond IM include groupchat, network management, content syndication, collaboration tools, file sharing, gaming, remote systems control and monitoring, geolocation, middleware and cloud computing, VoIP and Identity services.
- Does not support Quality of Service (QoS)
- Assured delivery of messages has to be built on-top of the XMPP layer. Normally, this is done using simple sequence number attributes in stanzas.
- Text-based communication.
- Since XML is text based, normal XMPP has a higher network overhead compared to purely binary solutions. This issue is being addressed by the experimental XEP-0322: Efficient XML Interchange (EXI) Format, where XML is serialized in a very efficient binary manner, especially in schema-informed mode.
- In-band binary data transfer is limited
- Binary data must be first base64 encoded before it can be transmitted in-band. Therefore any significant amount of binary data (e.g., file transfers) is best transmitted out-of-band, using in-band messages to coordinate. The best example of this is the Jingle XMPP Extension Protocol, XEP-0166.
Decentralization and addressing
The XMPP network uses a client–server architecture; clients do not talk directly to one another. The model is decentralized, anyone can run a server, but neither anonymous nor peer to peer, like Skype. By design, there is no central authoritative server as there is with services such as AOL Instant Messenger or Windows Live Messenger. Some confusion often arises on this point as there is a public XMPP server being run at jabber.org, to which a large number of users subscribe. However, anyone may run their own XMPP server on their own domain.
Every user on the network has a unique Jabber ID, often abbreviated as JID. To avoid requiring a central server to maintain a list of IDs, the JID is structured like an email address with a username and a domain name (or IP address) for the server where that user resides, separated by an at sign (@), such as firstname.lastname@example.org.
Since a user may wish to log in from multiple locations, they may specify a resource. A resource identifies a particular client belonging to the user (for example home, work, or mobile). This may be included in the JID by appending a slash followed by the name of the resource. For example, the full JID of a user's mobile account would be email@example.com/mobile.
Each resource may have specified a numerical value called priority. Messages simply sent to firstname.lastname@example.org will go to the client with highest priority, but those sent to email@example.com/mobile will go only to the mobile client. The highest priority is the one with largest numerical value.
JIDs without a username part are also valid, and may be used for system messages and control of special features on the server. A resource remains optional for these JIDs as well.
The means to route messages based on a logical endpoint identifier - the JID, instead of by an explicit IP Address present opportunities to use XMPP as an Overlay network implementation on top of different underlay networks.
XMPP as an extensible Message Oriented Middleware (xMOM) platform
||The neutrality of this article is disputed. (July 2014)|
XMPP provides a general framework for messaging across a network. Not surprisingly, this has a multitude of applications beyond traditional Instant Messaging (IM) and the distribution of Presence data. While several service discovery protocols exist today (such as zeroconf, or the Service Location Protocol), XMPP provides a solid base for the discovery of services (see XEP-0030 DISCO) residing locally or across a network, and the availability of these services (via Presence).
Building on its capability to support discovery across local network domains, XMPP is a perfect protocol for Cloud Computing where virtual machines, networks, and firewalls would otherwise present obstacles to alternative service discovery and presence-based solutions. Cloud computing and storage systems rely on various levels and forms of communication, including not only messaging between systems to relay state but also the migration or distribution of larger objects, such as storage or virtual machines. Along with authentication and in-transit data protection, XMPP can be applied at a variety of levels and may prove ideal as an extensible middleware or Message Oriented Middleware (MOM) protocol. Widely known for its ability to exchange XML-based content (natively), it is becoming an open platform for orchestrating the exchange of other forms of content including proprietary binary streams, Full Motion Video (FMV) content, and the transport of file-based content (see the Jingle series of extensions for numerous examples). Here the majority of the applications have nothing to do with human communications (i.e., IM) but instead provides an open means to support Machine-to-Machine (M2M) or Peer-to Peer (P2P) communications across a diverse set of networks.
XMPP via HTTP and WebSocket transports
The original and "native" transport protocol for XMPP is Transmission Control Protocol (TCP), using open-ended XML streams over long-lived TCP connections.
As an alternative to the TCP transport, the XMPP community has also developed an HTTP transport for web clients as well as users behind restricted firewalls. In the original specification, XMPP could use HTTP in two ways: polling and binding. The polling method, now deprecated, essentially implies messages stored on a server-side database are being fetched (and posted) regularly by an XMPP client by way of HTTP 'GET' and 'POST' requests. The binding method, implemented using Bidirectional-streams Over Synchronous HTTP (BOSH), allows servers to push messages to clients as soon as they are sent. This push model of notification is more efficient than polling, where many of the polls return no new data.
Because the client uses HTTP, most firewalls allow clients to fetch and post messages without any hindrances. Thus, in scenarios where the TCP port used by XMPP is blocked, a server can listen on the normal HTTP port and the traffic should pass without problems. Various websites let people sign into XMPP via a browser. Furthermore, there are open public servers that listen on standard http (port 80) and https (port 443) ports, and hence allow connections from behind most firewalls. However, the IANA-registered port for BOSH is actually 5280, not 80.
A perhaps more efficient transport for real-time messaging is WebSocket, a web technology providing for bi-directional, full-duplex communications channels over a single TCP connection. XMPP over WebSocket binding is defined in the IETF proposed standard RFC 7395.
XMPP is implemented by a large number of clients, servers, and code libraries. These implementations are provided under a variety of software licenses.
Several large public IM services natively use XMPP, including Google Talk and LiveJournal's "LJ Talk", Nimbuzz, and Ovi (Nokia). Various hosting services, such as DreamHost and GMX, enable hosting customers to choose XMPP services alongside more traditional web and email services. Specialized XMPP hosting services also exist in form of cloud so that domain owners need not directly run their own XMPP servers, including Cisco WebEx Connect, Chrome.pl, Flosoft.biz, i-pobox.net, and hosted.im.
XMPP is also used in deployments of non-IM services, including smart grid systems such as demand response applications, message-oriented middleware, and as a replacement for SMS to provide text messaging on many smartphone clients.
The XMPP Standards Foundation or XSF (formerly the Jabber Software Foundation) is active in developing open XMPP extensions. However, extensions can also be defined by any individual, software project, or organization. For example, Google has defined a number of non-XSF extensions, which are used in Google Talk and Google+ (e.g., for signalling related to Google Hangouts). Another example is the federation protocol in Apache Wave, which is based on XMPP.
Connecting to other protocols
One of the original design goals of the early Jabber open-source community was enabling users to connect to multiple instant messaging systems (especially non-XMPP systems) through a single client application. This was done through entities called transports or gateways to other instant messaging protocols, but also to protocols such as SMS or email. Unlike multi-protocol clients, XMPP provides this access at the server level by communicating via special gateway services running alongside an XMPP server. Any user can "register" with one of these gateways by providing the information needed to log on to that network, and can then communicate with users of that network as though they were XMPP users. Thus, such gateways function as client proxies (the gateway authenticates on the user's behalf on the non-XMPP service). As a result, any client that fully supports XMPP can access any network with a gateway without extra code in the client, and without the need for the client to have direct access to the Internet. However, the client proxy model may violate terms of service on the protocol used (although such terms of service are not legally enforceable in several countries) and also requires the user to send their IM username and password to the third-party site that operates the transport (which may raise privacy and security concerns).
Another type of gateway is a server-to-server gateway, which enables a non-XMPP server deployment to connect to native XMPP servers using the built in interdomain federation features of XMPP. Such server-to-server gateways are offered by several enterprise IM software products, including:
- IBM Lotus Sametime
- Microsoft Lync Server (formerly named Microsoft Office Communications Server – OCS)
The IETF XMPP working group has produced a number of RFC protocol documents: RFC 3920 (superseded by RFC 6120), RFC 3921 (superseded by RFC 6121), RFC 3922, RFC 3923, RFC 4622, RFC 4854, RFC 4979, and RFC 6122. The most important and most widely implemented of these specifications are:
- RFC 6120, Extensible Messaging and Presence Protocol (XMPP): Core, which describes client–server messaging using two open-ended XML streams. XML streams consist of <presence/>, <message/> and <iq/> (info/query). A connection is authenticated with Simple Authentication and Security Layer (SASL) and encrypted with Transport Layer Security (TLS).
- RFC 6121, Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence describes instant messaging (IM), the most common application of XMPP.
- RFC 6122, Extensible Messaging and Presence Protocol (XMPP): Address Format describes the rules for XMPP addresses, also called JabberIDs or JIDs. Currently JIDs use Stringprep (as defined in RFC 3454) for handling of Unicode characters outside the ASCII range, but this will be changed in the future to use the technology produced by the IETF's PRECIS Working Group.
The XMPP Standards Foundation (XSF) develops and publishes extensions to XMPP through a standards process centered on XMPP Extension Protocols (XEPs, previously known as Jabber Enhancement Proposals - JEPs). The following extensions are in especially wide use:
- Data Forms
- Service Discovery
- Multi-User Chat
- Publish-Subscribe  and Personal Eventing Protocol
- File Transfer
- Entity Capabilities
- HTTP Binding
- Jingle for voice and video
Internet of Things
XMPP features such as federation across domains, publish/subscribe, authentication and its security even for mobile endpoints are being used to implement the Internet of Things. Several XMPP extensions are part of the experimental implementation: Efficient XML Interchange (EXI) Format; Sensor Data; Provisioning; Control; Concentrators; Discovery.
- Comparison of instant messaging clients
- Comparison of instant messaging protocols
- Comparison of XMPP server software
- Secure communication
- Johansson, Leif (April 18, 2005). "Greater NOrdic MIddleware Symposium (GNOMIS)". Oslo: University of Stockholm.
- "Jabber Inc". Cisco.com. Retrieved 2012-11-24.
- "Jabber Instant Messaging User Base Surpasses ICQ" (Press release). XMPP Standards Foundation. September 22, 2003. Retrieved November 30, 2007.
- "Open Real Time Messaging System". Tech.slashdot.org. 1999-01-04. Retrieved 2012-11-24.
- Chatting Up the Chef Linux Journal March 1, 2003 by Marcel Gagné
- "Jabber.org – XMPP Server Migration". August 12, 2009. Retrieved December 14, 2009.
- Burd, Gary (January 17, 2006). "XMPP Federation". Retrieved November 30, 2007.
- "Google's chat client drops Jabber compatibility". Heise Online. May 20, 2013. Retrieved May 27, 2013.
- Florian Jensen (2008-01-17). "AOL adopting XMPP aka Jabber". Archived from the original on 20 January 2008. Retrieved 2008-01-17.
- "AOL XMPP Gateway". 2011-05-14. Archived from the original on 22 May 2011. Retrieved 2011-05-14.
- "Cisco Announces Definitive Agreement to Acquire Jabber". Retrieved January 2, 2010.
- "Facebook Chat Now Available Everywhere". Retrieved February 11, 2010.
- "Facebook Chat API". Retrieved November 29, 2011.
- Dare Obasanjo (2011-12-14). "Anyone can build a Messenger client—with open standards access via XMPP". Windowsteamblog.com. Retrieved 2012-11-24.
- Janko Roettgers (2011-06-28). "Skype adds XMPP support, IM interoperability next? — Tech News and Analysis". Gigaom.com. Retrieved 2012-11-24.
- RFC 6122
- Joe Hildebrand, Craig Kaes, David Waite (2009-06-03). "XEP-0025: Jabber HTTP Polling". Xmpp.org. Retrieved 2012-11-24.
- Ian Paterson, Dave Smith, Peter Saint-Andre, Jack Moffitt (2010-07-02). "XEP-0124: Bidirectional-streams Over Synchronous HTTP ([BOSH])". Xmpp.org. Retrieved 2012-11-24.
- clients, servers, and code libraries
- "Question FAQ #270-What is LJ Talk?". Livejournal.com. 2010-09-27. Retrieved 2012-11-24.
- "Google Wave Federation Protocol". Google.
- "XMPP rises to face SIMPLE standard", Infoworld magazine, April 17, 2003 XMPP rises to face SIMPLE standard
- "XMPP vs SIMPLE: The race for messaging standards", Infoworld magazine, May 23, 2003 Infoworld.com
- XEP-0045: Multi-User Chat
- XEP-0060: Publish-Subscribe
- "Lotus Sametime 7.5 Interoperates with AIM, Google Talk", eWeek, December 6, 2006 Eweek.com
- "Lotus ships gateway to integrate IM with AOL, Yahoo, Google", Network World, December 6, 2006 Networkworld.com
- "Unified Communications: Uniting Communication Across Different Networks", Microsoft Press Release, October 1, 2009 Microsoft.com
- XEP-0004: Data Forms
- XEP-0030: Service Discovery
- XEP-0163: Personal Eventing Protocol
- XEP-0071: XHTML-IM
- XEP-0096: File Transfer
- XEP-0115: Entity Capabilities
- XEP-0322: Efficient XML
- XEP-0323: Sensor data
- XEP-0324: Provisioning
- XEP-0325: Control
- XEP-0326: Concentrators
- XEP-0347: Discovery
- XMPP IoT Wiki
- XMPP IoT mailing list
- XMPP Standards Foundation
- Jabber User Guide – End user introduction to XMPP (archive)
- IETF Publishes XMPP RFCs
- XMPP Case Studies
- Podcast: FLOSS 49: XMPP Peter Saint-Andre interviewed by Randal Schwartz and Leo Laporte
- XMPP wiki site IoT systems chatty things