The &jep0073; introduced the concept of a "protocol suite". This document extends the basic support specified in JEP-0073 by specifying an Intermediate IM Protocol Suite.

This document follows the same approach as JEP-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 Jabber Software Foundation's standards process (as defined in &jep0001;).

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 JEPs (as well as various IETF RFCs and W3C specifications):

• &jep0004;
• &jep0020;
• &jep0047;
• &jep0065;
• &jep0068;
• &jep0082;
• &jep0095;

In addition, because the intermediate suite builds on the basic suite, by definition all protocols required by JEP-0073 are also required by the intermediate suite (refer to JEP-0073 for details).

This JEP introduces no additional security considerations above and beyond those defined in the documents on which it depends.

This JEP requires no interaction with &IANA;.

No namespaces or parameters need to be registered with the ®ISTRAR; as a result of this JEP.