Per a vote of the XMPP Council, changed status to Obsolete and referred implementors to XEP-0213 and XEP-0216.
1.02005-07-21psaPer a vote of the Jabber Council, advanced status to Draft.0.72005-06-08psaFurther clarified dependencies.0.62005-06-02psaPer Council discussion, modified the XEP-0045 profile to require all MUC use cases.0.52005-04-21psaModified the XEP-0045 profile to require occupant use cases and instant room creation only.0.42004-08-18psaClarified several matters in the text; changed name from "advanced" to "intermediate".0.32004-03-24psaUpdated to reflect approval of XMPP Core and XMPP IM.0.22003-11-24psaChanged status to Deferred.0.12003-09-08psaInitial version.
Note: This protocol suite is obsolete. For updated protocol suites, refer to XMPP Intermediate IM Client 2008 (XEP-0213)XEP-0213: XMPP Intermediate IM Client 2008 <https://xmpp.org/extensions/xep-0213.html>. and XMPP Intermediate IM Server 2008 (XEP-0216)XEP-0216: XMPP Intermediate IM Server 2008 <https://xmpp.org/extensions/xep-0216.html>..
The Basic IM Protocol Suite (XEP-0073)XEP-0073: Basic IM Protocol Suite <https://xmpp.org/extensions/xep-0073.html>. introduced the concept of a "protocol suite". This document extends the basic support specified in XEP-0073 by specifying an Intermediate IM Protocol Suite.
This document follows the same approach as XEP-0073. By design, the Basic IM Protocol Suite does not include more advanced instant messaging functionality; the present document fills the need for a protocol suite that addresses such functionality.
A protocol is deemed worthy of inclusion in this protocol suite if:
It addresses common needs of instant messaging users that are addressed by virtually all other popular IM services or systems.
It is more advanced than basic IM and presence.
It has achieved a status of at least Draft within the XMPP Standards Foundation's standards process (as defined in XMPP Extension Protocols (XEP-0001)XEP-0001: XMPP Extension Protocols <https://xmpp.org/extensions/xep-0001.html>.).
We define the Intermediate IM Protocol Suite as follows:
Note well that the foregoing protocols apply to clients only (i.e., they do not introduce new requirements for servers). In addition, these protocols have their own dependencies, which include the following XEPs (as well as various IETF RFCs and W3C specifications):
Data Forms (XEP-0004)XEP-0004: Data Forms <https://xmpp.org/extensions/xep-0004.html>.
In addition, because the intermediate suite builds on the basic suite, by definition all protocols required by XEP-0073 are also required by the intermediate suite (refer to XEP-0073 for details).
This document introduces no additional security considerations above and beyond those defined in the documents on which it depends.
This document requires no interaction with the Internet Assigned Numbers Authority (IANA)The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>..
No namespaces or parameters need to be registered with the XMPP RegistrarThe XMPP Registrar maintains a list of reserved protocol namespaces as well as registries of parameters used in the context of XMPP extension protocols approved by the XMPP Standards Foundation. For further information, see <https://xmpp.org/registrar/>. as a result of this document.