For the partially integrated service, MIX servers will reference the associated MUC server and MUC servers will reference the associated MIX service. This will allow a client that only support MUC or only supports MIX to find the right server if it is given a reference to the other one. For a client that supports both MUC and MIX, it will enable the client to select its preferred service. For a MIX client, it will also be useful to know the MUC service, so that this information can be shared with a MUC client invitation. - The following example shows how a MIX server identifies the associated MUC server: + The following example shows how a MIX server identifies the associated MUC server. Note that MUC MUST NOT be advertized as a feature:
The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:muc:0#muc-mirror'. The field with var='muc-mirror' is the value of which is the mirrored MUC domain's JID.
-Similarly, a MUC service can advertise an associated MIX doming. The following example shows discovery of a MUC domain.
+Similarly, a MUC service can advertise an associated MIX doming. The following example shows discovery of a MUC domain. Note that MIX MUST NOT be advertized as a feature