Table of Contents
This document describes the compliance with proprietary protocols supported by the Cisco AJAX XMPP Library. This document only details those specifications that the Cisco AJAX XMPP Library has some level of support for.
The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".
This document only discusses those protocols for which the Cisco AJAX XMPP Library contains some support for. If an RFC or XEP is not listed, the Cisco AJAX XMPP Library does not contain any explicit support for that protocol. When a protocol is listed, the "Level of Support" column indicates one of the following:
- Full: All MUSTs, MUST NOTs, SHOULDs, SHOULD NOTs, and MAYs regarding client-side requirements are implemented.
- Partial: All MUSTs and MUST NOTs are implemented, but other areas of the implementation do not meet all of the requirements. This document has a section that details what implmentation limitations exist for that protocol.
| IJEP | Version | Level of Support |
|---|---|---|
| IJEP-069: Temporary Presence Subscription | 1.1 | Full |
The Cisco AJAX XMPP Library implements all MUSTs, MUST NOTs, SHOULDs, SHOULD NOTs, and MAYs from IJEP-069.