XMPP

XMPP
Name	XMPP
Developer	Jabber Software Foundation; IETF contributors; Ignite Realtime
Released	1999
Programming language	Erlang, C#, Java, C++, Python
Operating system	Linux, Windows NT, macOS, Android, iOS
Platform	Internet
Genre	Instant messaging protocol
License	BSD license, MIT License

XMPP is an open, decentralized instant messaging protocol originating from the late 1990s designed for real-time communication across networks. It was developed by contributors associated with the Jabber Software Foundation and later standardised through the IETF processes involving working groups and drafts. The protocol underpins a diverse ecosystem of servers, clients, libraries, and extensions used by organisations such as Google, Facebook, WhatsApp (historically), and community projects like Prosody and Openfire.

History

The protocol began with the efforts of developers around the Jabber community and projects such as Jabberd and Jabber.org; early contributors included implementers from AOL, Cisco Systems, IBM, and independents like Jeremie Miller. Formalisation moved through the IETF as a series of RFCs and drafts, involving standards bodies and working groups associated with Internet Engineering Task Force processes and consensus-building similar to those seen in HTTP and SMTP standardisation. Commercial adoption by companies like Google and integration into services by Skype competitors accelerated development of protocol extensions and interoperability efforts with organisations such as Mozilla and Microsoft Corporation stakeholders. Over time, projects such as Eclipse Foundation-hosted libraries, contributors from Red Hat, and community-run servers contributed to a rich extension ecosystem formalised under XMPP Extension Protocols and tracked by community repositories.

Protocol and Architecture

The protocol uses a client–server and federated architecture comparable to protocols maintained by IETF and implemented across software stacks in languages like Java, C#, Erlang, and Python. Core messaging primitives rely on a UTF-8 and XML-based stanza model, with addressing based on Jabber Identifiers influenced by the Domain Name System used by ICANN-registered domains. Transport layers include Transmission Control Protocol sessions often secured with Transport Layer Security negotiated much like HTTPS sessions used by web servers such as Apache HTTP Server and Nginx. Server-to-server federation requires DNS SRV records and mechanisms corresponding to those used by Postfix and Eximmail systems. The architecture supports presence, roster management, multi-user chat components akin to conference systems used by IEEE standards in collaborative environments, and gateways to legacy networks maintained by vendors like Asterisk (PBX).

Features and Extensions

Extensibility is driven by a formal extension catalog managed by community editors, producing extensions for features such as file transfer, multi-user chat, message archive management, and publish–subscribe paradigms exploited by projects like PubSub implementations. Notable extensions include ones enabling end-to-end encryption interoperable with schemes developed by research groups at Open Whisper Systems and encryption standards influenced by NIST curves. Presence and roster semantics align with models used in groupware by Microsoft Exchange and collaboration suites like Nextcloud, while file and media transfer mirror approaches in SIP gateways and WebRTC integration developed by the W3C community. Identity federation and authentication integrate with infrastructure used by OAuth, SAML deployments common in enterprises such as Salesforce and universities using Shibboleth.

Implementations and Clients

Server implementations include open-source projects like Prosody, Openfire, and ejabberd, alongside commercial deployments managed by organisations such as Google in earlier integrations and niche vendors in telecommunications. Client software spans desktop and mobile, including cross-platform clients developed in Qt and GTK toolkits, mobile apps on Android and iOS, and integrations into collaboration products from vendors like Atlassian and Zimbra. Libraries for building servers and clients exist in ecosystems maintained by communities around Maven for Java and package managers like npm, PyPI, and NuGet.

Security and Privacy

Security practices for the protocol mirror those of internet protocols vetted by IETF working groups and cryptographic guidance from organisations like IETF TLS WG and Open Web Application Security Project. End-to-end encryption extensions draw on cryptographic primitives standardised by NIST and libraries from projects like OpenSSL and libsodium. Authentication integrates with enterprise identity providers including Active Directory and LDAP directories leveraged by institutions such as Harvard University in campus deployments. Privacy considerations include metadata minimisation debates similar to those involving companies like Apple and Google and regulatory contexts referencing laws such as General Data Protection Regulation in the European Union.

Use Cases and Applications

Deployments span instant messaging in enterprises comparable to Slack use cases, real-time signalling in telecommunications alongside SIP infrastructures, IoT messaging patterns used in industrial settings by vendors like Siemens and GE, and collaborative tools in academic settings used by institutions such as MIT and Stanford University. Public sector and nonprofit uses include secure communication platforms modelled after practices in Red Cross operations and civil society groups collaborating with organisations like UNICEF. Integrations extend to social networking backends, customer support chat platforms similar to Zendesk, and gaming presence systems used by studios comparable to Valve Corporation.

Category:Instant messaging protocols