Add blocking section

This commit is contained in:
Steve Kille 2018-06-06 10:11:00 +01:00
parent d01853d08f
commit 67f15c3e31
1 changed files with 17 additions and 2 deletions

View File

@ -31,12 +31,21 @@
<spec>XEP-0372</spec>
<spec>XEP-0369</spec>
<spec>XEP-0403</spec>
<spec>XEP-0404</spec>
</dependencies>
<supersedes/>
<supersededby/>
<shortname>MIX-PAM</shortname>
&ksmithisode;
&skille;
<revision>
<version>0.2.0</version>
<date>2018-06-06</date>
<initials>sek</initials>
<remark><p>
Add section on Blocking;
</p></remark>
</revision>
<revision>
<version>0.1.1</version>
<date>2018-06-05</date>
@ -351,7 +360,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
</section2>
<section2 topic="Roster Management" anchor="proxy-roster">
<section2 topic="Roster Management" anchor="usecase-roster">
@ -533,11 +542,17 @@ This approach enables flexible support of multiple clients for a MIX channel pa
</p>
</section2>
<section2 topic="MAM Archive Support" anchor="proxy-mam">
<section2 topic="MAM Archive Support" anchor="usecase-mam">
<p>
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.
</p>
</section2>
<section2 topic="Blocking Considerations" anchor="usecase-blocking">
<p>
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.
</p>
</section2>
</section1>