Jive Messenger Protocol Support
Jive Messenger implements the XMPP protocol as well as many extensions to XMPP
through the JEP process at jabber.org. This document provides a summary of that
protocol support and is updated for every Jive Messenger release.
Core XMPP Spport
A major goal of the Jive Messenger project is to provide full support for the XMPP
specifications, RFC 3920 and
RFC 3921. Jive Messenger has
full support for XMPP, except for the items listed below:
- TLS (RFC3920.5) -- Jive
Messenger provides support for a dedicated TLS/SSL port (5223) as used by the older "Jabber"
protocol but does not currently support TLS stream-negotiation as described in XMPP.
- Resource Binding (RFC3920.7)
- SASL (RFC33920.6) --
Jive Messenger currently relies on non-SASL authentication (JEP-0078) for authentication.
- S2S (RFC3920.10.2,
RFC33920.8) --
Server-to-Server (S2S) communication is not currently supported.
- Privacy Lists (RFC3921.10)
JEP Support
The Jabber Software Foundation has a standards process
for approving extensions (JEPs) to the XMPP protocol.
Jive Messenger's support for these JEPs is detailed below. Some JEPs do not require direct
server support and are only implemented by clients; such JEPs are not included in this list.