IETF XMPP Working Group

IETF XMPP Working Group
Name	IETF XMPP Working Group
Abbreviation	XMPP WG
Formed	2002
Purpose	Development of Extensible Messaging and Presence Protocol standards
Location	Internet Engineering Task Force
Leader title	Chairs

IETF XMPP Working Group

The IETF XMPP Working Group develops standards for the Extensible Messaging and Presence Protocol and related extensions, facilitating interoperable instant messaging and presence across networks. The group operates within the Internet Engineering Task Force framework, collaborates with standards bodies such as the World Wide Web Consortium and the XMPP Standards Foundation, and influences implementations used by projects like Google Talk, WhatsApp, Jabber, and Prosody.

Overview

The working group focuses on producing Request for Comments documents to advance interoperable protocols used in systems including AOL Instant Messenger, ICQ, Facebook Messenger, Skype integrations, and enterprise solutions from vendors such as Microsoft and IBM. It engages stakeholders from organizations like Cisco Systems, Ericsson, Nokia, Mozilla Foundation, Red Hat, Oracle Corporation, and Yahoo!. Key topics include message format, presence, roster management, multi-user chat used by services like Slack and Discord integrations, federation architectures adopted by platforms such as Matrix (protocol), and standards that intersect with OAuth 2.0, TLS, SASL, and DNS.

History and Charter

The group's charter emerged amid earlier efforts by communities around Jabber and the open-source projects led by figures associated with Jeremie Miller, enterprises like Cisco Systems, and academic contributors from institutions such as Massachusetts Institute of Technology and University of Cambridge. Its formation followed growing deployment of instant messaging in products from AOL, Microsoft MSN, and mobile services by Nokia and BlackBerry Limited. The charter defined liaison relationships with bodies such as the Internet Architecture Board, the Internet Research Task Force, and the XMPP Standards Foundation, and set milestones that referenced technologies like XML, HTTP, IPv6, WebSocket, and compression methods used by zlib and Brotli.

Standards and RFCs

The working group produced and maintained RFCs addressing the core protocol, extensions, and operational practices, aligning with earlier specifications influenced by W3C XML Schema work and encryption standards from OpenSSL and GnuTLS. Notable workstreams included message stanza profiles, presence semantics, multi-user chat, address formats interoperable with SIPv2 sessions and ENUM, and bridging with SIP and XMPP-over-HTTP (BOSH). Efforts referenced security frameworks like IPsec and key management approaches used in Pretty Good Privacy deployments, and considered identity and authentication models compatible with SAML and enterprise directories such as Active Directory.

Working Group Organization and Processes

The group follows IETF processes defined by the Internet Engineering Steering Group and coordinates through mailing lists, meetings at tradeshows like IETF Meetings, and tooling consistent with RFC 2418 style practices. Chairs and document editors liaise with area directors, working across time zones including contributors from European Union research labs, National Institute of Standards and Technology, and companies in Silicon Valley. Decision-making uses rough consensus and running code principles favored by projects like Apache Software Foundation and adheres to intellectual property policies influenced by standards from ITU-T and patent policies debated in contexts such as World Intellectual Property Organization.

Implementations and Interoperability

Reference implementations and interoperable servers and clients emerged across open-source and commercial ecosystems: server software like ejabberd, Prosody, Openfire, and Metronome; client software like Pidgin (software), Gajim, Adium, and mobile clients from Apple Inc. and Google platforms. Bridge projects linked XMPP to SIP, Matrix (protocol), IRC, and social networks such as Twitter and LinkedIn. Testing and interoperability events resembled plugfests held by organizations like European Telecommunications Standards Institute and the Open Mobile Alliance, with quality assurance influenced by practices at Mozilla Foundation and KDE.

Security and Privacy Considerations

Security work addressed end-to-end encryption models informed by Signal Protocol, server-to-server encryption using TLS 1.3 and certificate chains managed via Let's Encrypt and traditional authorities, and authentication interoperability with OAuth 2.0 and OpenID Connect. Privacy considerations engaged concepts from General Data Protection Regulation compliance for European deployments and operational guidance used by enterprises such as Amazon Web Services and Microsoft Azure. Threat models referenced vulnerabilities cataloged by MITRE and best practices consistent with advisories from CERT Coordination Center.

Relationship with XMPP Standards Foundation

The working group maintains liaison and complementary roles with the XMPP Standards Foundation (XSF), coordinating on extension specifications that the XSF incubates and on adoption pathways used by open-source projects like Jabberd2 and communities around XMPP Extensions (XEPs). This collaboration parallels interactions between the IETF HTTP Working Group and the W3C on web standards, with cross-participation from contributors associated with Google, Red Hat, Cisco Systems, and independent implementers.

Category:Internet Engineering Task Force working groups Category:Instant messaging Category:Internet protocols