This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026.

Chatopus is a Jabber/XMPP client for instant messaging (IM) on the Palm OS platform. The client adds feature-rich instant messaging and presence functionality to Palm devices, enabling Palm users to instantly communicate to other wireless and wired users.

RhymBox is a Jabber client for instant messaging. The Jabber network employs a distributed and secure infrastructure. The Jabber protocol is based on the IETF supported XMPP. Jabber is also linked to legacy services (e.g. Yahoo!, MSN, AIM, ICQ, etc).

One of the important requirements to achieve interoperability between conformant systems is the definition of a common communications protocol.

There are two, often exchangeably used terms for the protocol that Jive Messenger and Jive Smack uses: XMPP and Jabber. Although both refer to the same general network protocol, there are important differences between the two

Jabber, Inc. (www.jabber.com) today congratulated the independent Jabber Software Foundation (JSF) (www.jabber.org) for successfully guiding the core specification of the Extensible Messaging and Presence Protocol (XMPP) through the Internet Engineering Task Force's (IETF) rigorous peer-reviewed standardization process.

Released this week, the XIFF framework provides components and libraries for Flash developers to utilize XMPP, or as its more commenly known - Jabber for real-time applications.

Jabber's open, XML-based messaging and presence protocol is one small step closer to making its official pitch to the Internet's leading standards organization, with the establishment of a working group within the Internet Engineering Task Force.

Why another Java-Jabber communications API? I tried the current offerings and each was far enough away from my criteria to merit (drum-roll please) yet another API.

For some time now, the term XMPP (Extensible Messaging and Presence Protocol) has been used as a synonym for Jabber. To my knowledge, this usage began with Andre Durand (founder of Jabber, Inc.) and has continued within some elements of the Jabber community. More recently, the term has gained greater visibility through its association with the proposed IETF Working Group.

Secure IM Server-Windows,Jabber,LDAP,Archives im, instant messaging, jabber, hippa, sec, secure im, im server, instant messaging server, xmpp.

The Jabber Software Foundation (), the non-profit organization that manages open application protocols built on top of the IETF's Extensible Messaging and Presence Protocol (XMPP), and Winfessor Corporation (), today announced Winfessor's commitment to contribute both financial and in-kind donations to support XMPP/Jabber.

The Jabber protocols have evolved through an open design process within the Jabber community since 1999. The base protocols have been contributed to the Internet Engineering Task Force (IETF), whereas various protocol extensions are defined by the Jabber Software Foundation (JSF).

Hoping to calm the tumultuous interoperability waters in a vast sea of instant messaging, one industry group says it has the fix for at least part of the problem.

The Jabber Software Foundation (JSF), the non-profit organization that builds open application protocols on top of the IETF's Extensible Messaging and Presence Protocol (XMPP), today confirmed that Internet2's I2IM working group is focusing its efforts on XMPP. As described on the I2IM's web site, XMPP "has benefited from an open process, open-source implementations, and, recently, IETF-led protocol standardization."

The XMPP component is used to create a lightweight messaging client using the XMPP (Jabber) protocol.

The Internet Engineering Steering Group (IESG) has approved the Extensible Messaging and Presence Protocol (XMPP): Core specification as an IETF Proposed Standard. XMPP Core is a "protocol for streaming XML elements in order to exchange structured information in close to real time between any two network endpoints. While XMPP provides a generalized, extensible framework for exchanging XML data, it is used mainly for the purpose of building instant messaging and presence applications that meet the requirements of RFC 2779." The XMPP Core specification "includes guidelines to ensure that extensions are possible without conflicts or breaking core interoperability. Lack of conflicts is ensured with use of XML namespaces. Interoperability is ensured with careful layering of stanzas of known types, on top of the base stream."

One of the leading frameworks for real-time communications received a sizable vote of confidence Thursday, when the Internet Engineering Task Force (define) signed off on the core specifications of Extensible Messaging and Presence Protocol (XMPP).

Although instant messaging (IM) can be a convenient way to communicate at work, just as often it seems to end up as a comedy of errors: misinterpretations of tone, sending a personal message to the wrong contact and putting up with the terrible nicknames the guy in sales, a.k.a. "Sultan_of_Sales", feels compelled to use.

What a noisy last few weeks in the public instant messaging space. Microsoft (Quote, Chart), AOL (Quote, Chart) and Yahoo (Quote, Chart) all rolled out new product upgrades, all of them promising to reinvent the popular text-chat application.