Extensible Messaging and Presence Protocol

From P2P Foundation
Jump to: navigation, search

= XMPP is the Extensible Messaging and Presence Protocol, a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.

URL = http://www.xmpp.org/


Description

From the Wikipedia:

"Extensible Messaging and Presence Protocol (XMPP) is an open, XML-inspired protocol for near-real-time, extensible instant messaging (IM) and presence information (a.k.a. buddy lists). It is the core protocol of the Jabber Instant Messaging and Presence technology. The protocol is built to be extensible and other features such as Voice over IP and file transfer signaling have been added.

Unlike most instant messaging protocols, XMPP is based on open standards. Like e-mail, it is an open system where anyone who has a domain name and a suitable Internet connection can run their own Jabber server and talk to users on other servers. The standard server implementations and many clients are also free and open source software." (http://en.wikipedia.org/wiki/XMPP)


Characteristics

"XMPP was originally developed in the Jabber open-source community to provide an open, secure, spam-free, decentralized alternative to the closed instant messaging services at that time. XMPP offers several key advantages over such services:

  • Open -- the XMPP protocols are free, open, public, and easily understandable; in addition, multiple implementations exist in the form clients, servers, server components, and code libraries.
  • Standard -- the Internet Engineering Task Force (IETF) has formalized the core XML streaming protocols as an approved instant messaging and presence technology. The XMPP specifications were published as RFC 3920 and RFC 3921 in 2004, and the XMPP Standards Foundation continues to publish many XEP series.
  • Proven -- the first Jabber/XMPP technologies were developed by Jeremie Miller in 1998 and are now quite stable; hundreds of developers are working on these technologies, there are tens of thousands of Jabber servers running on the Internet today, and millions of people use XMPP for instant messaging through public services such as Google Talk and XMPP deployments at organizations worldwide.
  • Decentralized -- the architecture of the XMPP network is similar to email; as a result, anyone can run their own XMPP server, enabling individuals and organizations to take control of their communications experience. Although there are proposals for taking this further. XMPP isn't peer to peer or serverless.
  • Secure -- any XMPP server may be isolated from the public network (e.g., on a company intranet), robust security using SASL and TLS has been built into the core XMPP specifications, and the XMPP network is virtually spam-free. In addition, the XMPP developer is actively working on end-to-end encryption to raise the security bar even further.
  • Extensible -- using the power of XML, anyone can build custom functionality on top of the core protocols; to maintain interoperability, common extensions are published in the XEP series, but such publication is not required and organizations can maintain their own private extensions if so desired.
  • Flexible -- XMPP applications beyond IM include network management, content syndication, collaboration tools, file sharing, gaming, remote systems monitoring, web services, lightweight middleware, cloud computing, and much more.
  • Diverse -- a wide range of companies and open-source projects use XMPP to build and deploy real-time applications and services; you will never get "locked in" when you use XMPP technologies."

(http://xmpp.org/tech/overview.shtml)

More Information

  1. Presence
  2. XMPP Standards Foundation
  3. Jabber Software Foundation