From 67f15c3e31758aaa8f06b32d53bdc621f0861e65 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Wed, 6 Jun 2018 10:11:00 +0100 Subject: [PATCH] Add blocking section --- xep-0405.xml | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/xep-0405.xml b/xep-0405.xml index afab4c35..ee2ba11f 100644 --- a/xep-0405.xml +++ b/xep-0405.xml @@ -31,12 +31,21 @@ XEP-0372 XEP-0369 XEP-0403 + XEP-0404 MIX-PAM &ksmithisode; &skille; + + 0.2.0 + 2018-06-06 + sek +

+ Add section on Blocking; +

+
0.1.1 2018-06-05 @@ -351,7 +360,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa - + @@ -533,11 +542,17 @@ This approach enables flexible support of multiple clients for a MIX channel pa

- +

Archive of MIX channel messages is done by the participant's server. Where a message is sent to the participant's server and discarded because there are no active clients, it will still be archived. This means that the messages will be available in the local archive and can be picked up by clients when they come online.

+ + +

+ This section describes an issue that needs to be addressed by servers that provide blocking capabilities based on JID. Messages distributed by a MIX channel come from JIDs containing the bare JID of the channel. For presence stanzas (specified in MIX-PRESENCE), IQ stanza relay (specified in MIX-PRESENCE), and private messages (specified in MIX-ANON) use an encoded JID, where the local part of the bare JID contains both the channel name and the senders Stable Participant ID, for example '123435#coven@mix.shakespeare.example'. A server implementing blocking and MIX-PAM needs to recognize this encoding, to prevent blocking these messages when this is not desired. +

+