From 34b3cf81c1695389e42fe1da25347b1902692ce5 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Tue, 2 Jan 2018 10:41:18 +0000 Subject: [PATCH] Remove requirement for all user clients to support MIX, --- xep-0369.xml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/xep-0369.xml b/xep-0369.xml index 0a32f70e..fd98959c 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -51,6 +51,7 @@ Clarify that private messages must not be groupchat, Creating Channel Clarification, Address security concerns on Converting a 1:1 Conversation to a Channel, + Remove requirement for all user clients to support MIX,

@@ -370,7 +371,7 @@
  • Online clients MAY register presence, which is then shared with participants who have subscribed to presence.
  • MIX decouples addressing of channel participants from their nicknames, so that nickname changes do not affect addressing.
  • Each participant is addressable by a single bare JID, which is a proxy JID (not the user's real JID) to make it straightforward to hide the user's real JID from other channel participants. Full JIDs comprised of this bare JID plus a resource (also anonymized) are then constructed, allowing visibility into the number of online resources participating in a channel.
    • -
  • Although some protocol is shared with MUC, MUC clients are not interoperable with a MIX service. This means that where a user chooses to use MIX, all of the users clients need to support MIX.
    • +
  • Although some protocol is shared with MUC, MUC clients are not interoperable with a MIX service.
  • MIX requires the server to which the MIX client connects to provide functionality to support MIX. This functionality is defined in this specification and referenced as "MIX Participant's Server Behaviour".
  • MIX domains MUST NOT be used to host end user JIDs.