Jabber™ for Mobile Users

 

1.     Introduction

Jabber is an open XML protocol for the real-time exchange of messages and presence between any two points on the Internet. The first application of Jabber technology is an asynchronous, extensible instant messaging platform, and an IM network that offers functionality similar to legacy IM systems such as AIM, ICQ, MSN, and Yahoo. However, Jabber offers several advantages over legacy IM systems:

·         Open -- the Jabber protocol (XMPP) is free, open, public, and easily understandable, and multiple open-source implementations exist for Jabber servers, clients, and development libraries.

·         Extensible -- using the power of XML namespaces, anyone can extend the Jabber protocol for custom functionality; to maintain interoperability, common extensions are managed by the Jabber Software Foundation.

·         Decentralized -- anyone can run their own Jabber server, enabling individuals and organizations to take control of their IM experience.

·         Secure -- Any Jabber server may be isolated from the public Jabber network, many server implementations use SSL for client-server communications, and numerous clients support PGP/GPG for end-to-end encryption; more robust security using SASL and session keys is under development.

Jabber answers many needs for individuals and organizations alike. However, it is important to understand that Jabber doesn't solve all the world's problems. Specifically, Jabber is not:

·         A universal chat client -- while there are Jabber clients for a wide range of computing platforms, they do not offer out-of-the-box interoperability like Trillian or GAIM; interoperability between Jabber and other systems is made possible by server-side "gateways" to the legacy IM systems.

·         An automatic solution to interoperability -- some (but by no means all) Jabber servers offer interoperability with legacy IM systems through "gateways" that translate the Jabber protocol into legacy protocols; however, Jabber is not primarily focused on interoperability, because only the legacy IM systems themselves can make interoperability a reality.

·         A single IM service or software company -- the Jabber community is not monolithic; instead, there exists a wide range of public and private Jabber servers, open-source projects, and software companies, all using the Jabber protocol to build real-time applications and services.

Jabber offers some unique opportunities for wireless users. With a Jabber Instant Messaging server installed at a corporate site, and a mobile workforce equipped with wireless capable devices and Jabber software, users can access and send instant messages and data securely from anywhere in the world. This document discusses the use and deployment of Jabber for mobile enterprise users.

 

2.     Deployment

A typical Jabber based deployment for mobile users is illustrated in Figure 1.  The mobile users are equipped with wireless capable devices, in the form of a Microsoft PocketPC™, Microsoft and non-Microsoft Smartphones™, laptops, and PalmOS™ PDA’s. Using the Jabber protocol (“XMPP”) they communicate via the wireless network and Internet to a Jabber server that sits behind a firewall at the corporate site. All traffic between the wireless device and the server is typically encrypted and secured using 128-bit SSL technology.

 

An alternative deployment is to restrict the use of the Jabber messaging server from within the physical boundaries of the campus. To do this, the Jabber server would simply sit on the local network and communicate with wireless and landline users who are connected the local area network.

 

Figure 1 - Typical Deployment for Mobile Users

 

3.      Advantage: Jabber

A significant enhancement of a Jabber based solution over a proprietary one is that all communication from user to your corporate server is encrypted and does not rely on third-party messaging services or networks. This is an important differentiator between a Jabber and a third party provided solution. Because the Jabber Messaging server resides within the corporate network, it is under the administration and control of your IT department. Another advantage for mobile users is due to the Jabber architecture’s “store and forward” messaging system. In this situation, any messages destined for currently offline users will be stored by the Jabber server, and delivered when the mobile users comes online. Some client software also allows the mobile user to compose messages offline and have those messages sent when a network connection becomes available.

 

Another advantage is the open protocol that Jabber uses, called XMPP. The use of an open protocol allows multiple implementations of the Jabber server and the client software to be available from several sources, which gives you a wide range of choices and fosters the development of additional applications based on the XMPP protocol. In addition to the open protocol, several open source implementations of both the client and server software are available – which gives your organization the ability to audit and modify the software to meet your specific needs.

 

If needed, the Jabber server can be configured to communicate with legacy IM networks such as MSN Messenger™, AOL Instant Messenger™, Yahoo! Instant Messenger™ and ICQ™.

4.     Getting Started

There are a few elements that you will need to get a Jabber based system for mobile users deployed on your network. The first element is to provide your users with wireless capable mobile devices equipped with Jabber client software. There is software available for most platforms and form factors including the Microsoft PocketPC™, Microsoft PocketPC Phone Edition™, Microsoft Smartphone™, J2ME enabled smart phones, RIM Blackberry™ and Microsoft Windows XP/2000™ laptops. Jabber software will work on virtually any wireless network, including ones that use the CDPD, GPRS, CDMA and 802.11 protocols. For use outside of the corporate network it is recommended that you choose a client that supports SSL encryption, so communications remain secure. It is also possible to use Jabber via a VPN connection if your mobile device supports it.

 

The second element to choose is the Jabber server. The server software runs on multiple platforms, including Linux™ and Windows NT/2000/XP™. A typical setup may consist of an Intel Pentium III server running Linux and the Jabber server software. It is recommended that you place the server behind a firewall, but to leave port 5222/5223 open so the Jabber server can communicate with the remote Jabber clients.

 

5.     Conclusion

A Jabber based messaging system provides significant advantages over proprietary messaging systems for mobile users. With clients and servers available for a wide variety of platforms and architectures and based on a standardized open protocol and architecture, Jabber gives you the power and flexibility to deploy a solution that will meet the needs of your mobile organization –without getting tied to a proprietary network or provider.

 

6.     Additional References

Jabber Software Foundation – Supports and maintains the Jabber architecture.

Jabber, Inc – Commercial supplier of Jabber server software and clients.

 

For further information contact: mov Software, Inc.